SOP-00N: [Title]¶
[Mon DD, YYYY] ยท @[author]
1. Document Control¶
| Field | Value |
|---|---|
| Document ID | SOP-00N |
| Version | 0.1 (Draft) |
| Owner | Lloyd Johnson, Johnson Technical Systems LLC |
| Milestone | Network+ Fundamentals / Subnetting & VLANs / Security+ Frameworks / Network Operations & Troubleshooting |
| Review cycle | [e.g. Every 6 months, or after any upgrade or new failure mode] |
| Classification | Internal / Portfolio sample |
| Related | [SOP-00X Title; ...] |
2. Purpose and Scope¶
What this SOP accomplishes and why it exists.
In scope: systems, people, and situations this applies to.
Out of scope: what it does not cover, and where that is handled instead.
3. System Description or Reference¶
The environment, components, or reference values the procedures depend on. Use a table.
4. Procedure A: [Name]¶
- Step one.
- Step two.
Add Procedure B, C, and so on as separate sections.
5. Verification¶
The procedure passes only when every check holds.
- Check one
- Check two
6. Known Failure Modes or Responsible Parties¶
Use whichever fits: a Symptom / Cause / Resolution table for operational SOPs, or a Role / Responsibility table for process SOPs.
| Symptom | Cause | Resolution |
|---|---|---|
7. Control Mapping¶
Verify each reference against the published framework text before changing status to Reviewed.
| Procedure step | NIST SP 800-53 Rev 5 | ISO/IEC 27001:2022 Annex A or AICPA SOC 2 |
|---|---|---|
8. Revision History¶
| Version | Date | Change |
|---|---|---|
| 0.1 | [YYYY-MM-DD] | Initial draft |