ISO/IEC 27001 never uses the words "penetration test" as a named mandatory control. What it does require, under Annex A.8.29, "Security testing in development and acceptance," is that security testing be defined and performed across the development lifecycle — and in practice, no credible certification auditor accepts an automated scan alone as evidence of that control.
We deliver the manual, exploit-led testing that actually satisfies A.8.29, built and reported in a format your certification body will recognise on sight.
We apply a risk-based testing scope: a full, manual penetration test at least annually and after any significant change to your applications, infrastructure or threat model, with lighter automated validation and peer review sufficient for minor updates. Scope typically covers external and internal networks, web applications and APIs, and cloud configuration — whatever is actually in your Statement of Applicability.
Why it matters
Companies pursuing ISO 27001 in Cyprus are usually doing it for a reason that has nothing to do with the paperwork itself — a client RFP, an insurer, or a partner's security questionnaire. An auditor who cannot see evidence for Annex A.8.29 raises a nonconformity, and a nonconformity delays or derails certification at exactly the moment your commercial deal is waiting on it.
What we test
- External & internal network penetration testing
- Web application & API penetration testing
- Cloud configuration & access-control review
- Annex A.8.29 evidence-pack preparation
- Vulnerability management process review
- Post-remediation retest for auditor evidence
Common vulnerabilities we uncover
- No documented security testing evidence for Annex A.8.29
- Ad hoc or automated-only scanning presented as a substitute for testing
- Untested changes deployed straight to production
- Missing risk-based testing frequency justification
- Findings with no reproducible evidence an auditor can review
- No retest evidence proving remediation actually happened
How we run your engagement
- Kick-off & scoping. A short call to agree goals, in-scope assets and rules of engagement, so your iso 27001 penetration testing (annex a.8.29) is safe, authorised and aimed at your real business risk.
- Mapping & discovery. Before touching anything we map the full attack surface in scope, so nothing exploitable slips through.
- Hands-on testing. Cyprus-based specialists exploit and chain weaknesses manually — the flaws scanners walk straight past — to show genuine impact.
- Reporting. Each issue is verified, CVSS-rated and documented with a step-by-step reproduction and a practical fix your team can apply.
- Free retest. Once you have remediated, we re-test at no extra cost to confirm the attack path is truly closed.
Tools & techniques
We test manually — external and internal networks, web applications and APIs, and cloud configuration and access control — and structure every report specifically as Annex A.8.29 evidence: scope, methodology, findings with reproducible proof, severity, and remediation status, in the format a certification auditor expects to review in minutes, not hours.
Where you are pursuing ISO 27001 alongside NIS2, DORA or GDPR, we build the evidence once so it supports every framework that needs it, rather than repeating the same testing under a different label.
When you need this engagement
- You are pursuing ISO 27001 certification for the first time
- Your certification body has flagged missing evidence for Annex A.8.29
- You are maintaining certification and need annual testing evidence
- A client or RFP requires ISO 27001 backed by a real penetration test, not a scan
- You are combining ISO 27001 with NIS2 or DORA and want one evidence base for both
What you receive
- Manual penetration test report mapped to Annex A.8.29
- Auditor-ready evidence pack
- Risk-based testing scope & frequency recommendation
- Vulnerability management process review
- Prioritised remediation roadmap
- Free retest with documented evidence
Your deliverables
When your iso 27001 penetration testing (annex a.8.29) wraps up, you receive a clear, audit-ready report plus a walkthrough call with your team. Inside you will find:
- A concise executive summary that management and the board can act on
- Every technical finding with a reproducible, copy-paste proof of concept
- CVSS v3.1 ratings and plain-language business impact for each issue
- Practical, prioritised remediation your developers can implement straight away
- A free retest and updated finding status once fixes are in place
- A signed attestation letter for clients, auditors, GDPR, NIS2 and ISO 27001
Standards & frameworks
ISO/IEC 27001:2022
Annex A.8.29
ISO/IEC 27002
What you gain
By the end of your iso 27001 penetration testing (annex a.8.29), you will know exactly which weaknesses a real attacker could exploit, what it would cost your business, and the precise order in which to fix them — backed by evidence, not a scanner’s guesswork. Cyprus firms use our findings to close critical gaps, satisfy client and regulator security questionnaires, and demonstrate due diligence for GDPR and NIS2. With a free retest included, you also get documented proof the issues are resolved.
Working with us
Every iso 27001 penetration testing (annex a.8.29) begins with a short, no-obligation scoping call to understand your goals, environment and constraints, followed by a fixed-price proposal. Most work is delivered remotely, and because we are based in Cyprus we work in your timezone with on-site visits across Limassol, Nicosia and island-wide where it helps. We keep you updated throughout and flag any critical finding immediately rather than waiting for the report. Everything is covered by a signed NDA and safe, non-disruptive testing that protects your production systems. You receive your report, a walkthrough and a complimentary retest once fixes land. Engagements are typically booked one to three weeks ahead, and urgent testing can often be arranged — just email hi@cypruspentest.com.
Why Cyprus businesses choose CyprusPentest
Your iso 27001 penetration testing (annex a.8.29) is run by senior offensive-security specialists who test the way genuine attackers do — manually, creatively and focused on proving real impact. What sets us apart:
- Based in Cyprus — local, in your timezone, with on-site coverage across Limassol and Nicosia.
- Manual, exploit-led testing that chains vulnerabilities the way an attacker would, well beyond automated scanners.
- Reproducible proof for every finding, with copy-paste steps your team can independently verify.
- Compliance-ready reporting that supports GDPR, NIS2, ISO 27001 and CySEC expectations.
- A free retest so you have documented evidence your fixes actually hold.
- Fixed-price and responsive, with a named point of contact from scoping through to retest.
Explore related services
ISO 27001 Penetration Testing (Annex A.8.29) pairs well with our other Cyprus penetration testing services for fuller coverage. You may also want:
How much does ISO 27001 Penetration Testing (Annex A.8.29) cost?
Every iso 27001 penetration testing (annex a.8.29) in Cyprus is scoped and priced individually, so you pay only for the coverage you need — with no hidden extras. After a short, no-obligation scoping call we send a fixed-price quote, usually within one business day, with clear deliverables, a firm timeline and a complimentary retest included. The price depends on the size and complexity of your environment, so you always know the cost up front before any work begins.
Get a fixed-price quote
Frequently asked questions
Does ISO 27001 actually require penetration testing?
Not by name — the standard never uses the words "penetration test" as a mandatory control. But Annex A.8.29, security testing in development and acceptance, is the control certification auditors expect evidenced, and in practice a credible certification audit will not pass without one.
How often does ISO 27001 penetration testing need to happen?
Most organisations test annually at minimum, plus after any significant change to applications, infrastructure or their threat model — a risk-based approach where minor changes get lighter validation and major releases get a full test.
What exactly does Annex A.8.29 require?
It requires security testing to be defined and performed across the development lifecycle. It does not mandate a specific method, which is why a manual penetration test — reproducible, evidenced and reviewed by a human — is the accepted way to satisfy it.
Can this evidence also help with NIS2, DORA or GDPR?
Yes. We structure the report so the same testing evidence can support multiple frameworks at once, reducing duplicate work if you are pursuing ISO 27001 alongside other obligations.