Phase 2 · Security Foundation

Stabilize access, ownership, and baseline controls before automation expands the system

Security Foundation follows a System Review when access, ownership, admin roles, devices, and operating rules need to be stabilized first. Practical control — not a preset tool stack or managed security retainer.

Why this matters

Automation and AI are risky when accounts, permissions, devices, and handover rules are unclear. Security Foundation stabilizes control so later workflow and automation work does not scale the wrong problems.

Where Security Foundation sits

Phase 2 usually follows System Review when control gaps dominate, and prepares Automation Readiness when access and ownership are stable enough.

PreviousSystem ReviewOperational diagnosis
This pageSecurity FoundationAccess and ownership control
NextAutomation ReadinessWorkflow stability

See the full six-phase sequence

What this phase includes

Typical signals

  • unclear admin ownership across tools and shared accounts
  • weak account handover when roles change
  • devices and endpoints not reviewed against a baseline
  • automation considered before access and controls are stable

Focus

  • Account ownership and admin roles — who controls access and shared responsibility
  • Access review and offboarding — repeatable rules for onboarding and departures
  • Device and endpoint baseline — endpoints aligned with how the team actually works
  • Structural compliance readiness — operational evidence — not legal interpretation or certification

Outputs

  • access and ownership findings
  • priority control gaps
  • account and admin cleanup plan
  • control roadmap before automation expands

Common control gaps we look for

  • Shared admin accounts without a named owner or recovery path
  • Former staff, contractors, or agencies still holding access
  • Critical tools without consistent MFA or admin discipline
  • Devices and endpoints not reviewed against an agreed baseline
  • SaaS sprawl — tools connected, but no clear access or ownership map
  • Offboarding that does not reliably remove access when roles change

Ready to scope the right control work?

Start with a System Review so control work is scoped before implementation. Security Foundation follows only when the diagnosis supports it.

Start with System Review