The Identity
Stack Guide
What you should use vs. what you probably use
Personal Gmail accounts. Shared passwords in a Google Doc (yes, a Google Doc). No MFA. No MDM. Your "offboarding process" is hoping the intern who quit doesn't remember the Netflix password.
We'll tell you what stack makes sense — no sales pitch (ok, maybe a small one).
Google Workspace doing everything. 1Password with "shared vaults" that 40 people have access to. Someone set up Okta once but half the apps aren't connected. Access reviews = the CEO asking "do we still need Figma?" once a year.
We'll tell you what stack makes sense — no sales pitch (ok, maybe a small one).
Okta SSO for 60% of apps, the rest use SAML "when we get around to it." Access reviews in a spreadsheet that's always 3 months out of date. The security team has a Jira board titled "Identity Debt" with 200 tickets. Nobody looks at it.
We'll tell you what stack makes sense — no sales pitch (ok, maybe a small one).
You've outgrown your startup tools but haven't upgraded. Someone still does access reviews in a spreadsheet. Three different people think they're the admin on Okta. The SaaS spend report was "almost done" for six months.
We'll tell you what stack makes sense — no sales pitch (ok, maybe a small one).
Three identity systems that don't talk to each other. SailPoint implementation that started 8 months ago and is "60% done." A compliance team that spends 40% of their time taking screenshots. 2,000 orphaned accounts from the last two acquisitions.
We'll tell you what stack makes sense — no sales pitch (ok, maybe a small one).
An identity org chart with 15 people and 4 different reporting lines. CyberArk for PAM, SailPoint for IGA, Okta for SSO, Entra for M365, ServiceNow for ticketing — all with different "sources of truth." Your CISO has a slide that says "Identity Fabric" on it but can't tell you how many service accounts exist.
We'll tell you what stack makes sense — no sales pitch (ok, maybe a small one).