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

[Investigate]: add UI proof/picture "evidence" #506

Open
meganwolf0 opened this issue Jun 28, 2024 · 0 comments
Open

[Investigate]: add UI proof/picture "evidence" #506

meganwolf0 opened this issue Jun 28, 2024 · 0 comments
Labels
enhancement New feature or request question Further information is requested

Comments

@meganwolf0
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

There appears to be some use cases where a screenshot is valid "proof" that something is being performed, and generally there may be control satisfaction cases that would be most easily captured as a picture as opposed to trying to assess some declarative proof (e.g., in the form of a config or manifest). Would it be worthwhile investigating possible solutions to programmatically capture screenshots or measure existence of UI fields? This would probably only perform half of a Lula Validation, since policy probably couldn't check the content, but it could save some time with automated collection, repeatability, and mapping evidence to a control.

Additional context

Some go libraries that may provide functionality that would assist:

@meganwolf0 meganwolf0 added the enhancement New feature or request label Jun 28, 2024
@github-actions github-actions bot added the triage Awaiting triage from the team label Jun 28, 2024
@brandtkeller brandtkeller added question Further information is requested and removed triage Awaiting triage from the team labels Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants