Ensure that all MESA-Toolkit operations account for exclude files.
Motivation and context
Currently only discovery and full port scans account for exclude files. Remaining operations rely on running the scoper operation before running those operations. This can pose a potential risk of inadvertently scanning out of scope assets if ran without first running scoper. Ideally, every operation should account for exclude files inline to minimize the potential risk of scanning out of scope assets.
Implementation notes
Every operation that performs scanning functionality has the ability use the exclude flag independently
Acceptance criteria
How do we know when this work is done?
[ ] aquatone operation allows for using the exclude flag
[ ] default_logins operation allows for using the exclude flag
[ ] encryption_check operation allows for using the exclude flag
[ ] smb_signing_check operation allows for using the exclude flag
[ ] vuln_scans operation allows for using the exclude flag
💡 Summary
Ensure that all MESA-Toolkit operations account for exclude files.
Motivation and context
Currently only discovery and full port scans account for exclude files. Remaining operations rely on running the scoper operation before running those operations. This can pose a potential risk of inadvertently scanning out of scope assets if ran without first running scoper. Ideally, every operation should account for exclude files inline to minimize the potential risk of scanning out of scope assets.
Implementation notes
Acceptance criteria
How do we know when this work is done?