FAQ
Answers for evaluating Continuum.
Questions that come up after reviewing the platform, security posture, and AI approach, organized by what you're trying to confirm before an evaluation.
Continuum is
- Security Command Platform
- Connected operating context
- Assurance and decision layer
- Governed operating model
Continuum is not positioned as
- SIEM
- Vulnerability scanner
- Ticketing system
- Traditional GRC platform
01 / Product
What Continuum is and where it fits.
What is Continuum?
Continuum is a Security Command Platform that connects cybersecurity risk, compliance assurance, audit evidence, third-party risk, AI governance, ownership, and business context around a shared operating model. The purpose is to keep the context behind security and assurance decisions connected rather than reconstructed separately for each workflow.
What does "Security Command Platform" mean?
It means Continuum creates connected operating context rather than a single dashboard or isolated workflow. Assets, risks, controls, evidence, ownership, business processes, and decisions can be understood through the relationships between them, so fragmented security information becomes actionable decision context.
Is Continuum a GRC platform, SIEM, vulnerability scanner, or ticketing system?
Continuum is not positioned as a SIEM, vulnerability scanner, or ticketing system. It is a Security Command Platform designed to connect risk, assurance, evidence, business context, ownership, and governance across the workflows that need them.
It overlaps with some concerns traditionally associated with GRC, but its scope is broader than a compliance or risk register.
What does Continuous Security Assurance mean?
Continuous Security Assurance means maintaining a current understanding of security state, evidence confidence, control posture, risk exposure, and ownership as normal operating context rather than reconstructing them only when an audit or review requires it.
It does not mean every control is automatically and continuously tested or that all evidence is collected without review.
02 / Operating model
How connected context works.
What does "connected context" mean in practice?
The same underlying facts remain connected across different purposes. Asset ownership, control relationships, evidence, dependencies, risk context, and decision history do not need to be reconstructed from scratch every time work moves between risk review, assurance, audit, or reporting. That connected context helps teams understand impact, prioritize risk, support assurance, and make more informed decisions.
Does Continuum require moving all enterprise data into one system?
Continuum is not designed as a universal enterprise data warehouse and does not replace enterprise systems of record. It creates a security decision model from relevant relationships across existing environments, rather than assuming every enterprise dataset belongs in one system.
How does Continuum handle evidence and audit readiness?
Evidence remains connected to the controls, obligations, and assurance activity it supports. Freshness, review status, reuse, and audit context help teams understand whether evidence is still useful and where it supports assurance work.
Does every framework have the same level of support?
No. Support depth varies by framework and version, described in four stages: Catalogued, Mapped, Evidence-aware, and Assurance-ready.
These stages describe depth of support, not certification.
03 / Security and trust
AI boundaries, evidence integrity, and accountability.
What is Continuum AI?
Continuum AI is AI-powered security and assurance assistance inside governed Continuum workflows. It works from connected operating context so it can help explain evidence, controls, risk, and review paths while human review and accountability remain in place.
What is the difference between Continuum AI and AI Governance?
Continuum AI assists work inside the platform. AI Governance governs the AI systems an organization operates or relies on.
They address different problems, even though both operate within the wider Continuum model.
Does AI make security or governance decisions?
No. Continuum AI assists work inside the platform, but security and governance decisions remain owned by accountable people and governed workflows.
Can AI processing stay inside a controlled deployment boundary?
Continuum can support deployment patterns where AI processing remains within a controlled environment. The applicable deployment boundary depends on the specific environment and configuration.
04 / Security and deployment
How platform security is approached and reviewed.
How does Continuum approach platform security?
Continuum is designed around governed access, reviewable workflows, traceable evidence, traceable decisions, and human accountability. Security-sensitive behavior is also subject to verification as the platform evolves.
How are sensitive actions and accountability handled?
Sensitive actions remain connected to role, context, workflow, review state, business impact, and outcome. Accountability stays with accountable people rather than being separated from the action or delegated to an automated decision process.
Can deeper security or deployment architecture be reviewed?
Yes. Deeper implementation and deployment detail can be reviewed through a Security & Deployment Brief during a focused evaluation rather than being published on the public site.
Are internal security test details public?
No. The public site describes security verification as an ongoing discipline, including areas such as authorization boundaries, workflow behavior, evidence integrity, and failure behavior. Specific test inventories, procedures, and findings are not published publicly.
05 / Environment fit
How Continuum fits an existing environment.
Does Continuum integrate with existing security tools?
Continuum is designed around connected operating context, so relevant signals from existing tools can support risk understanding, assurance, and security decision-making. Integration availability depends on the specific system, deployment context, and current product scope, so requirements should be confirmed during an evaluation.
Do we need to replace our current security stack?
No. Continuum is intended to work as a connected assurance and decision layer rather than requiring wholesale replacement of an existing security stack. The goal is to connect technical issues, affected assets and processes, business impact, risk understanding, and decisions where relevant to the evaluation scope.
06 / Evaluation and next steps
How to evaluate Continuum at its current stage.
Is every capability described on the site already complete?
No. The site describes both current platform capabilities and the direction Continuum is being developed toward. Forward-looking areas are identified as platform direction rather than assumed to be complete today. A briefing can clarify the current scope relevant to a specific evaluation.
How should we evaluate Continuum?
Start with the Platform overview and the capability page closest to your priority. A focused briefing can then walk through the connected model, current product scope, security posture, and relevant deployment considerations in the context of your environment.
See Continuum
Still have a question about how Continuum fits your environment?
Request a briefing and we'll walk through how the connected model, security posture, and AI approach apply to your evaluation.