deixic
Log inRequest a demo

← Blog

Topic

Identity & access

Remove a departing employee's access across the connected systems, read each removal back, and keep the receipt for the auditor.

9 articles

SeriesMake your agents finish the job →Make the AI investment work →Why did the agent do that? →Carry work between connected systems →Identity and access →

Lead article

· 5 min read

CC6.2 is where first SOC 2 audits go sideways

Offboarding is the control growing companies often fail. Why a termination does not reach every system, what an auditor samples, and the evidence that holds up.

Archive

All Identity & access articles

Browse every article →
  1. When an agent asks for more access, what should the buyer ask first?4 min
  2. Why service-account permissions don't fit agents7 min
  3. An Okta agent should explain the access before it changes anything4 min
  4. The lethal trifecta: where it actually lives6 min
  5. How do MCP permissions work when agents use company tools?4 min
  6. Why does my GitHub agent get 404 or resource not accessible errors?4 min
  7. Who should own the credentials an agent uses?4 min
  8. Sub-agent identity: inherit and narrow7 min