17 docs tagged with "identity"

What an access path is, how it is materialised from the entity graph, the flat API endpoints, and how the detail page surfaces risk, ownership, and remediation. Includes proposed identity-scoped grouping design (not yet shipped).

Split autonomous_identity into 4 distinct types (identity, automation, connection, credential) to accurately model non-authenticating artifacts

Target authentication architecture for SecurityV0 — portal UI, API, and infrastructure access. Three IdPs (GitHub at L1 perimeter, WorkOS at L2 application, Entra at L3 Azure RBAC), four SSH tiers including a narrow Tier-1.5 emergency key, an Active subscription-Owner Entra account (no PIM, no backup SP — 2nd-human-Owner is the rollback) with Security Defaults MFA-on-sign-in.

Make ServiceNow entity identity PDI-independent (versioned typed natural keys) and move deletion protection to a server-enforced per-tenant policy, so a curated demo tenant survives any PDI change with zero manual steps. Executed on dev 2026-07-24 (manifest 25bfda55…) and independently re-verified 2026-07-27; 91 legacy entities re-keyed, 10-entity protected floor intact, zero active-graph dangling references.

High-level implementation plan and graph-enhancement research for a SecurityV0 AWS connector — covering IAM identity graph, workload metadata, ECR/code-deploy chain, and cross-account trust modelling

9-type entity system (identity, workload, connection, credential, owner, role, permission, resource, execution_evidence) and execution chains for the SecurityV0 execution/authority graph

How SecurityV0 decides whether a thing is an identity (principal), a permission grouping (role / permission_set), a permission, or a resource — by behavior, not by the word a vendor uses. Includes the litmus test and a cross-system mapping table (AWS, Entra ID, ServiceNow, GitHub, Kubernetes). Read this whenever a type label looks wrong.

First-principles redesign of SecurityV0's entity type system

Round 5 CISO analysis on what entity type Business Rules, Script Includes, REST Messages, OAuth Profiles, Flow Designer Flows, and Scheduled Jobs should actually be in the SecurityV0 data model

Critical analysis of the current entity_type system

Round 5 critical analysis of entity type classification for automation artifacts (Business Rules, Script Includes, REST Messages, OAuth Profiles, Flow Designer Flows, Scheduled Jobs)

Product-level analysis of whether Business Rules, Script Includes, REST Messages, OAuth Profiles, Flow Designer Flows, and Scheduled Jobs should remain classified as entity_type 'identity' or be re...

6-agent analysis on correct entity typing for automation artifacts

Founder response on access-path identity grouping. Reframes the problem from aggregation to access chain as the unit of risk, control, remediation, and prioritization.

Comprehensive comparison of MVP1 PRD product vision against current platform delivery, identifying structural gaps in UI automation focus, graph visualization, ingestion architecture, and business-...

Deterministic scope boundary for W1 (Agentic AI Exposure Discovery & Assessment)

Deterministic evaluation logic for W1 operating on the normalized execution/authority graph