Understand how Raptor Comply organizes your NERC compliance data into facilities, control centers, cyber systems, and cyber assets.Raptor Comply organizes your NERC compliance data into a structured hierarchy of infrastructure resources. At the top sit Facilities and Control Centers - the physical and operational anchors of your NERC-registered footprint. Below them, Cyber Systems group logically related assets, and Cyber Assets represent the individual devices and software instances you track day-to-day. Understanding this hierarchy helps you navigate the API and build integrations that accurately reflect your compliance posture.
Infrastructure resource types
Facilities
A Facility represents a physical or logical NERC-registered site - a substation, generation plant, transmission station, or similar entity. Facilities are the top-level entity in most Raptor Comply workflows. Nearly everything else - cyber systems, cyber assets, evidence, tasks, and training assignments - can be anchored to a facility. When you query the API, filtering by facility is usually the most direct path to the data you need.Control Centers
A Control Center represents an operational control center that oversees one or more facilities. Control centers can be assigned to or unassigned from facilities, and they can own their own cyber systems and cyber assets independent of any single facility. If your organization operates an Energy Management System (EMS) or a SCADA environment that spans multiple sites, those are typically modeled as control centers in Raptor Comply.Cyber Systems
A Cyber System represents a BES Cyber System (BCS) as defined under NERC CIP. Each cyber system belongs to either a facility or a control center, and it acts as a logical grouping that collects the cyber assets subject to the same CIP impact classification. When you classify assets as High, Medium, or Low impact under CIP-002, you do so at the cyber system level.Cyber Assets
A Cyber Asset is an individual device, software instance, or logical element classified under a parent cyber system. This is the most granular infrastructure resource in Raptor Comply - firewalls, historians, workstations, PLCs, switches, and similar OT/IT components all live here. Cyber Assets are the only infrastructure resource with full create, update, and delete access via the API today, which makes them the right integration point for keeping your CMDB or asset inventory in sync with Raptor Comply.Resource hierarchy
API access by resource
| Resource | API Access | Available endpoints |
|---|---|---|
| Facilities | Read | GET /facilities, GET /facilities/{id} |
| Control Centers | Read | GET /control-centers, GET /control-centers/{id} |
| Cyber Systems | Read | GET /cyber-systems, GET /cyber-systems/{id} |
| Cyber Assets | Full CRUD | GET, POST, PATCH, DELETE on /cyber-assets and /cyber-assets/{id} |
Compliance resources
Sitting above the infrastructure layer, Raptor Comply also manages a set of compliance resources: Policy Documents, Evidence, Tasks, and Training (modules and assignments). These higher-level objects reference infrastructure resources - for example, a task may be scoped to a specific facility, or evidence may be attached to a cyber system. API access to compliance resources is rolling out progressively; see the API Reference for current availability.Create, update, and delete operations for Facilities, Control Centers, and Cyber Systems are coming soon. Today those resources are read-only via the API. Full CRUD for these resource types will be available in an upcoming release.