External
Internet-facing hosts, services and exposed applications, from an attacker's starting point.
PYXA is the product. PYXA Consulting is the team behind it, available for penetration tests, vulnerability management programs, compliance audits and CISO advisory. We work with the platform underneath or with whatever you already run; buying one never requires the other.
Fixed scope and a written deliverable, not open-ended staffing.
Practitioners only. The people who built the platform run the work.
We leave you with something your own team can run without us.
EU-based · English and French · on-site or remote
Find what an attacker would find first, prove it, and retest until it is closed. Every finding comes with the evidence, the business impact and the fix, ranked the way a remediation team can act on.
Internet-facing hosts, services and exposed applications, from an attacker's starting point.
Lateral movement, privilege escalation and the attack paths to Tier Zero from an internal foothold.
Authenticated and unauthenticated testing following the OWASP Web Security Testing Guide.
Each fixed finding is tested again. A finding closes when the retest says so, not when a ticket does.
You end up withA report your engineers can act on. If you run PYXA, the findings are imported straight into it and tracked to a verified retest.
Most programs do not fail on detection. They fail on ownership, on a priority nobody agrees with, and on closure nobody verifies.
Scanner coverage against your real asset inventory, the blind spots, and a ranked view of what matters this quarter rather than a severity histogram.
You end up withA written assessment and a 90-day plan your CISO can take to the board.
Asset ownership, priority policy, SLAs the business has agreed to, campaign cadence, verification and the reporting line upward, run with your team until the rhythm holds without us.
You end up withOwners, deadlines, verified closure and a monthly report nobody argues with.
A gap assessment against the framework you are held to, the evidence wired into your tooling rather than assembled by hand, and a dry run of the questions an auditor will ask.
Article 21 risk-management measures and the Article 23 reporting process: 24-hour early warning, 72-hour notification.
The information security assessment for the automotive supply chain, ahead of the audit provider's visit.
Vulnerability handling, SBOM, coordinated disclosure and the reporting clocks for products placed on the EU market.
Requirements 6 and 11: vulnerability identification, timely patching and quarterly scanning, with evidence that regenerates.
The limit, statedWe are not a certification body. We assess you against the framework and prepare you for the accredited auditor, who issues the certificate.
Fractional support for the part of the job that is not technical: the roadmap, the board narrative, the budget case, vendor selection, and the conversations with engineering leadership about why this quarter's patching matters more than the feature. A second practitioner in the room when the decisions are made.
We are not trying to become a dependency. The last phase exists to make us unnecessary.
Interviews with security, infrastructure and the business. What is scanned, what is owned, what is actually being fixed today.
Priority policy, SLA bands and ownership signed off by the people who will be held to them. This is where programs are won or lost.
First campaigns, first verified closures, first honest report. We sit in the weekly meeting and fix what breaks.
Runbooks, policy documents, dashboards and the training so the program survives the next reorganisation.
When a mission runs on PYXA, the report is the Command Center: one estate score with its contributions, a chain of counts from open findings down to the ones that reach a crown jewel, and SLA performance stated with its denominator.
When it runs on your existing tools, we build the same discipline into them: a number with a denominator beats an adjective, and an unscanned asset is never reported as clean.
PYXA Consulting and the PYXA product have the same owner, and that is disclosed in writing before PYXA is discussed with a client. PYXA is never the only remediation recommendation in a paid assessment, and the product and the consulting are separate contracts.
A first call is 30 minutes with a practitioner, not a qualification script. If a mission is not the right answer, we will say so.
Run the free edition on your own server today, or see PYXA on your own scanner data in a 30-minute demo.