SecTest Atlas

Map the attack path. Verify the defense. Preserve the evidence.

Quick start · Install · AI setup · 简体中文 · Contribute

An execution-focused handbook for authorized security assessments. SecTest Atlas turns real attack paths into searchable, checkable, and actionable test cases across networks, servers, wireless, applications, cloud-native platforms, and AI systems.

Open locally · Chinese field handbook · Security policy

Warning

For authorized assessment, education, and defensive validation only. Obtain written permission and define scope, test windows, data handling, rollback, and emergency contacts before running any test.

Why this project

• 31 chapters and 700+ checks covering the full assessment lifecycle.
• No build step: one self-contained HTML file works directly in a browser.
• Operator-friendly UI: navigation search, persistent checkboxes, dark mode, mobile drawer, and print/PDF export.
• Evidence-oriented: findings are structured around observation, proof, impact, remediation, and retest.
• Bilingual onboarding: English-first project documentation with the complete Chinese field handbook included.

Quick start

git clone https://github.com/cndoin/sectest-atlas.git
cd sectest-atlas
python -m http.server 8080

Open http://localhost:8080. There are no package dependencies and no build command. See INSTALL.md for Windows/macOS/Linux instructions, or give AI_INSTALL.md to your coding agent.

Coverage

Area	Included topics
Frameworks	PTES, NIST SP 800-115, OSSTMM, MITRE ATT&CK, CIS Benchmarks
Network & host	L2–L4, DNS, segmentation, Linux/Windows, identity, credentials
Application & platform	Web, API, microservices, cloud, containers, Kubernetes, CI/CD
Wireless & emerging tech	WPA2/WPA3, Wi-Fi 6E/7, BLE, ZigBee, AI/LLM/agents
Resilience	Detection, purple teaming, recovery, ransomware, performance, chaos testing
Delivery	Risk scoring, reports, authorization, ROE, evidence, acceptance criteria

Repository layout

.
├── index.html              # Interactive handbook and GitHub Pages entry
├── assets/                 # Brand and interface visuals
├── docs/handbook.md        # Complete Chinese Markdown handbook
├── INSTALL.md              # Local installation and serving guide
├── AI_INSTALL.md           # Ready-to-use instructions for coding agents
├── CONTRIBUTING.md         # Contribution rules
└── SECURITY.md             # Disclosure policy and legal boundary

Responsible use

1. Test only assets covered by explicit written authorization.
2. Prefer isolated or pre-production validation before approved production windows.
3. Minimize evidence collection, redact sensitive data, and follow agreed retention rules.
4. Document every finding with observation, evidence, impact, remediation, and retest status.
5. Commands in the handbook are references, never permission to test an external target.

Maintenance

Security standards and platform behavior change over time. Updates should cite authoritative sources, state applicable versions and verification dates, and distinguish mandatory requirements from best practices and environment-specific guidance.