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.

Sign up for GitHub

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

Jump to bottom

OVAL Vulnerability Template is time consuming #1

Open
GoogleCodeExporter opened this issue Oct 15, 2015 · 1 comment
Open

OVAL Vulnerability Template is time consuming #1

GoogleCodeExporter opened this issue Oct 15, 2015 · 1 comment
Labels
auto-migrated Priority-Low Type-Other

Comments

@GoogleCodeExporter
Copy link
Contributor 

When starting a vulnerability scanning using OVAL and 
windows.vulnerability.xml, this could take a long time. 

This is not an issue but due to the large xml file processed. The oval 
interpreter takes a long time to collect value and analyze information. This is 
by the far the most annoying thing is OVAL.

You may also notice that ovaldi consumes a huge amount of CPU and memory !!

Please, report me any crash due to ovaldi. I will be happy to rely it to the 
oval mitre dev team.

Original issue reported on code.google.com by [email protected] on 5 Dec 2010 at 4:27
@GoogleCodeExporter
Copy link
Contributor Author

Original comment by [email protected] on 5 Dec 2010 at 4:32

  • Changed state: New

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Low Type-Other
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter