Purpose
Use this skill for approved archive creation or packaging of limited assessment artifacts.
Phase Fit
- Primary: Validation and Controlled Impact Demonstration
- Secondary: Reporting, Retest and Closure
Use When
- Need to package approved assessment artifacts or evidence.
- Need to test whether archive handling affects an approved transfer path.
- Need a repeatable evidence-packaging workflow.
Avoid When
- Archiving broader data than the approved proof path requires.
- Password-protected or staged archives are not explicitly approved.
Inputs
- Approved file scope
- Archive format and retention requirements
- Transfer or reporting goal
Procedure
- Archive only the minimum approved file set.
- Record exact archive format and options used.
- Use the archive only for the approved reporting or validation objective.
- Preserve or destroy the archive according to engagement rules.
- Repeat the same packaging path during retest if needed.
Command Syntax
Replace sample paths with approved in-scope files.
# Create an archive
7z a contoso-evidence.7z evidence/
# Create a password-protected archive
7z a -p'<password>' contoso-evidence.7z evidence/
# AES-256 encrypted archive (also encrypts file names)
7z a -p'<password>' -mhe=on contoso-evidence.7z evidence/
# Add specific file types
7z a contoso-docs.7z "C:\sensitive\*.docx" "C:\sensitive\*.xlsx"
# Split archive into 100 MB parts
7z a -v100m contoso-large.7z C:\large-folder\
# List archive contents
7z l contoso-evidence.7z
# Extract archive
7z x contoso-evidence.7z -o C:\temp\out\
Evidence to Capture
- Exact file scope placed into the archive
- Archive format and options used
- Why packaging mattered to the assessment objective
Safety Boundaries
- Keep archive scope minimal and approved.
- Protect archives as sensitive evidence when they contain assessment data.