The STaIG process is predictable once you know the sequence. Below is the standard path, with references to the specific control areasSTaIG auditors focus on.
Typical end-to-end timeline: 3 – 9 months.
Step 1 — Scoping
Define exactly what's in scope: product lines, systems, offices, subsidiaries, and third-party processors. Over-scoping is the single biggest cause of STaIG cost blowouts; under-scoping risks a scope gap at audit time.
Step 2 — Gap Assessment
Compare your current state against the STaIG control set and produce a gap register. Teams typically run this with either an internal lead or a readiness-focused consultant.
Control areas you'll be assessed on
- Technology governance framework and accountability
- Cybersecurity risk management
- Data governance and protection
- AI ethics and governance principles
- Cloud security and third-party risk management
- Incident response and business continuity
Step 3 — Remediation
Close the gaps. In practice this is a mix of:
- Technical implementation — MFA, logging, encryption, access reviews, backups, vulnerability management.
- Policy and documentation — information security policy, incident response plan, risk register, data classification, vendor management.
- Process adoption — change tickets with approvals, periodic access reviews, management review meetings, awareness training.
Step 4 — Self-Attestation or Third-Party Review
STaIGdoes not strictly require an accredited auditor. Depending on who's asking (customer, regulator, insurer), you may need a self-attestation, a third-party opinion letter, or a readiness assessment report. Clarify this before signing an auditor.
Common Pitfalls
- Scope creep during the engagement. Freeze scope at kickoff.
- Policy without practice. Auditors verify behavior, not just documents.
- Last-minute evidence hunts. Evidence should be collected continuously, not scrambled for the audit window.
For cost breakdowns and budget tiers, see the cheapest path to STaIG. For when it's worth it, see when and why to pursue STaIG.