Starting data
Inventories, SBOMs, and exports from your tools establish which software and versions to track. We identify gaps and the additional information needed.
An agreed tracking scopeLoading page…
Platform & data control
See affected components, remediation priorities, and evidence of fixes in one place. Discover how your inventories become cases your teams can act on.
Tools prepare and correlate information. Assessment remains human, you retain the decisions, and your authorised teams implement fixes.
Products, versions, systems, owners and constraints.
An agreed scope and clear responsibilities.SBOMs, inventories and authorised results. An SBOM is a software bill of materials.
Identified data with explicit coverage limits.Vendor advisories, vulnerability databases, CERT notices and exploitation information.
Dated references and contradictions to examine.Component, version, distribution, configuration, exposure and business impact.
A justified human conclusion, or information to obtain.Owners, deadlines, dependencies, workarounds and exceptions.
An action plan for teams authorised to implement fixes.Post-change checks, history and available evidence.
Progress information usable in reviews and decisions.The same case can have different conclusions across deployed versions. Choose a version, then a case to follow the reasoning.
Example workflow
Démo-Transit · 1.2-démo
The fictional Demo Portal 1.0 inventory contains Demo-Transit 1.2-demo.
Prepare the update and verify deployment for this version.
The verified fix in version 1.1 does not close the occurrence in version 1.0.
Accepted risk is a decision about residual risk, not a fix. “In progress” describes the action, not the disappearance of the vulnerability.
Consolidation limits repeated checks. Version tracking distinguishes fixes, affected deployments and missing evidence. An action plan links owners, deadlines and dependencies, while history supports reviews.
Components, observed versions, sources and coverage to complete.
Applicability, context, sources, reasoning and retained uncertainties.
Owner, deadline, status and dependencies for each action.
Documented end-of-support dates and migrations to plan.
Priorities, blockers, decisions and available verification evidence.
Reusing your tools can avoid unnecessary replacement. Benefits are measured within your scope: reusable capacity is not automatically a cash saving. Self-hosting also requires operations, backups and maintenance.
Assess value using your assumptionsWe agree on the data needed, where it is processed, who can access it, and who receives reports. Your exports can support tracking without direct access to your network.
Inventories, SBOMs, and exports from your tools establish which software and versions to track. We identify gaps and the additional information needed.
An agreed tracking scopeA guided walkthrough shows how to assess an alert, plan an action, and verify the result. The presentation focuses on your technical questions and reporting needs.
Assessment, actions, and evidenceAnalysis takes place in the environment agreed with you. Access, data exchanges, and report delivery follow your organization's confidentiality requirements.
Reports for authorized recipientsPublic sources → authorised knowledge updates → processing environment.
Authorised customer inventories → agreed environment → decisions and reports for authorised recipients.
You retain control of access and the information you share.
A self-hosted tool may call analysers, download databases or send telemetry. An external request containing a package name, PURL or version can already reveal part of an inventory.
Flows must be identified and authorised. Local databases or mirrors can limit external requests where supported. Offline operation depends on preloaded resources and database freshness; notifications receive no confidential data by default.
Inventory, component analysis, monitoring, and action tracking: each tool contributes to a specific deliverable. We select the integrations that fit your scope and existing tools.
Tools are selected according to your hosting needs and their licenses. n8n Community is distributed under the Sustainable Use License.
Access, flows, history and recovery structure operations and the checks to maintain. Engagement arrangements are defined for your environment.
Named accounts, least privilege and tests of allowed and denied access.
Observe exchanges, remote analysers and telemetry before validation.
Useful history and restricted log access, with no secrets in logs.
Tracked versions, separate backups and a restoration exercise.
AI helps prepare summaries and relate information. The consultant still verifies sources, applicability and decisions. The choice of a local model or external service depends on confidentiality rules and authorised flows.
Each conclusion remains linked to its sources. The consultant reviews AI suggestions before including them in priorities and reports.
The SOC laboratory illustrates triage of a test event. Vulnerability management tracks vulnerabilities and their treatment; detection examines events that may indicate suspicious activity.
A test machine produces a benign event.
Configured collection sends it to the detection engine.
A rule produces an alert to examine.
Asset and vulnerability context enriches the case.
The consultant assesses the case and records a test response procedure.
Vulnerability monitoring and detection answer complementary questions: which components need fixing, and which events need investigation. Continuous SOC monitoring is a separate service.
With Wazuh, events are linked to the asset and affected components to support investigation and action tracking.
Our service covers vulnerability monitoring, assessment, and remediation tracking. A demonstration can also show how detection alerts relate to affected components. A 24/7 SOC service is a separate engagement.
In your environment or on dedicated professional infrastructure, as agreed with you. Processing location, access, and data exchanges are defined before the engagement.
We start with your available inventories, SBOMs and tools. Useful interfaces are assessed in context. Any new component must address a defined need.
Authorised exports can support tracking without direct network access. Public sources require controlled updates; offline work depends on preloaded data and its freshness.
The choice of local execution or an external service depends on the data and authorised flows. For an engagement, tools, data processing and transfers are agreed before processing.
Coverage depends on inventories, artefacts, sources, versions and methods. Uncertain cases remain visible and require human verification.
Follow an alert through to resolution: affected versions, assessment based on sources, priority, action, and evidence of the fix. We tailor the walkthrough to the questions your technical teams and leadership need answered.
Tracking supports relevant processes and evidence within the applicable scope. A toolchain alone does not demonstrate overall organisational or product compliance.
Available inventories, versions to track, confidentiality and expected reports: a few lines are enough to prepare a conversation.