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

Support to sync Audit findings #270

Open
captainfalcon23 opened this issue Jun 6, 2024 · 4 comments
Open

Support to sync Audit findings #270

captainfalcon23 opened this issue Jun 6, 2024 · 4 comments
Labels
backlog enhancement New feature or request

Comments

@captainfalcon23
Copy link

Hello! Just wondering if there are plans to support syncing of audit findings?

@SteveMcGrath
Copy link
Collaborator

Let me add this to the backlog.

@SteveMcGrath
Copy link
Collaborator

So looking into this new, audit findings in TSC should just pull. TVM would likely require a completely new mapping and a lot of effort to make this work.

Trying to decide if audit findings shoudl be within the same project, a different project, and how we should map these out as the fields in TVM are very different between compliance and vuln findings.

@SteveMcGrath
Copy link
Collaborator

so an update here, after a lot of investigating it seems to make more sense to have a separate project for the audit findings. the data is sufficiently different enough that it doesn't seem to neatly line up at all.

@SteveMcGrath SteveMcGrath added the enhancement New feature or request label Jul 12, 2024
@captainfalcon23
Copy link
Author

When we previously used T.SC, we did sync the audit findings, but noticed it would always create duplicates, so stopped that.

Interesting that the data doesn’t line up, I know when you go to an asset and export all data it all (vulns and audit findings) gets exported nicely into a CSV.

Obviously I don’t have enough insight into this project, or how the tenable API works, but if you feel it needs to be a seperate project, then so be it :) Happy to help if needed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants