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

Tenable SC (vulnerability) pipeline feature request: tenable_sc.vulnerability.age #7198

Closed
jgreene-TrappTech opened this issue Jul 31, 2023 · 1 comment · Fixed by #7210
Closed
Assignees

Comments

@jgreene-TrappTech
Copy link

jgreene-TrappTech commented Jul 31, 2023

Please add tenable_sc.vulnerability.age or vulnerability.age derived from (tenable_sc.vulnerability.last_seen - tenable_sc.vulnerability.first_seen) to the logs-tenable_sc.vulnerability-<version> pipeline, formatted as days.

possible approach:

if(ctx?.tenable_sc.vulnerability.first_seen != null && ctx?.tenable_sc.vulnerability.last_seen !=null ) {ctx.tenable_sc.vulnerability.age = ChronoUnit.DAYS.between(ZonedDateTime.parse(ctx?.tenable_sc.vulnerability.last_seen), ZonedDateTime.parse(ctx?.tenable_sc.vulnerability.first_seen)); }

Justification: Many audits require the tracking and remediation of vulnerabilities discovered and have Vulnerability Remediation SLAs. Having this value calculated by the pipeline supports enriched reporting and alerting.

@elasticmachine
Copy link

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

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

Successfully merging a pull request may close this issue.

4 participants