Client workspace
Engagements, published findings, remediation, assets, reports, evidence requests, ROSS, team, and settings.
Offensive Security Assurance Platform
From approved scope to verified security evidence.
Benedam is the shared operating layer for clients, BalticSec operators, and Cyberross platform administrators — with each role seeing only the surface it needs.
Lifecycle
A continuous chain of custody for assurance
Every decision and evidence item stays connected to its engagement, asset, finding, remediation, and retest.
- 01
Authorise
Versioned scope, Rules of Engagement, safety limits, and accountable approvals.
- 02
Test
Expert-led manual testing supported by bounded, approved automation.
- 03
Validate
Evidence, exploitability, and impact reviewed before client publication.
- 04
Remediate
Ownership, comments, decisions, deadlines, and integrations in one workflow.
- 05
Retest
Fresh evidence confirms whether the original path is actually closed.
- 06
Prove
Executive, technical, and auditor views generated from the same verified record.
Role-aware
Three operational surfaces, one source of truth
Client-safe activity is separated from operator tradecraft, while the platform control plane remains hidden from ordinary users.
BalticSec operations
Assignment, attack hypotheses, internal notes, finding QA, retests, reports, and engine operations.
Platform control plane
Tenant provisioning, memberships, modules, engine pools, schema status, deployments, backup evidence, and audit events.
Four modules, one model
One model, not a collection of disconnected portals
Read live from the module registry. Penetration Testing ships today; the others say how far along they are and when we expect them, because “coming later” is what a buyer reads as “never”.
Available now
Penetration Testing
Assets, missions, staged automated attack, operator-validated findings, remediation tracking and sealed reports.
In developmentQ4 2026
Red Team Operations
Campaigns against business objectives, ATT&CK-mapped actions, deconfliction, detection scorecards and after-action review.
30% complete. Shared spine ready: assets, findings, evidence, reporting and commerce are module-agnostic. Campaign model designed, not built.
In developmentQ2 2027
Threat Modelling
Architecture versions, components, data flows, trust boundaries, threats, mitigations, owners, and links to pentest evidence.
10% complete. Method chosen (STRIDE over component diagrams) and the link into pentest scoping is designed. Data model not started.
In developmentQ3 2027
IT Audit
Controls, evidence requests, reusable framework mappings, continuous tests, exceptions, auditor access and report snapshots.
10% complete. Framework priority set for this market (NIS2 and DORA first). Control library not started.
Start with evidence
Turn the next security test into a continuous assurance programme.
Explore a read-only product tour, or tell us what you need to prove and we will scope it with you.