RBAC (Role-Based Access Control)
Restricting platform and system access based on a user's organizational role. ORDR implements RBAC to ensure security analysts, clinicians, and administrators work within their appropriate function scope.
What is RBAC (Role-Based Access Control)?
Restricting platform and system access based on a user's organizational role. ORDR implements RBAC to ensure security analysts, clinicians, and administrators work within their appropriate function scope.
Role-Based Access Control (RBAC) restricts system access based on a user's organizational role rather than their individual identity. Users are assigned to roles (e.g., security analyst, clinical engineer, OT operator, administrator); roles are granted permissions to perform specific actions on specific resources. Managing access at the role level simplifies administration: when a user's job changes, their role assignment changes, automatically updating all their permissions without modifying individual access rules.
In connected asset security platforms, RBAC serves two purposes. Externally, it models the correct access boundaries for different stakeholder groups: the security team needs full threat and risk visibility; clinical engineers need device lifecycle and maintenance views; OT operators need process-specific device data; executives need summary reporting. Each group has different information needs and should have access scoped appropriately. Internally, RBAC ensures that the security platform itself is governed with appropriate access controls.
RBAC is distinct from the device-level access control that connected asset security platforms enforce on IoT and OT networks. Platform RBAC governs who can see and configure the security tool. Device access control policies govern what network traffic connected devices are permitted to send and receive. Both are important; they operate at different layers.
Key Facts
- RBAC is required by HIPAA's access control standard and NIST SP 800-53 AC-2 (account management)
- Least-privilege RBAC reduces insider threat risk by limiting unnecessary access to sensitive security data
- Role proliferation (too many specialized roles) is a common RBAC anti-pattern that makes administration complex
- Regular access reviews — comparing assigned roles against current job functions — are required under multiple compliance frameworks
How ORDR Addresses RBAC (Role-Based Access Control)
ORDR implements RBAC across user roles including security analyst, clinical engineer, network administrator, executive viewer, and custom roles. Each role sees the data and capabilities appropriate to their function — clinical engineers see medical device lifecycle and maintenance data without full threat hunting capability; security analysts have full investigation tools; executives see risk trend dashboards.
See ORDR in actionFrequently Asked Questions
Complete visibility across your entire attack surface.
ORDR unifies IT, IoT, and OT asset intelligence so your team can see—and act on—what matters most.