Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to reproduce any observation #301

Closed
brandtkeller opened this issue Mar 9, 2024 · 3 comments
Closed

Ability to reproduce any observation #301

brandtkeller opened this issue Mar 9, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@brandtkeller
Copy link
Member

brandtkeller commented Mar 9, 2024

Intent

For the Lula validation process - we have access to the validations (proofs) of what is measured and the policy it must adhere to - this can be linked and/or transient across OSCAL as the project defines.

The missing piece for historical assessment data is to have the collected data present in the Assessment-Results such that anyone performing an audit of what was assessed would have the ability to "replay" a given point-in-time observation.

I believe this creates a layer of trust where auditing can be a function of reviewing both the validation inputs, data applied against the inputs, and the policy decision that was made to influence the finding state.

Potential Considerations

  • encode the data collected from domains that is processed by a provider and include it in the assessment-result in some way.
  • Create a flag in the validate command that allows for the replay of a specific observation? Make the output more verbose by logging a pretty-json object and the results of this offline-replay.
  • Other functionality?

Sub-issues

Since this is a decent chunk of work, the following issues have been created to close out this issue:

@brandtkeller brandtkeller added the enhancement New feature or request label Mar 9, 2024
@brandtkeller
Copy link
Member Author

Is there other metadata that we need to include in the observation other information that is pertinent for reproducible result.

@brandtkeller brandtkeller added this to the OSCAL Reporting data milestone Mar 15, 2024
@brandtkeller
Copy link
Member Author

Should we consider the use of a separate file for storing the data collected?

@brandtkeller
Copy link
Member Author

This issue has been decomposed into the aforementioned issues. Closing this issue as complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: ✅ Done
Development

No branches or pull requests

2 participants