SBOM & vulnerability viewer
Explore a product's components, filter its CVEs, and mark what's actually exploitable with VEX.
Miftuħ demo → InteractiveTħejjija għas-CRA score
Tick off the essential requirements and watch a deterministic readiness score move in real time.
Miftuħ demo → InteractiveWhich CRA class are you?
Answer three questions about your product and see whether the CRA treats it as default, important, or kritiku — and what that means.
Miftuħ demo → WalkthroughGenerating a CRA dossier
How SBOMs, scans, and decisions compile into audit-ready technical documentation.
Miftuħ demo → WalkthroughThe CRA incident-reporting clock
24 hours, 72 hours, 14 jiem — the early-warning and notification deadlines when an exploited flaw is found, and what each one needs.
Miftuħ demo → WalkthroughSecure-by-default, requirement by requirement
The CRA's essential product requirements — no default passwords, least privilege, secure updates — as a checklist you can actually work.
Miftuħ demo → ScenarioScenario: responding to a new CVE in minutes
A kritiku vulnerability drops at 9am. Follow the trail minn alert to a customer-ready answer.
Miftuħ demo → ScenarioScenario: answering a security questionnaire
The enterprise questionnaire that used to take a week — answered minn a living evidence log.
Miftuħ demo → ScenarioScenario: when an open-source dependency goes dark
A core library's sole maintainer disappears. Manage the CRA risk of unmaintained components without panic.
Miftuħ demo → ScenarioScenario: choosing your conformity route
Self-assessment or a notified body? Walk the decision the CRA forces on you, and what each path costs in time and proof.
Miftuħ demo → InteractivePjan your CRA support window
Set your product's expected lifetime and see the support period the CRA obliges you to cover.
Miftuħ demo → WalkthroughA CRA-grade patch process
Monitor, assess with VEX, remediate, and ship a signed update — with SLAs that scale by severity.
Miftuħ demo → WalkthroughStanding up coordinated disclosure
security.txt, intake, triage, and researcher comms — the disclosure process the CRA expects.
Miftuħ demo → WalkthroughSBOM generation in CI/CD
Wire CycloneDX generation into the pipeline so every build emits a current SBOM that feeds monitoring.
Miftuħ demo → WalkthroughGoverning third-party components
Inventory, license and maintenance health, and a policy gate before a dependency ever ships.
Miftuħ demo → ScenarioScenario: ending support the CRA way
A product reaches end-of-life. Notify users, ship the last update, and close out the support period on record.
Miftuħ demo → ScenarioScenario: a poisoned dependency
A popular package ships a malicious version. Detect espożizzjoni minn the SBOM, contain, and communicate — calmly.
Miftuħ demo → ScenarioScenario: a CRA conformity audit
The auditor arrives. Walk them minn SBOM to VEX to dossier — every claim traceable to evidence.
Miftuħ demo → ScenarioScenario: documenting a risk acceptance
A low-severity flaw won't be fixed before release. Record a defensible, time-boxed acceptance with sign-off.
Miftuħ demo → ScenarioScenario: does the CRA apply to your OSS?
Walk the open-source exemptions and the steward-vs-manufacturer line to a clear yes or no.
Miftuħ demo →