Security and compliance engineering for product controls and review readiness
We provide cybersecurity and compliance services for teams preparing products for security reviews. Choose a readiness programme with controls and evidence work, or authorized penetration testing of agreed systems.
01Work
Security work around product and review requirements
We match cybersecurity scope to the product requirement or exposure you need to assess.
Preparing responses to a buyer's security questionnaire
We sort the requested evidence into existing records, documentation work and engineering gaps. That defines a readiness scope and a basis for a quote.
Assessing applicable standards and laws
ISO 27001 is a management-system standard. GDPR and HIPAA set legal obligations in their applicable contexts; PCI DSS is a payment-security standard. We assess the relevant requirements for healthcare and e-commerce systems.
Assessing an alert or a near miss
An incident, near miss or dependency alert needs a clear assessment scope. The next engineering or testing step follows the affected systems and available evidence. Our web application security checklist supports a review of application controls.
Assessing AI application security
AI application security assesses model context and tool access alongside conventional tests. We build and operate AI products of our own and publish the guide to securing MCP servers.
02Services
Readiness engineering, penetration testing and software QA
Cybersecurity consulting and penetration testing address different kinds of evidence; our software testing and QA work supports the release process.
| Service | What you are actually buying |
|---|---|
| Cybersecurity and compliance consulting | A framework, or a questionnaireWe assess applicable requirements, controls and evidence, then define documentation and engineering work. Remediation can be part of the commissioned scope, with its priorities and acceptance criteria agreed for the product.Cybersecurity and compliance consultingOr book a meeting |
| Penetration testing | Evidence is the deliverableAn authorized offensive test of agreed systems and relevant AI application surfaces. Ranked findings describe the exposure identified within that scope. Remediation and retesting can be included or commissioned separately.Penetration testingOr book a meeting |
| Security testing inside QA | It is continuousSecurity checks as part of ongoing software testing and QA. The quality practice agrees application coverage, cadence and automation around the product's risks and release process.Software testing and QAOr book a meeting |
03Fit
Where penetration testing fits your security programme
A penetration test provides point-in-time findings within agreed targets and methods.
| Your situation | What we recommend |
|---|---|
| No patching discipline, and a pen test has been booked | Patching firstEstablish dependency updates and access review for known issues, then agree what the penetration test will assess. Scope and sequencing follow the exposure and any required assessment conditions. |
| A questionnaire whose answers are true but undocumented | Write, do not buildDocument the controls behind each answer and collect the supporting records. Compliance tooling may help with evidence workflows or automated checks; its useful role depends on the product and requirement. Assess any engineering gaps separately. |
| A certification wanted because it seems prudent | Practices firstDefine the security practices you need and why certification would be useful. Where a customer requires a certificate, assess the specific standard and the route to independent certification. Controls and evidence have value beyond the certificate. |
| An annual test, and a product that ships weekly | Continuous, not annualUse security checks in the agreed sprint workflow alongside periodic offensive testing. Their coverage and cadence follow the changes to the product; a penetration test adds deeper findings within its assessment scope. |
| A deal blocked on a customer's security review | Start hereConsulting clarifies the review requirement, maps available evidence and defines documentation or engineering gaps. Agree a scope around what the customer asks and which systems are included. |
| AI features live, and the new surface untested | Test itAI application security checks complement conventional testing. Assess the additional attack surface, with agreed targets and boundaries for model context and tool access. |
What we hold, and what that covers
unicrew holds ISO 27001:2022 and ISO 9001:2015 certifications, renewed through a multi-stage audit with Quay Audit UK. Our active security practice includes one dedicated security engineer and a part-time senior security consultant. We have ISTQB-certified QA engineers. These organizational certifications and individual qualifications are separate from the requirements and remediation agreed for your product.
04Order
From review requirement to an agreed security scope
Use the review requirement to agree which security work to commission for the systems in scope.
- Map requirements to current controlsWe classify questionnaire answers by available evidence, missing documentation and control gaps. That establishes the work to scope. From you: the questionnaire, its review requirements and a named owner of the controls.You getA triaged questionnaire
- Prepare the documentation and evidenceWe document agreed policies and collect evidence of how the controls operate. A fixed-scope readiness sprint suits a defined questionnaire and evidence scope. From you: existing records and the people who own the processes.You getAn evidence pack
- Agree testing and remediate by riskTesting and engineering can be commissioned separately or together. Priorities follow the assessed exposure and review requirements. From you: agreed test targets or repository access, and someone authorized to approve the changes.You getRemediation, highest risk first
- Define ongoing ownership and reviewWe agree ownership for dependency updates, access reviews and security checks in the delivery process. Evidence handover and any continuing review work have a defined scope and cadence. From you: a named control owner and agreement on maintenance responsibilities.You getControls in the delivery process
We sort a buyer's security questionnaire into what you can prove, what needs writing down and what needs engineering. That shows which service you need first. In most companies I have looked at, the writing is the largest part and takes about a fortnight.
Vuhar MamedovManaging Partner, Europe, unicrew05Proof
Healthcare, authentication and research platform engineering
HealthcareCancerDocs: healthcare software built to the HIPAA Security RuleSoftware built to the HIPAA Security Rule for a private cancer consultation platform.
SecurityRefactoring the Data Architecture of a Multi-Factor Authentication PlatformSolus Connect is an innovative multi-factor authentication platform that uses 3D facial authentication and machine learning to track down fraudulent behavior.
Knowledge ManagementSaaS for Digital ResearchA SaaS solution that helps knowledge workers streamline research work involving a substantial amount of information.
06Questions
Questions about security scope and review readiness
unicrew holds ISO 27001:2022 for information security and ISO 9001:2015 for quality management.
The organizational certificates were renewed through a multi-stage audit with Quay Audit UK. We have ISTQB-certified QA engineers; ISTQB is an individual testing qualification.
We help prepare controls and evidence for a security review or compliance assessment.
Cybersecurity consulting assesses requirements and gaps; documentation and engineering remediation follow the agreed scope. The applicable requirements differ:
- ISO 27001 concerns organizational information-security management.
- GDPR is an EU regulation.
- HIPAA sets obligations in applicable healthcare contexts.
- PCI DSS is a payment-security standard.
- NIS2 is an EU directive, with applicability assessed for the organization.
Penetration testing provides findings from an authorized assessment. The customer, auditor or certifier makes the acceptance decision.
We assess AI application security alongside conventional security testing.
The agreed scope can address:
- Prompt injection in model-connected workflows.
- Data leakage through model context.
- Access control for tool calls and connected resources.
Penetration testing tests agreed surfaces. Cybersecurity consulting scopes access and data-flow design. These checks complement the application's conventional tests.
We quote security work for the agreed assessment, documentation or engineering scope.
- Time and materials is billed hourly and quoted per project.
- Fixed price is outcome based and quoted per project.
- Team extension is billed monthly per team member.
There is no minimum engagement period. Most engagements start within two to four weeks.
We work with existing tooling where it supports the agreed scope. Compatibility, access and any needed changes are established during scoping.
What teams usually pair this with
All servicesScope the security work your product needs
Share the security questionnaire or assessment requirement and describe the systems it concerns. We will identify the evidence, documentation and engineering scope to quote.