Xarmoured is an independent, founder-led cybersecurity engineering company. We test web applications, APIs and Android apps today, and we are building defensive engineering and our own platform, Protocol, on the same evidence.
A signal enters through the public surface. Identify what is reachable and what it trusts.
Scope follows your system. Testing follows the paths an attacker could take.
Manual-first testing of authentication, authorization, business logic, input handling and the attack paths scanners routinely miss.
Scope and deliverables 02Test object authorization, authentication, data exposure, workflow abuse and trust between API consumers and backend services.
Scope and deliverables 03Assess Android application behavior across the client, local storage, transport layer and backend APIs.
Scope and deliverables 04Verify that remediation closes the original attack path without relying on screenshots, tickets or assumptions.
Scope and deliverablesScanners help identify potential weaknesses. Understanding whether a weakness can be exploited takes context: who has access, what the system trusts, and what happens when that trust fails.
Define assets, access, exclusions, testing windows and rules of engagement. Establish how urgent findings will be communicated before any testing begins.
Next: mapAuthorization, business logic and attack chaining are tested by people, not inferred from scanner output.
Each finding records the conditions, the reproduction and the real impact, and states the limits of the assessment.
Engineers get a clear path to fix the cause. We then test the fix against the original path.
Protocol is the security engineering platform Xarmoured is developing, built around the lifecycle every engagement already follows. It is under active development and is not yet available.
Evidence → Finding → Remediation → Retest → Measured improvement
Explore ProtocolAn authorization bypass in Invoice Ninja allowed access that the application should have denied. Fixed in 5.13.27.
A server-side request forgery issue in Invoice Ninja could make the server send requests on an attacker's behalf.
BookStack did not correctly enforce access control on its attachment editing endpoint. Fixed in 26.05.3.