Safety framework
Command risk profile
Risk band: Low Medium High
Required permissions:
Risky command warning: Nmap/TLS probing can affect upstream rate limits
Rollout caveat: Test in staging; only escalate with rollback plan
Security workflow
Security checks lab
Move from command to interpretation in one pass: run, paste output, and capture findings locally.
All examples are safe-by-default, with mutating paths explicitly marked.
Scope
- Validate TLS trust chain, protocol, and expiry windows.
- Validate security headers and response posture.
- Confirm recovery and rollback behavior after hardening changes.
Command cards
Core commands
TLS inspection
openssl s_client -connect app.example.com:443 -servername app.example.com -showcerts -verify_return_error
Use with host value only. Replace host values with your endpoint.
Header capture
curl -sI https://app.example.com | sed -n '1,80p'
Pipe output into analyzer and verify security header presence.
Transport validation
nmap -p443 --script ssl-enum-ciphers app.example.com
Run from staging ranges; avoid sensitive production endpoints.
Progress
Checklist
0 of 0 complete
Local analysis
Paste command output for interpretation
Finding capture
Record local findings
Filter:
Total in this lab: 0
Reference path