System context
- Responsible for
- Capturing what you are building.
- Uses
- API specs, IaC, diagrams, repositories or a written description.
- Gives you
- A system model with components and data flows, without re-entering it by hand.
- Workflow stage
- Steps 1–2
Platform overview
Astrix is threat modeling software that takes the architecture your teams already document and turns it into a structured, scored threat model. This page walks through what goes in, what the platform does with it, and what your security and engineering teams get out.
You provide
Astrix
Your teams get
Introduction
Threat modeling is a structured way of asking what could go wrong with a system before attackers find out. Security practitioners often frame it as four questions. They apply to any threat modeling effort, with or without a tool.
Astrix is a threat modeling platform built around those questions. It does not replace your reviewers' judgment. It removes the manual work around them: redrawing architectures, applying a methodology by hand, scoring findings case by case, and chasing mitigations through slide decks.
The table shows where the general practice ends and where Astrix provides specific support.
Platform at a glance
Each area has a distinct job. Together they take a threat model from first import to tracked mitigation.
Core platform capabilities
Six capability groups, each described by the need it addresses, what Astrix actually does, and where it fits in a threat modeling practice. For a feature-by-feature reference, see Astrix features and capabilities.
A · System context
Most threat models start with someone redrawing the architecture by hand, and that copy is out of date the moment the real design moves on.
Astrix starts from artifacts your teams already maintain. It accepts OpenAPI and Swagger definitions; Terraform, CloudFormation and ARM templates; Kubernetes YAML; Visio and draw.io diagrams; uploaded architecture images; and GitHub repositories. When none of those exist yet, as in early design, you can describe the system in plain language.
B · Threat identification
Teams pick different methodologies for different systems, and results vary with whoever runs the session.
Astrix has a dedicated analyzer for each of five methodologies, each with its own detection logic: STRIDE, PASTA, VAST, SAIF and MAESTRO. You choose the framework and the analyzer generates a draft threat model from the system model.
Analysis is AI-assisted. By default it runs on an enterprise AI service hosted in the EU, and each request passes multiple guardrail layers before and after the model call. If no AI provider is configured, a built-in rule engine runs the analysis inside Astrix. Either way, the output is advisory: your reviewers accept, adjust or reject it.
C · Threat assessment
A long list of threats without severity or context leaves teams arguing about what to fix first.
Each finding Astrix produces carries a CVSS score, a CWE identifier for the underlying weakness, a MITRE ATT&CK mapping for the attacker technique, and specific mitigation guidance. Severity-by-likelihood heat maps show where findings cluster across the model.
For regulated environments, compliance gap analysis maps threats to the controls they affect in HIPAA, GDPR, PCI DSS, SOX, FISMA, NIST SP 800-53 and ISO 27001. This shows where threats touch your control set. It is not an audit, a certification or a guarantee of compliance.
D · Threat analysis
Individual findings rarely show how an attacker could chain weaknesses together to reach something valuable.
Astrix maps attack paths as a graph, with kill-chain analysis that places threats along the stages of an attack, and lateral-movement detection that shows how an attacker could move between components after gaining a foothold.
E · Mitigation planning
Findings recorded in documents tend to stall: no owner, no ticket and no record of what was decided.
Every finding comes with specific mitigation guidance. You can export selected findings as work items to Jira, GitHub Issues or Azure DevOps, and track remediation status in Astrix, where changes are kept in an append-only remediation log. Slack and Microsoft Teams notifications keep the right people informed.
Astrix documents and tracks mitigation decisions. It does not change your systems or apply controls itself; your teams do that through their normal delivery process.
F · Collaboration and ongoing review
A threat model is only useful if the right people can work on it and it keeps pace with the design.
Each threat model has owner, editor and viewer roles. You can organize users into teams and share models with expiring links. Teams edit together in real time, discuss findings in comment threads, and every change is recorded in an audit trail.
When the architecture changes, re-analyze the model and keep snapshots of earlier versions. Export threat models and reports as PDF or DOCX, or schedule reports by email for stakeholders who do not use the platform.
Threat modeling workflow
The threat modeling workflow Astrix supports, stage by stage. Not every stage is automated: each row shows what your team does and what Astrix provides.
Decide what is in scope: the application, its components and its boundaries.
Your team
Chooses the system and supplies specs, IaC, diagrams, a repository or a description.
Astrix
Imports those artifacts and captures the system description and components.
Understand how information moves and where security assumptions change.
Your team
Checks that the model is complete and confirms where data crosses trust boundaries.
Astrix
Represents the data flows between components as part of the threat model.
Apply a methodology to find what could go wrong.
Your team
Selects the framework that fits the system and reviews the draft threats.
Astrix
Runs the dedicated analyzer for that framework to generate a draft threat model.
Decide which threats matter and how much.
Your team
Accepts, adjusts or rejects findings and agrees priorities.
Astrix
Provides CVSS scores, CWE and ATT&CK mapping, heat maps, attack paths and compliance gaps.
Act on findings and keep the model current.
Your team
Owns and implements mitigations, and re-runs the review when the design changes.
Astrix
Supplies mitigation guidance, exports work items, tracks remediation, keeps snapshots and produces reports.
Architecture Threat Modeling
Architecture Threat Modeling examines a design before it is deployed: its components, interfaces and dependencies, the data flowing between them, and the trust boundaries those flows cross. It brings out the security assumptions the design depends on, so teams can test them deliberately rather than discover them in production.
In Astrix, the system model holds the components and data flows, the selected framework's analyzer raises threat scenarios against them, and attack path visualization shows how those scenarios connect across the attack surface.
The two complement each other. Threat modeling shapes the design; testing checks the implementation. Astrix supports the first and does not replace the second.
Platform security
A threat model describes how your systems could be attacked, so the platform that holds it must be trustworthy itself. Each item below is labelled with its status: a control implemented in the platform or a documented commitment. We also threat-model our own platform with Astrix.
Each customer organization has its own dedicated database, and organization membership is verified on every request.
Single sign-on via OpenID Connect with your identity provider, multi-factor authentication, and organization, team and per-model roles.
Data is encrypted in transit and at rest using industry-standard encryption.
Hosted in the EU on enterprise-grade cloud infrastructure. Dedicated deployments in other regions are available on request.
Only the system description, components and data flows are sent for analysis, through multiple guardrail layers. Never identities, evidence files or credentials.
Per-organization audit logs that your admins can view, plus security checks on uploaded files.
Neither Astrix nor its default AI provider trains models on your content or outputs.
Export at any time. On exit, data is deleted within contractual timeframes and deletion is confirmed in writing. Breach notification within contractual timeframes.
Security lifecycle
Threat modeling is most valuable during design, and it stays useful as systems change. It complements secure design reviews, application security testing and vulnerability management; it does not replace them.
Describe the planned system in plain language to raise threats early, before the design is fixed.
Import or describe the design, analyze it, and agree mitigations while changes are still cheap.
Mitigations arrive as Jira, GitHub Issues or Azure DevOps work items with guidance attached.
SAST, DAST and penetration testing check the implementation. Findings from the threat model can help focus that testing.
PDF or DOCX reports show which threats were identified, accepted or mitigated.
Re-analyze when the architecture changes, and keep snapshots of earlier versions.
Use cases
Security architect · new customer-facing service
AppSec team · existing system adding a payment provider
Product security · LLM-powered or multi-agent application
Security consultancy or channel partner
What sets Astrix apart
Astrix is a threat modeling platform, not a general security suite. These are the strengths that follow from that focus.
STRIDE, PASTA, VAST, SAIF and MAESTRO each have purpose-built detection logic, including frameworks written for AI and multi-agent systems.
Specs, IaC, diagrams and repositories become the threat model's input, so the model reflects the system as it is defined.
CVSS, CWE and MITRE ATT&CK give security, engineering and risk teams a shared vocabulary, with mitigation guidance attached.
AI output is advisory. Roles, comments, audit trails and remediation logs keep people accountable for every decision.
A database per customer, EU hosting, controlled AI data flow, and no training on customer data.
Capabilities and outcomes
The capability is what Astrix provides. The value is what teams can achieve when they use it as part of their own process.
| Platform capability | What it provides | Potential value |
|---|---|---|
| Architecture import | A system model from specs, IaC, diagrams or a description | Less time redrawing systems, more time reviewing them |
| Framework analyzers | A methodology-specific draft threat model | More consistent analysis across teams and reviewers |
| Scored, mapped findings | CVSS, CWE, ATT&CK and mitigation guidance per finding | Clearer prioritization and communication of design-level risk |
| Attack path visualization | Graph-based paths, kill-chain stages and lateral movement | Better visibility into how weaknesses combine |
| Remediation tracking | Work-item export, status tracking and an append-only log | Visible ownership and history of security decisions |
| Re-analysis and snapshots | Updated models and earlier versions kept for reference | Threat models that keep pace with the architecture |
Astrix supports threat modeling and security design review. It does not eliminate threats, prevent breaches or guarantee regulatory compliance.
Resources
Astrix is threat modeling software from Cognexaa. It builds a threat model from your architecture artifacts, analyzes it with a framework-specific analyzer, and produces scored findings with mitigation guidance that teams can review, track and keep up to date.
The platform covers:
It is offered as Starter, Professional and Enterprise plans. Usage limits differ by plan, and report export is included in all three. Pricing is available on request.
Astrix captures a system's description, components and data flows from what you import or describe, then analyzes that model rather than individual lines of code. Attack path visualization shows how threats connect across components. See the architecture example.
Astrix automates the drafting:
People stay responsible for scope, for accepting or adjusting findings, for agreeing priorities and for implementing mitigations. AI output is advisory. See who does what at each stage.
Five, each with a dedicated analyzer:
No. Threat modeling examines the design; penetration testing, SAST and DAST examine the implementation. Astrix complements those activities and can help focus them on the areas of highest design-level risk. See where Astrix fits.
Each customer organization has its own database, hosted in the EU on enterprise-grade cloud infrastructure. Data is encrypted in transit and at rest. Access is controlled through SSO, MFA and role-based permissions, with audit logs. Only architecture metadata is sent for AI analysis, and customer data is not used to train models. See the security details.
Book a demo by emailing sales@cognexaa.com, ideally with a system you would like to see modeled. The Cognexaa team can also walk your security reviewers through the platform's architecture and controls under NDA.
Explore the platform, understand its capabilities, and evaluate how it could support your security architecture and threat modeling work.
sales@cognexaa.com · Back to the Astrix homepage