Product

NOXA product scope is presented from implemented runtime behavior.

This page follows repository-backed capabilities and responsibility boundaries across runtime, factory, and packager.

See Editions Trust / Product Chain Documentation Map

Capabilities

Runtime capabilities confirmed in repository documentation

Each capability below is anchored to runtime docs and code paths.

Incident-centric operations

Incidents are the primary operational object, with ticket flows maintained as compatibility paths where needed.

Source: ../Noxa/docs/data-model/incident-model.md

Event normalization and cyber data structuring

Heterogeneous events are normalized into stable operational fields while raw payload access stays controlled and auditable.

Source: ../Noxa/docs/data-model/data-normalization.md

Assets, findings, remediation, and timeline

NOXA links incidents to assets, findings, remediation plans, and timeline events to support coordinated response workflows.

Source: ../Noxa/docs/product/product-vision.md

Connectors and correlation above detection tooling

NOXA integrates with SIEM/EDR/XDR/scanners/webhooks while focusing on correlation, deduplication, and incident operations.

Source: ../Noxa/docs/connectors/siem-connectors.md

MITRE ATT&CK and auditability

MITRE mapping, analyst decisions, enrichment actions, and workflow transitions are expected to remain traceable.

Source: ../Noxa/docs/operations/mitre-integration.md

Offline-compatible AI assistance

AI support is optional, local-first/controlled, and constrained by RBAC, data visibility rules, and trust-chain policies.

Source: ../Noxa/docs/ai/ai-capabilities.md

Boundary

Runtime, Factory, and Packager keep explicit roles

Signing and key generation remain outside runtime; runtime stays verify-only.

NOXA runtime

Responsibilities

Verify signatures and artifact coherence locally.

Enforce edition/capability controls in APIs and services.

Expose diagnostics, production-guard checks, and local audit visibility.

Out of scope

No private-key signing.

No license generation.

No bundle production.

Noxa-License-Factory

Responsibilities

Create and renew licenses with schema governance.

Sign license payloads (detached signature).

Operate license lifecycle views and internal audit trail.

Out of scope

No runtime enforcement.

No product-manifest generation.

No customer bundle assembly.

Noxa-Packager

Responsibilities

Validate license input and edition/module coherence.

Generate signed product-manifest and bundle-manifest assets.

Package install files, checksums, docs, and signed bundle archive.

Out of scope

No runtime enforcement.

No license issuance.

No private keys in frontend.

Continue

Review edition controls, deployment models, and licensing workflow.

Editions Deployment Licensing