Services
What each engagement covers and what you hold at the end. Testing and compliance work can be scoped and quoted together.
- Security leadership
- Virtual CISO
Penetration testing
We use scanners for coverage, then spend most of the time on manual work: access control between users and tenants, business logic, authentication flows and the way services trust each other. Those are areas automated tools tend to miss.
Tenders in India, the Gulf and much of Asia often call this VAPT (vulnerability assessment and penetration testing).
- Web applications and REST or GraphQL APIs, tested against OWASP WSTG and ASVS
- iOS and Android apps against OWASP MASVS, including the backend they call
- AWS, Azure and Google Cloud configuration and IAM reviews, checked against CIS Benchmarks
- External and internal network tests, including Active Directory
- Source code review for high-risk components
Audit readiness
For a first certification or a regulator's deadline. We start from what you already do, write down what's missing, and help your team run the controls for long enough to build up the evidence an audit looks for.
- Gap or readiness assessment against the standard or regulation, with a prioritised plan
- Policies and procedures written around how your company actually operates
- Risk assessment and Statement of Applicability (ISO 27001)
- Evidence collection and readiness checks before the auditor arrives
- Preparing for management review and internal audit
- Support during the external audit, including auditor queries
Virtual CISO (vCISO) and GRC programme
Many companies need a security lead before they can justify hiring one full-time. A virtual CISO gives you that person for a set number of days each month.
- Security strategy and a roadmap
- Risk register and policy ownership
- Regular reporting to leadership and the board
- Customer security questionnaires and due diligence calls
- Incident response planning and tabletop exercises
- Preparing for surveillance and recertification audits
Managed vulnerability scanning
Scheduled scanning and a person reviewing the output. We confirm each issue, remove duplicates and false positives, and send you the ones that need fixing with a suggested owner and deadline. Priority depends on whether an issue is known to be exploited and how exposed the system is, not only on its CVSS score.
- Scheduled external and internal vulnerability scanning, with a retest to confirm each fix
- Cloud security posture monitoring
- Regular reporting on open risk and how quickly it's being fixed
- Notes on newly disclosed vulnerabilities in software you run
Third-party risk
Checking the security of suppliers who hold your data, and answering the security questionnaires your own customers send.
- Supplier risk framework, with suppliers tiered by the data they hold and the access they have
- Supplier assessments and follow-up on findings
- Completing inbound questionnaires (SIG, CAIQ and custom formats)
- A security pack and trust page content for your sales team
OT and ICS security
We plan each assessment with your plant engineers. We start with passive methods and test a live process actively only inside an agreed change window.
- Architecture review against the Purdue model, including every route between the IT and control networks
- Passive asset discovery and traffic analysis
- Zone and conduit risk assessment following IEC 62443-3-2, with guidance from NIST SP 800-82
- Remote access and vendor connection review
Risk assessments and training
Standalone risk assessments for a new product, acquisition or market. Training is short and specific to the audience.
- Information security and privacy risk assessments
- Data protection impact assessments (DPIA)
- Secure development training for engineering teams
- Awareness sessions and phishing simulations for staff
What affects the price
We don't sell fixed packages, because two applications that look similar can need very different amounts of testing. For a test, the fee mostly depends on:
- How many user roles and tenants need testing against each other
- The number of API endpoints, or the size of the cloud estate
- Whether we test from the outside only, or with credentials and source code
- Testing windows, such as nights or weekends for production systems
For compliance work it's the number of frameworks, how many locations and systems are in scope, and how much is already documented. Sending those details with your first email makes a quote quicker.
Not sure which of these you need? Tell us what prompted the question and we'll suggest where to start.
Contact us