SectionIdentity and Access Mgmt
Technology category
ReBAC
ReBAC belongs to the Identity and Access Mgmt area. ReBAC, or Relationship-Based Access Control, determines authorization from the relationship between a subject and a protected object. Examples include owner, team member, service administrator, manager, or approver.
Acronym Glossary
This glossary explains acronyms used in this part so the intended security function is clear.
- ReBAC
- Relationship-Based Access ControlAccess control based on the identity's relationship to a specific object, team, owner, or managed service.
What This Technology Covers
ReBAC, or Relationship-Based Access Control, determines authorization from the relationship between a subject and a protected object. Examples include owner, team member, service administrator, manager, or approver.
Why It Matters
ReBAC is useful for shared data, project teams, and complex applications where a role or static attribute alone does not explain why a particular identity should access a particular object.
In practice, this is not only a technical function. It is a way to place the solution into a broader security architecture. Many organizations operate dozens of consoles and tools, so the challenge is also to understand which technology solves which type of risk.
This category helps name the problem precisely, narrow the list of relevant solutions, and distinguish technologies that may look similar at first glance. That is useful for partners and customers who already understand cybersecurity but need a clear map of the market and available portfolio.
Typical Use Cases
ReBAC is usually considered when an organization needs tighter control over a specific security layer within Identity and Access Mgmt. It can complement an existing architecture, replace an outdated tool, improve visibility, or consolidate functions currently split across multiple products.
Place In The Architecture
Within the broader Identity and Access Mgmt architecture, ReBAC should be assessed by how it connects to existing security and operational processes. Its practical value appears when the solution provides usable data, clear policies, understandable reporting, and integrations with existing tools.
When mapping this technology to SecTec portfolio vendors, it is important to consider not only the feature itself, but also deployment model, licensing, management level, supported platforms, and integration with adjacent areas. In a specific architecture, ReBAC may be a standalone platform, a capability, or part of a broader solution.
How To Assess The Technology
When selecting a solution, the most important assessment points are:
- which problem the solution covers and where its boundaries are
- whether it supports the organization's existing environment
- how it integrates with SIEM, SOAR, XDR, IAM, cloud, or ticketing
- what level of automation, reporting, and auditability it provides
- whether it reduces operational complexity or only adds another isolated console
Related Areas
Vendors From The SecTec Portfolio
Attack coverage and defensive context
MITRE ATT&CK® Enterprise version 19.1 is used as a reference model. The mapping is a SecTec expert interpretation and does not imply endorsement by MITRE.
Practical attack scenarios
- Phishing and identity abuseAn adversary manipulates a user, obtains credentials, or abuses a trusted account to gain access to the environment.
- Cloud and SaaS compromiseAn adversary abuses cloud identities, permissions, configurations, or application integrations to access services and data.
- Supply chain and trusted accessAn adversary abuses a supplier, software dependency, external access path, or trusted relationship to bypass normal controls.
- Business Email Compromise and mailbox takeoverAn adversary takes over or impersonates a trusted email identity and abuses communications for fraud, payment diversion, data collection, or further phishing.
- Privilege escalation and persistenceAn adversary expands privileges, creates or modifies accounts and policies, and establishes repeatable access to systems, identities, or cloud environments.
- Insider threat and authorized access abuseAn insider or an adversary with a valid account abuses legitimate permissions to discover, copy, manipulate, or transfer sensitive data.
Relevant ATT&CK techniques
- T1069 · Permission Groups DiscoveryDetect, Prevent, Respond
- T1078 · Valid AccountsDetect, Prevent, Respond
- T1098 · Account ManipulationDetect, Prevent, Respond
- T1136 · Create AccountDetect, Prevent, Respond
- T1484 · Domain or Tenant Policy ModificationDetect, Prevent, Respond