Skip to content

Commit 837bdce

Browse files
docs: document raw scan output retention and cleanup (#2351)
Co-authored-by: Soujanya S H <[email protected]>
1 parent 7239e61 commit 837bdce

1 file changed

Lines changed: 12 additions & 0 deletions

File tree

docs/SECURE_DEPLOYMENT.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -367,6 +367,18 @@ network behavior of these variables.
367367
> assess.
368368

369369
---
370+
## Raw Scan Output Retention and Cleanup
371+
372+
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.
373+
374+
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.
375+
376+
Before cleaning up runtime-generated artifacts:
377+
378+
* Ensure no active scan is using the files.
379+
* Preserve any reports or artifacts required for investigation or auditing.
380+
* Delete only runtime-generated files and retain repository placeholder files such as `.gitkeep`.
381+
* Verify that required scan results have been exported or archived before removal.
370382

371383
# Hardening Checklist
372384

0 commit comments

Comments
 (0)