Deployment / Your operational boundary
CENTARGUS is designed so core detection, investigation, and approval can run on-premises or fully air-gapped. The essential workflow does not require a continuous public-cloud connection.
Explore deployment options
Designed around the boundary
you need to protect.
Choose an operating environment
Select a deployment context to explore how connectivity changes while investigation, approval, and evidence remain centered on your environment.
Use existing identity and telemetry where egress is allowed. Keep the approval record in your environment while planning connectivity around your organization’s requirements.
Run CENTARGUS beside the systems it protects. This deployment is designed for organizations whose data residency and operational control requirements keep security operations on site.
Core operations are designed to run without runtime calls to public model services. Intelligence and models are maintained on media your organization controls.
On-premises / Conceptual workflow
Conceptual view of the public deployment options. A briefing establishes the requirements for your environment; this diagram is not an implementation topology.
| Planning consideration | Connected enterprise | On-premises | Air-gapped |
|---|---|---|---|
| Connectivity | Permitted by organizational policy | Core operations do not depend on a continuous public-cloud connection | No runtime calls to public model services |
| Operational focus | Existing identity and telemetry | Data residency and local control | Isolated operations and controlled updates |
| Human approval | Within the organization’s workflow | Within the organization’s workflow | Within the organization’s workflow |
| Key briefing topic | Allowed sources and connections | Infrastructure and operating ownership | Update media and acceptance process |
Prepare for the briefing
Explore the four conversations that shape a useful deployment discussion. Bring your constraints, operating responsibilities, and review expectations.
Map where your telemetry already lives and what must never leave the site. The useful starting point is your operational boundary and its owners.
Questions to bringName the systems that keep care or operations moving. Agree on which workstations, services, and control systems must not be isolated automatically.
Questions to bringPlan who reviews recommendations across shifts. A human approval step needs an accountable owner and a practical handover process.
Questions to bringDefine what the oversight process needs after an incident. Make the decision, supporting evidence, and rationale part of the discussion from the beginning.
Questions to bringYour constraints belong in the conversation
A focused briefing connects the deployment context to the systems you protect and the people who authorize response.
