Design Partner Program
IDENTITY SECURITY TESTING

Validate the identity paths attackers use to escalate.

Most breaches don’t break in. They log in. Hayrok follows the chain from one test identity through sessions, groups, roles, and service accounts, and proves which links an attacker could actually use.

run_id_0731Identity attack path · contractor → production
ILLUSTRATIVE DATA
HOPS TESTED7 / 7
REPRODUCED2
BLOCKED1
TEST IDENTITIES1
HOP 1 / 7 · CONTRACTORObserved
Test identity starts with contractor access. Approved test identity representing an external contractor. No real user credentials are used.
identityc.lee@contractor (test)
sourceidentity provider
mfaenrolled · satisfied
IDENTITY SOURCESOktaAuth0Google WorkspaceKubernetesGitHubVault
01 · IDENTITY SECURITY TESTING COVERAGE

Identity Security Validation: Reaching Further Than It Should

Identity exposure rarely sits in one setting. It lives in how sessions, roles, groups, and machine identities combine. Each area below is tested with approved test identities, never real user credentials.

01
AUTHENTICATION

Sessions and tokens

Session lifetime, reuse after logout, and token acceptance across apps and environments.

→session reuse after logout→cross-app token acceptance
02
MFA AND STEP-UP

Where MFA actually applies

Which sensitive actions really require step-up, and which paths skip it.

→step-up on sensitive actions→MFA bypass paths
03
ROLES AND GROUPS

Inherited access

Nested groups, templates, and role bundles that grant more than anyone intended.

→nested group inheritance→role bundle drift
04
PRIVILEGE ESCALATION

Climbing the ladder

Self-assigned roles, invite flows, and admin functions reachable from lower roles.

→self role change→admin function access
05
MACHINE IDENTITIES

Service accounts and keys

Impersonation, standing keys, and CI identities with access far beyond their pipeline.

→service account impersonation→long-lived keys
06
LIFECYCLE

Joiners, movers, leavers

Whether access ends when people leave or change roles, including tokens and API keys.

→post-offboarding access→mover access residue
02 · PRIVILEGE ESCALATION TESTING

Privilege Escalation Testing: Expected vs. Observed

Define what each role should be able to do. Hayrok attempts each sensitive action as each role and shows where the system allowed more than the policy says.

ACTIONviewereditoradmin
View billing
Invite a user
Change own role
Export customer data
Rotate API keys
PRIVILEGE ESCALATIONReproducedHigh

Editor can promote itself to admin through the profile settings API.

actionChange own role
roleeditor
expecteddenied
observedallowed
Reproduced with an approved test identity for the role. Exported data is limited to synthetic records.
03 · CROSS-USER AND TENANT ISOLATION

Tenant Isolation Testing: One Customer, Never Another’s Data

Hayrok signs in as a test user in one tenant and tries to reach another tenant’s data the ways attackers do: swapped IDs, overridden tenant headers, shared search, exports, and caches. Each attempt is recorded as held or broken.

TECHNIQUE 02 · TENANT HEADER OVERRIDEILLUSTRATIVE
AAcmetenant_acme
CALLERalice@acme (test)
inv_ac_118
reports/q3
!
GGlobextenant_globex
REACHEDinvoices (all)
users (4)
billing profile
requestGET /api/invoices · X-Tenant-Id: globex
asalice@acme
expected403
observed200 OK · 12 invoices
ReproducedHighThe API trusted the header over the session’s tenant claim and returned Globex invoices.
04 · IDENTITY LIFECYCLE SECURITY TESTING

Identity Lifecycle Validation: Prove Access Ended

Joiner, mover, and leaver changes are where access quietly outlives its purpose. Hayrok replays each change with test identities and checks what still works afterwards.

LEAVER

Contractor offboarded at 09:00.

Account disabled09:00 · identity provider Observed
SSO sessions09:05 · re-auth attempt Denied
Personal API token09:40 · GET /api/projects Reproduced
SSH certificate09:40 · expired Denied
1 A token survived offboarding IdP sessions were revoked, but a personal API token issued before offboarding still worked 40 minutes later.
05 · SERVICE ACCOUNT SECURITY TESTING

