On the Radar is a real time visibility platform that helps organizations track digital assets, user activity, and potential risks across multiple environments. Many security and operations teams rely on it to maintain continuous monitoring and rapid response.
Ownership structure, deployment model, and data governance shape how the platform is used and governed across enterprise and public sector organizations.
| Platform Name | Type | Deployment Model | Primary Owner Entity | Key Governance Controls |
|---|---|---|---|---|
| On the Radar | Visibility & Monitoring | SaaS and On Prem | Platform Vendor + Customer Security Team | RBAC, Data Residency, Audit Logs |
| On the Radar Enterprise | Visibility & Monitoring | Hybrid | Customer Organization | Custom Policies, Encryption, SSO |
| On the Radar Cloud | Visibility & Monitoring | Public Cloud | Cloud Provider & Vendor | Shared Responsibility, Compliance Certifications |
| On the Radar Community | Visibility & Monitoring | SaaS | Vendor Managed | Standard SLAs, Role Based Access |
Ownership Model and Governance
Understanding who owns on the radar requires examining contractual terms, data residency rules, and operational responsibilities. Enterprise agreements often define roles for configuration, oversight, and incident handling.
Governance committees within customer organizations approve policies that control access scope, retention periods, and integration depth across security tools and business systems.
Deployment Architecture and Infrastructure
Hosted vs Self Managed Installations
The deployment model influences performance, compliance, and long term maintenance. Hosted options reduce local operational load, while self managed setups provide greater control over data flow and tuning.
Infrastructure decisions include networking, storage, logging, and failover design, which determine how well the platform scales with growing asset inventories and event volumes.
Compliance, Data Privacy, and Risk Management
Regulatory Alignment and Controls
Platform usage must align with industry regulations, regional laws, and internal risk policies. Mapping data handling processes to frameworks such as GDPR, HIPAA, or NIST supports audit readiness.
Continuous review of access scopes, retention settings, and integration points reduces exposure and supports responsible monitoring across distributed environments.
Operational Management and Support
Support Models and Service Ownership
Clear support tiers define response times, escalation paths, and ownership for troubleshooting. Service level agreements specify uptime guarantees and maintenance windows that affect monitoring reliability.
Operational playbooks, runbooks, and training ensure that customer teams can manage integrations, interpret alerts, and maintain visibility over evolving infrastructures.
Key Recommendations and Next Steps
- Review contractual ownership clauses and data rights in every agreement.
- Map deployment options to compliance requirements and risk appetite.
- Define roles for configuration management, monitoring, and incident response.
- Establish clear support expectations and service level agreements with the vendor.
FAQ
Reader questions
Who retains ownership of collected telemetry and configuration data?
The customer organization typically retains ownership of its telemetry and configuration data, while the vendor may process it under defined service terms to deliver platform functionality.
Can an enterprise fully host On the Radar on its own infrastructure?
Yes, enterprise deployments can be self hosted, allowing full control over infrastructure, data storage, network routing, and integration with on premises security tools.
How are updates, patches, and feature releases managed across different ownership models?
Vendor managed updates apply to hosted and community tiers, while enterprise deployments often coordinate change windows, testing, and validation through internal release management processes.
What happens to ownership and access when a contract with the vendor ends?
Contract terms typically define data export procedures, continued access windows, and migration support to help the customer transition to alternative solutions without disruption.