user-role-identification

Identifying actors requires building a typed actor catalog detailing authentication mechanisms, trust levels, and data visibility before designing behaviors. This ensures access control boundaries are explicit, preventing authorization mistakes during system modifications.

Tenant boundaries must be enforced at the query and write layer whenever multi-tenant data visibility is involved. Explicit scoping prevents unauthorized cross-tenant access by declaring exactly what data each actor can see and manipulate within their tenant scope.

Scoping data visibility for RBAC requires explicitly declaring what data each actor type can see, cannot see, and aggregate. This role inventory approach forces clear visibility declarations by object and field, securing endpoints against IDOR and privilege escalation.

Handling webhook trust requires classifying external systems as typed actors with explicit authentication mechanisms and trust levels. This prevents trust-boundary violations by ensuring external calls are subject to the same authorization checks as internal service-to-service calls.

Modeling permission boundaries for service-to-service calls requires treating services as typed actors with explicit goals and data visibility limits. This approach flags unclear enforcement predicates and escalates risks to dedicated threat-modeling workflows.

Escalating security risks when enforcement predicates are unclear involves routing the typed actor catalog to permission-boundary-modeling and threat-modeling workflows. This handoff flags audit gaps, IDOR, and privilege escalation risks for deeper analysis.