Machine Identity Security: More Access Than They Use

Service accounts, CI identities, and API keys rarely log in the way people do, so they rarely get reviewed. Hayrok tests who can act as each one and what it can actually reach.

IDENTITYKINDCAN BE USED BYREACHESRESULT
ci-deployer CI service account deploy-staging role kv/prod/* secrets Reproduced
svc-reporting API key · 412 days old anyone with repo read analytics warehouse Reproduced
k8s:orders/default Kubernetes service account any pod in orders ns cluster-wide list secrets Observed
gh-actions-oidc Workload identity main branch workflows only staging deploy only Not confirmed
backup-runner Scheduled job identity ops-oncall group prod snapshots (read) Observed
06 · IDENTITY THREAT DETECTION VALIDATION

Detection Effectiveness: The Path Worked. Did Anyone Notice?

For each step of the identity path, Hayrok records what your identity provider, SIEM, and detection rules saw while it ran. Gaps between expected and observed detections become findings too.

STEP 03 · DETECTION EVIDENCE

Service account impersonation

Cloud audit logimpersonation event exp log logged
SIEMhuman → service account impersonation exp alert no alert
Detection ruleITDR: privilege jump exp alert no alert
Logged, but neither alert fired. This step was invisible to responders.
07 · CONTINUOUS IDENTITY VALIDATION

Identity Drift Detection: Catch It Before It’s a Path

Groups get nested, roles get copied, people move. Scheduled runs replay the same approved paths and show when a boundary that held last week stops holding.

REPRODUCED HOPS PER WEEKLY RUNILLUSTRATIVE
W1W2W3W4W5W6W7W8
PATH EXTENDED2026 · week 45

Impersonation added a second reproduced hop.

With the deploy role in place, the run reproduced service account impersonation and a production secret read.
HOPdeploy staging → ci-deployer
HOPci-deployer → kv/prod/*
08 · GOVERNED IDENTITY TESTING

Governed Testing: Test Identities Only

Every attempt is checked against the approved plan before it runs. Anyone with authority can stop a run instantly.

identities: test_only

Test identities only

Every attempt uses approved test accounts and service identities. Real user credentials are never collected.

actions: read_first

Read before write

Role changes and other writes are added to the plan only when someone approves them, and are reverted after.

sessions: bounded

Bounded sessions

Sessions and tokens created during a run are tracked and revoked when it ends.

stop: anytime

Stop conditions

Lockouts, alerts, or unexpected responses pause the run automatically.

09 · IDENTITY POSTURE VS PROOF

Identity Validation vs Posture: What Works, Not What’s Assigned

Posture tools read settings. A penetration test explores one engagement. Identity security validation keeps proving which paths are usable as roles, groups, and people change.

Identity posture tool
Penetration test
Hayrok identity security testing
WHAT IT SHOWS
Assigned roles, groups, and settings.
What a tester reached during the engagement.
Which identity paths are usable, hop by hop, with evidence.
INHERITED ACCESS
Listed, often without context.
Depends on tester time.
Each inherited permission exercised with a test identity.
MACHINE IDENTITIES
Inventory of service accounts.
Sometimes in scope.
Impersonation and standing keys validated in the path.
LIFECYCLE
Point-in-time snapshot.
Rarely covered.
Joiner, mover, and leaver changes replayed and checked.
AFTER A FIX
Next scan.
Separate retest.
Retest from the evidence record; the result joins the same record.
10 · FAQ

Identity Security Testing FAQ: What Evaluators Ask

It proves which identity paths an attacker could actually use. Hayrok exercises sessions, roles, groups, and service accounts with approved test identities and records what was reproduced, observed, or not confirmed.

Book an Identity Demo: A Path Validated in Your Environment

Walk through connecting an identity source, configuring test identities, approving the plan, and reading the path and evidence.

✓Connect an identity source and test identities✓Approve the plan and follow the path hop by hop✓Read the evidence and retest after a fix
Book a Demo