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

Consider adding run-as-user concept #55

Open
zport opened this issue Jan 14, 2019 · 0 comments
Open

Consider adding run-as-user concept #55

zport opened this issue Jan 14, 2019 · 0 comments

Comments

@zport
Copy link
Contributor

zport commented Jan 14, 2019

@djhaynes commented on Mon Aug 19 2013

As an output of the AI/OVAL Developer Days conversation (March 2011), it was
proposed that the OVAL System Characteristics file would benefit from some
construct that allowed the specification of the user that the scan was run as.

Outstanding questions that would need to be answered:

  1. Would this simply record the user at a file level, or at a more detailed
    level. (There are cases where an Interpreter would raise privileges during the
    scan, and should that information also get recorded?)
  2. Would use of AI be an appropriate implementation? Or something simpler?

Reference: Minutes from the Developer days conversation, available on the OVAL
web site.

http://oval.mitre.org/community/docs/OVAL_Spring_2011_Developer_Days_Minutes.pdf


@djhaynes commented on Mon Aug 19 2013

This item has been deferred from the Version 5.10 release.


@djhaynes commented on Mon Aug 19 2013

Recommend that this feature be prototyped using the xsd:any space within the
OVAL System Characteristics <system_info/> element. it is unclear that
the concept will apply to all tools. Some tools raise and lower their
privileges based upon needed access at run time. For this capability to be
useful it may need to reflect the privileges used when collecting each object.


@djhaynes commented on Mon Aug 19 2013

This has been moved to the OVAL Language Sandbox on GitHub.

OVALProject/Sandbox#95


@solind commented on Fri Sep 02 2016

Note, XCCDF captures this information in the cdf12:identity element. Punting to 5.12.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant