Threat modeling software features

Threat Modeling Capabilities for Security-Focused Design Decisions

This page covers what Astrix does at each step of a threat model: what you can put in, how it is analyzed, and what you get back. Each feature is labelled to show whether Astrix does the work, assists it, or leaves the decision to your team.

Anatomy of a findingIllustrative example
Denial of service at the API gatewayAn attacker floods the system with requests to exhaust resources.
  1. FrameworkSTRIDE: Denial of service
  2. SeverityCVSS 9.0
  3. WeaknessCWE-400
  4. TechniqueMapped to MITRE ATT&CK
  5. MitigationRate-limit requests per IP at the gateway
  6. Next stepReview, then export as a work item
The example finding comes from Astrix product material. The layout is a conceptual summary, not a product screenshot.

Astrix features in detail

Capability 1

Architecture import

Astrix builds the system model for a threat model from artifacts your teams already maintain, or from a written description when no artifacts exist yet.

Why it matters

Redrawing an architecture by hand for every review is slow, and the copy drifts from the real system. Starting from the definitions themselves keeps the model closer to what is actually built.

Supported inputs
OpenAPI / SwaggerTerraformCloudFormationARMKubernetes YAMLVisiodraw.ioDiagram imageGitHub repositoryPlain language
What you receive
A system model ready for analysis.
Automation
Astrix does it parsing and modeling · You decide scope and completeness
Most useful for
Application and solution architects, AppSec engineers

How it works in Astrix

  1. Create a threat model and choose an input.
  2. Upload the file, connect a GitHub repository, or type a description.
  3. Astrix captures the system description, components and data flows, with no manual entry of components.

Capability 2

Framework-specific threat analysis

Astrix identifies threats against the model using the methodology you select. Each of the five supported methodologies has its own dedicated analyzer with purpose-built detection logic.

Why it matters

Different systems call for different methods, and hand-run sessions vary with whoever leads them. A dedicated analyzer applies the chosen method the same way each time.

Methodologies
STRIDEPASTAVASTSAIFMAESTRO
What you receive
A draft, methodology-specific threat model for review.
Automation
Astrix assists drafting · You decide what to accept
AI provider options
An enterprise AI service hosted in the EU by default. Other providers only on written request; dedicated deployments can use your own AI service.

How it works in Astrix

  1. Select STRIDE, PASTA, VAST, SAIF or MAESTRO.
  2. The analyzer generates a draft threat model. By default this is AI-assisted, using an enterprise AI service hosted in the EU, behind multiple guardrail layers; with no AI provider configured, a built-in rule engine runs the analysis inside Astrix.
  3. Your reviewers accept, adjust or reject each result. Re-run the analysis whenever the model changes.

Capability 3

Scored findings and prioritization

Every finding is enriched with standard severity and classification data and specific mitigation guidance, and findings can be viewed together on a severity-by-likelihood heat map.

Why it matters

A list of threats without severity or context leads to debate about what to fix first. Standard identifiers give security, engineering and risk teams the same vocabulary.

What you receive
Findings that can be ranked, compared and acted on, plus a heat map of where they cluster.
Most useful for
AppSec teams, security architects, risk and governance teams

Scores and mappings support your reviewers' judgment; they do not replace it.

How it works in Astrix

  • CVSS scoreSeverity for each finding.
    Astrix does it
  • CWE identifierThe underlying weakness.
    Astrix does it
  • MITRE ATT&CK mappingThe attacker technique involved.
    Astrix does it
  • Mitigation guidanceA specific recommended fix for each finding.
    Astrix does it
  • PrioritiesAgreeing which findings to address first.
    You decide

Capability 4

Attack path visualization

Astrix maps how threats connect across the model as a graph. Kill-chain analysis places threats along the stages of an attack, and lateral-movement detection shows how an attacker could move between components.

Why it matters

Weaknesses that look minor alone can combine into a serious path. Seeing the chain helps teams find the controls that break several paths at once.

Views
Attack path graphKill-chain stagesLateral movementHeat map
What you receive
A visual of entry points, paths and the assets they lead to.
Automation
Astrix does it mapping · You decide which paths to break

Capability 5

Compliance gap analysis

Astrix maps each identified threat to the control it affects in seven regulatory and security frameworks, and highlights the controls where threats create gaps.

Why it matters

In regulated environments, a design-level threat is also a question about control coverage. Mapping the two together lets security and compliance teams discuss the same findings.

Gap analysis shows where threats affect controls. It is not an audit, a certification or a guarantee of compliance.

Frameworks
HIPAAGDPRPCI DSSSOXFISMANIST SP 800-53ISO 27001
What you receive
A view of which controls are affected by which threats.
Automation
Astrix does it mapping · Outside Astrix formal compliance assessment

Capability 6

Remediation, reporting and handoff

Astrix moves reviewed findings into the tools where engineering work happens, keeps a record of their status, and produces reports for people who do not use the platform.

Why it matters

Findings left in documents rarely get fixed. Each threat needs an owner, a ticket and a record of what was decided.

Destinations
JiraGitHub IssuesAzure DevOpsSlackMicrosoft TeamsEmail
Report formats
PDFDOCX
Most useful for
Engineering and DevSecOps teams, security leaders, review boards

Exports are customer-initiated: your organization configures and authorizes each integration.

How it works in Astrix

  • Work-item exportPush selected findings to Jira, GitHub Issues or Azure DevOps.
    You choose what
  • NotificationsAlert Slack or Microsoft Teams channels.
    Astrix does it
  • Remediation trackingStatus for each finding, kept in an append-only log.
    Astrix records
  • ReportsExport threat models and reports as PDF or DOCX, or schedule them by email.
    Astrix does it
  • Implementing fixesChanging code, configuration or infrastructure.
    Outside Astrix

Capability 7

Collaboration, access and model history

Teams work on threat models together with controlled access, and the platform keeps a history of how each model changes.

Why it matters

A threat model holds sensitive design information and changes as the system does. Access, discussion and history need to be part of the tool, not an afterthought.

What you receive
A shared, access-controlled threat model with a reviewable history.
Most useful for
Security teams working across several engineering teams, and consultancies managing client organizations
Plans
Starter, Professional and Enterprise, with usage limits (such as models, members and snapshots) that differ by plan

How it works in Astrix

  • Per-model roles and teamsOwner, editor and viewer roles, teams, and expiring share links.
    You assign
  • Real-time editing and commentsWork on a model together and discuss findings in threads.
    Astrix assists
  • Audit trailChanges and admin actions recorded, viewable by your admins.
    Astrix does it
  • Snapshots and re-analysisKeep earlier versions; re-analyze when the design changes.
    You trigger
  • Sign-in and organization adminOpenID Connect SSO, multi-factor authentication, organization and partner administration.
    You configure

Threat modeling workflow

Who does what, step by step

How the features fit together in one engagement, split into what Astrix does, what your practitioners decide, and what happens outside the platform.

Step 1Context

Astrix doesImports artifacts or reads the description
You decideScope, and which artifacts to use
Outside AstrixGather current design documents

Step 2Model

Astrix doesCaptures components and data flows
You decideConfirm the model is complete and where trust boundaries sit

Step 3Analyze

Astrix doesRuns the selected framework's analyzer
You decideChoose the framework; review the draft

Step 4Prioritize

Astrix doesScores, maps, builds attack paths and gap views
You decideAccept, adjust or reject; agree priorities
Outside AstrixFormal risk acceptance in your governance process

Step 5Act

Astrix doesExports work items, notifies, tracks status
You decideWhat to export and who owns it
Outside AstrixImplement fixes in code and infrastructure

Step 6Maintain

Astrix doesKeeps snapshots and produces reports
You decideWhen to re-analyze after a change
Outside AstrixSecurity testing of the implementation

Inputs, analysis and outputs

What goes in, what happens, what comes out

Inputs

  • API definitions: OpenAPI / Swagger
  • Infrastructure-as-code: Terraform, CloudFormation, ARM, Kubernetes YAML
  • Diagrams: Visio, draw.io, architecture images
  • Source: GitHub repositories
  • Text: a plain-language system description

Analysis

  • Astrix does itSystem modeling from your inputs
  • Astrix assistsThreat identification by the selected analyzer: AI-assisted by default, or by the built-in rule engine
  • Astrix does itScoring, CWE and ATT&CK mapping, attack paths and compliance mapping
  • You decideReview, acceptance and prioritization of every finding

Outputs

  • Findings with scores, mappings and mitigation guidance
  • Views: attack paths, heat maps, compliance gaps
  • Work items in Jira, GitHub Issues or Azure DevOps
  • Reports in PDF or DOCX, on demand or scheduled
  • History: snapshots, remediation log, audit trail

Feature-to-value mapping

From feature to practical value

Astrix capabilities, what users can do with them, and why it matters
CapabilityWhat you can doWhy it matters
Architecture importStart a model from existing specs, IaC or diagramsHelps keep the model close to the real system
Framework analyzersApply the right methodology to each systemSupports consistent analysis across reviewers
Scored findingsRank threats with CVSS, CWE and ATT&CKCan improve clarity when agreeing priorities
Attack pathsSee how weaknesses chain togetherHelps target controls that break several paths
Compliance gapsSee which controls a threat affectsConnects design risk to control coverage
Remediation handoffSend findings to engineering trackers and record statusGives each threat an owner and a history
Collaboration and historyReview together, with roles, comments and snapshotsKeeps the model current and its changes reviewable

Designed for security and engineering teams

The capability each team relies on most

  • Application security

    Framework analyzers and scored findings, to scale reviews beyond a few experts.

  • Security architects

    Attack path visualization, for reasoning across components and boundaries.

  • Engineers and architects

    Architecture import and work-item export, so security fits existing artifacts and trackers.

  • Security consultants

    Organization and partner administration, plus PDF and DOCX deliverables.

  • Security leaders

    Consistent scoring, compliance gap views and reports across teams.

For scenario-by-scenario detail, see threat modeling use cases by role.

Product scope

What is available, and what to confirm

A clear line between current features, practitioner judgment, and questions worth raising in a demo.

Available today

  • The seven capability groups on this page
  • Five framework analyzers
  • The listed inputs, integrations and report formats
  • Starter, Professional and Enterprise plans

Requires your judgment

  • Scope and completeness of each model
  • Accepting, adjusting or rejecting findings
  • Risk acceptance and priorities
  • Implementing and testing fixes

Confirm during a demo

  • How repository import works for your codebases
  • Integrations beyond those listed on this page
  • Hosting outside the EU (dedicated deployments on request)
  • Plan limits for your expected usage

Astrix analyzes the designs and definitions you provide. It does not scan live cloud accounts or running systems, and it does not replace security testing.

Security and privacy

How your design data is handled

A summary for evaluators. Status labels and further detail are on the platform security overview.

  • Isolated per customer. Each organization has its own dedicated database.
  • Limited AI data. Only the system description, components and data flows are sent for analysis; never identities, evidence files or credentials.
  • No training on your data. Neither Astrix nor its default AI provider trains models on your content.
  • Encrypted. In transit and at rest, using industry-standard encryption.
  • Access control. SSO via OpenID Connect, MFA, role-based access and audit logs.
  • EU hosting. Hosted in the EU on enterprise-grade cloud infrastructure.

Resources

Features and capabilities FAQ

What capabilities does Astrix provide for threat modeling?

Seven groups:

  • architecture import
  • framework-specific threat analysis
  • scored findings and prioritization
  • attack path visualization
  • compliance gap analysis
  • remediation, reporting and handoff
  • collaboration, access and model history

See the capability overview.

Does Astrix automate threat identification?

Partly. The selected framework's analyzer generates a draft threat model, AI-assisted by default or using a built-in rule engine. Astrix then scores and maps each finding. The output is advisory: your reviewers accept, adjust or reject each finding and decide priorities. See who does what.

Which threat modeling methodologies are supported?

STRIDE, PASTA, VAST, SAIF and MAESTRO, each with a dedicated analyzer.

What inputs can users provide, and what outputs are available?

Inputs: OpenAPI/Swagger, Terraform, CloudFormation, ARM, Kubernetes YAML, Visio, draw.io, architecture images, GitHub repositories and plain-language descriptions.

Outputs:

  • scored findings with mitigation guidance
  • attack paths, heat maps and compliance gap views
  • work items in Jira, GitHub Issues or Azure DevOps
  • PDF and DOCX reports

See inputs and outputs.

How does Astrix fit into an application or security architecture review?

It provides the threat model the review works from, along with comments, roles, attack paths and reports to support the discussion. Decisions stay with the reviewers. Read the design review use case.

Which integrations does Astrix support?

Work-item export to Jira, GitHub Issues and Azure DevOps, notifications to Slack and Microsoft Teams, email reports, and GitHub repository import. If you need another integration, confirm it with the Cognexaa team before relying on it.

How can an organization evaluate Astrix?

Use the demo request form, or email sales@cognexaa.com to book a demo using one of your own systems. Bring the questions listed under "Confirm during a demo".

See Astrix in action

Explore the current Astrix experience and assess how its threat modeling capabilities fit your security design workflow.

sales@cognexaa.com · Read the platform overview