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

A flag to run "full" report again? #6

Open
7MinSec opened this issue Oct 5, 2022 · 2 comments
Open

A flag to run "full" report again? #6

7MinSec opened this issue Oct 5, 2022 · 2 comments

Comments

@7MinSec
Copy link

7MinSec commented Oct 5, 2022

Hi,

I'm baaaaaack :-)

My understanding of the tool workflow is as follows:

  1. Run the script, get the "full" Ping Castle results in a (very good looking) list.
  2. Fix some things.
  3. Run script again and see what vulns are new/changed/removed
  4. Repeat steps 2 and 3.

However, is there a way to run the script and get a new "full" report just to see what things look like at a high level? The only way I've found to do this is by nuking everything in the reports folder, but I don't want to do that either since I want my historical report to show I'm being a good sysadmin!

Thanks,
Brian

@mpgn
Copy link
Collaborator

mpgn commented Oct 7, 2022

Something like this ?

image

@7MinSec
Copy link
Author

7MinSec commented Oct 10, 2022

Yes I think so. Could there be a header of sorts that indicates something like "Changed since last run" and then a header indicating "Full report" just to make the context of each section clear?

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

2 participants