About

Security testing, done with permission.

Twarx Vulnerability Assessment helps businesses find and fix weaknesses in their systems. We only ever test systems with written authorisation from their owner.

Who we are

Vulnerability Assessment, at Twarx.

Twarx is a studio with four departments: AI Research, Micro SaaS Boutique, Brand Foundry and Vulnerability Assessment. This department checks whether the systems businesses run hold up against the ways systems are actually attacked.

It exists because building and securing software are closely linked. Most of the weaknesses we look for, such as missing access checks, exposed storage and outdated components, are ordinary engineering mistakes. Understanding how software is built helps us explain findings in terms developers can act on, and helps us recommend fixes that fit how a team actually works.

Our rule is simple: we only ever test systems with written authorisation from their owner. Every engagement starts with a signed scope that names the systems, the limits and the testing windows. If something is not covered by that authorisation, we do not test it.

The aim of every engagement is the same: a clear picture of where you are exposed, a practical plan for fixing it, and written confirmation once the fixes are in place.

Principles

What we hold ourselves to

01

Authorisation before everything

We only ever test systems with written authorisation from their owner, within a scope both sides have signed. When in doubt, we stop and ask.

02

Defensive by purpose

Our work exists to help organisations close gaps. Findings go to the system owner and the people they name, and nobody else.

03

Plain reporting

We explain what we found, why it matters and how to fix it, in language that leadership and developers can both use.

04

Care on live systems

We prefer staging environments, agree limits for production, avoid destructive techniques and stop immediately if anything looks at risk.

05

Follow-through

An assessment is not finished when the report is sent. We support the fixes and retest to confirm they worked.

Our standards

Commitments on every project

  • We only ever test systems with written authorisation from their owner.
  • Every finding in our reports has been verified by a person.
  • Your findings are confidential and shared only with the people you name.
  • Engagement data is deleted on request when the work ends.
  • Timelines and prices are agreed in writing before any testing starts.
  • Retesting of fixed issues is part of every assessment.

Know where you stand

Tell us what you want tested. We will reply with a proposed scope, the authorisation we need, and a quote.