Protocol is the security engineering platform being developed by Xarmoured to connect offensive assessments, adversary simulation, defensive validation and security intelligence.
Security findings often end up scattered across reports, spreadsheets and tickets. It becomes hard to show what was tested, what was found, what changed and whether the fix held. Offensive and defensive teams can work from different records, so the same weakness is found, patched and forgotten without anyone measuring the result.
This is the lifecycle Protocol is designed around. It is also how every Xarmoured engagement is already structured. Protocol’s job is to turn that practice into a durable, shared record.
What was tested, what was observed, and the proof that it happened.
A validated issue with scope, severity, impact and reproduction.
The fix, tracked to the underlying cause rather than a closed ticket.
The original attack path repeated against the fix.
A recorded result: resolved, partially resolved or still open.
These are the design principles of the platform, not a feature list. Feature-level status is shown in the architecture below.
Every finding traces back to the evidence behind it, and forward to its fix.
What was tested, when and under what scope stays visible across engagements.
From discovery through validation, remediation and closure, with explicit states.
Fixes tracked against the underlying cause, not just the status of a ticket.
Each retest repeats the original path and records resolved, partially resolved or open.
Labels show what we are prepared to claim today. Nothing on this page is available to use.
Being designed to provide organization and tenant boundaries, role-based access, shared assets, evidence storage, audit logs, APIs, integrations and notifications. None of these is offered to external users.
Being built around engagement and asset management, findings with CWE and CVSS mapping, evidence, reporting and retesting. Planned for later: controlled attack scenarios and adversary emulation, which are not being built yet.
Intended to cover security telemetry, SIEM and EDR integrations, detection rule management, hunt libraries and investigation workflows, mapped to MITRE ATT&CK. Not a SIEM or EDR, and no integrations exist.
Intended to link CVE and advisory intelligence, attack techniques and threat research to attack scenarios and detections. Not started as a product.
The longer ambition is to carry the same evidence trail across the boundary between attack and defense. Intelligence informs the attack. Attack validates the defense. Defense identifies gaps. Validation measures improvement. This is a long-term direction, not a feature: none of this loop is built or available today.
Real assessments show where security work actually breaks down.
Published findings develop new knowledge and methods.
Repeatable steps become technology rather than spreadsheets.
Customer work tests the platform, and the platform improves delivery.
Over time: penetration testing teams and consultancies, product security teams, and security providers that want evidence and validation to outlast a single report. If this is a problem you work on, we would like to talk about it. This is a conversation, not a sign-up. We are not offering early access or taking pre-orders.