Skip to content

docs: document raw scan output retention and cleanup #2351

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

Merged
utksh1 merged 1 commit into from
Aug 4, 2026
Merged

docs: document raw scan output retention and cleanup #2351

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/SECURE_DEPLOYMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -367,6 +367,18 @@ network behavior of these variables.
> assess.

---
## Raw Scan Output Retention and Cleanup

SecuScan stores runtime-generated scan artifacts in directories such as `data/raw/`, `backend/data/raw/`, `data/reports/`, and `backend/data/reports/`. These directories contain temporary scan outputs, reports, and other generated artifacts that are created during scan execution.

Operators should retain runtime-generated artifacts only for operational needs such as validation, troubleshooting, or incident analysis. These artifacts are not intended to be committed to version control.

Before cleaning up runtime-generated artifacts:

* Ensure no active scan is using the files.
* Preserve any reports or artifacts required for investigation or auditing.
* Delete only runtime-generated files and retain repository placeholder files such as `.gitkeep`.
* Verify that required scan results have been exported or archived before removal.

# Hardening Checklist

Expand Down
Loading