Azure DevOps Security Review
A service connection is a standing credential into your Azure subscription, held by a pipeline that anyone with repository access can change. We pen test what that pipeline will run, and what the connection behind it can reach. CREST-certified testers, fixed price from £3,060, scoped in 24 hours.
- Unlimited retesting
- No rescheduling or cancellation fees
- Fixed quote within 24 hours
“I would highly recommend EJN Labs to any organisation seeking reliable, detailed, and well-managed penetration testing services, particularly for government or enterprise-level projects.”
Imran SaghirProject Lead, SquareOne“There wasn’t another company we could find that could deliver what we needed in the timeframe we needed. The client loved it, and we got instant ROI from the engagement.”
Dan WilcocksonCo-Founder, CelloriMost Azure DevOps organisations hold at least one service connection with Contributor or Owner on a subscription, because that was the quickest way to make deployment work. Anyone who can cause a pipeline to run arbitrary commands inherits it.
Why the service connection is the prize
Getting a pipeline to run arbitrary commands is often easier than it should be. Variables interpolated into script steps, pipeline definitions editable without review, and pull request triggers that run definitions from the source branch all provide a path.
Approval and check configuration is the control that should stop this, and it is frequently applied to environments that do not matter while the production one is exempt. We test what is enforced rather than what is configured.
ISO 27001, SOC 2, PCI DSS and Cyber Essentials Plus audits accept manual penetration test evidence. Scan-only evidence is generally insufficient.
PIPELINES, CONNECTIONS + AGENTS
What we actually pen test on an Azure DevOps organisation
Manual pen testing across pipeline injection, variable groups and secrets, service connection privilege, agent pool isolation and branch and approval policy.
Pipeline injection and variable handling
Variables and parameters reaching script and task inputs, whether values from a pull request branch or a queue-time override can inject commands, and runtime parameter validation.
Service connections and privilege
Every service connection enumerated with its scope and permission, whether connections are shared across projects, which pipelines may use them, and what each one can reach in Azure or elsewhere.
Variable groups and secret scope
Secret variable handling, whether secrets are masked in logs, key vault linked groups and their access policies, and whether a pipeline can print or exfiltrate a secret it is permitted to use.
Triggers and pull request handling
Whether pull request builds run the definition from the source branch, fork pull request settings, and whether an outside contributor can reach secrets or a service connection.
Agent pools and isolation
Self-hosted agent reuse between jobs and projects, what the agent can reach on the network, credentials cached on the agent, and whether the agent identity itself carries privilege.
Branch policies and approvals
Required reviewers and their bypass permissions, environment approvals and checks on production, whether pipeline definitions themselves are protected, and organisation-level permission inheritance.
METHODOLOGY
Azure DevOps Security Review: From Scope to Attestation
CREST-aligned methodology built on OWASP Web Security Testing Guide, OWASP ASVS, NIST SP 800-115, and PTES. Each finding maps to all four standards plus your specific compliance regime.
Reconnaissance
Application mapping, technology fingerprinting, content discovery, parameter enumeration, authentication-flow analysis, role-matrix construction.
Vulnerability Assessment
Authenticated and unauthenticated automated scanning across every user role, plus targeted manual checks for known weakness patterns.
Manual Exploitation
Hands-on testing by a CREST-certified pentester. Business-logic exploitation, chained vulnerabilities, privilege escalation, impact validation.
Reporting + Retest
Executive summary, technical report with CVSS scores and reproduction steps, walkthrough call, free retest after remediation, attestation letter.
CREDENTIALS
Verified Accreditations Auditors Accept
Every credential below is independently verifiable. UK procurement teams, FCA supervisors, ISO 27001 / SOC 2 auditors, and cyber insurance underwriters all recognise these standards.
GET YOUR QUOTE
Get a CREST Azure DevOps pen test quote in 24 hours
A fixed-price quote back in one business day, from a named CREST assessor. No sales pipeline, no chasing.
- CREST and IASME accredited. Testing your auditors and clients already recognise.
- Fast-track testing within 24 hours where required. Free retest of every fix included.
- Live findings via your client portal, not a four-week PDF.
- Fixed price from £3,500 for a single-role, single-app scope, agreed up front. Most engagements run £5,000 and up. No day-rate surprises.
Dan WilcocksonCo-Founder, CelloriUnder NDA Further named references available on a scoping call.
- We reply within one business day with a fixed-price quote from a named CREST assessor.
- You approve the scope and we book a start date, usually within 24 hours.
- Live findings land in your client portal as we test, with a free retest of every fix.
Get your fixed pen test quote in 24 hours
Quote request received
We will reply within one business day with your fixed-price quote from a named CREST assessor.
Your data stays with us. No newsletter signup.
or book a 20-min scoping call first
We reply within one business day. Your data stays with us. No newsletter signup.
COMPLIANCE READY
Reports Mapped to Every Framework
Findings are explicitly tagged to the relevant control reference. Your audit team submits the report directly without translation work.
ISO 27001:2022
Annex A.8.8 management of technical vulnerabilities plus A.5.15-5.18 and A.8.2-8.5 access control validation.
SOC 2 Type I & II
CC6 logical access, CC7 system operations, CC8 change management evidence.
PCI DSS
Requirement 11.4 application penetration testing across cardholder data environments, including ecommerce penetration testing for online retail platforms.
FCA SYSC
SYSC 4.1.1R, 6.1.1R, 13 mapped to each finding for FCA-regulated firms.
UK GDPR
Article 32 effectiveness testing, customer-data security controls, ICO-acceptable evidence.
Cyber Essentials Plus
Direct certification through our IASME body status, single-vendor delivery.
PRICING
Transparent Azure DevOps Security Review Pricing
Pricing depends on app complexity, user-role count, business-logic depth, and integration surface. The day count flexes; the included deliverables stay the same across all engagements.
2 to 3 testing days
Single user role, basic CRUD application, marketing website with auth. Around 5 working days from kickoff to report.
Get a fixed quote3 to 5 testing days
Multi-role SaaS, business application with payment integration. Around 8 to 12 working days from kickoff to report.
Get a fixed quote5 to 7 testing days
Multi-tenant platform, complex authorisation matrix, integration-heavy applications. Around 15 to 20 working days from kickoff to report.
Get a fixed quotePart of Technologies We Pen Test. These are examples of the stacks we publish pages for, not a complete list. If yours is not here we still test it. Related pages:
BY SECTOR
Azure DevOps Security Review for Your Sector
Sector-specialist scoping for UK businesses with sector-specific compliance regimes and threat models.
Fintech & FCA-Regulated
FCA SYSC, Open Banking FAPI 1.0, PSD2 SCA, payment-flow scrutiny, KYC/AML testing.
Fintech sector pageSaaS Companies
SOC 2 Type I & II evidence, multi-tenant boundaries, role escalation, customer-tenant isolation.
SaaS sector pageLaw Firms
SRA Cyber Standard, privileged data, conveyancing fraud defence, partner-tier procurement.
Law firm sector pageHealthcare
NHS DTAC, DSP Toolkit v6, UK GDPR Article 32, EHR systems, telehealth platforms.
Healthcare sector pageInsurance
FCA / PRA Operational Resilience, cyber underwriting, claims data, broker portals.
Insurance sector pagePublic Sector
CCS / G-Cloud framework, NCSC-aligned, citizen-facing services, PSN-compliance scrutiny.
Public sector pageWHY EJN LABS
What You Get From Azure DevOps Security Review
Six concrete differentiators competitors don’t all match.
CREST-Certified Testers, Verifiable
Every test by a CREST-certified pen tester (CRT, CCT APP, CCT INF where applicable). Verify our company status at crest-approved.org.
24-Hour Startup, Where Required
From signed scope to active testing in a single business day for incident response, audit deadlines, or regulator-driven timelines.
Live Findings, Not 4-Week PDFs
Critical issues reported during testing through your client portal. Your team remediates while testing continues.
Audit-Ready Reports
Executive summary plus full technical report with CVSS scores and explicit framework mappings (ISO 27001, SOC 2, PCI DSS, FCA SYSC).
Free Retests, Standard
Verify remediation of every finding before close-out. Letter of attestation for audit submission included. Most competitors charge £1,500-£3,000 per retest.
UK-Based CREST Testers
Every engagement performed by vetted, UK-based CREST-certified testers, matched to your needs, security clearance, and compliance scope.
FAQ
Frequently Asked
Do you need admin access to the organisation?
Read access to project settings, service connections and pipeline definitions gives the best result. We can test with less, but service connection scope is where the highest-severity findings live and that needs visibility.
Will you run anything against our Azure subscription?
Only with explicit agreement and within a scope you define. Usually we demonstrate what a service connection could do using read-only calls rather than making changes, and we say exactly where we stopped.
We use both Azure DevOps and GitHub. Should we test both?
If both can deploy, yes. Organisations migrating between them often leave the old pipelines connected and credentialed, and an abandoned pipeline with a live service connection is a genuine risk.
Is this a replacement for our Azure security review?
No, it is the layer above. This covers the pipeline and its credentials. Testing what those credentials reach inside the subscription is our Azure cloud security review, and the two fit together.
What do we receive?
A report mapped to ISO 27001, SOC 2 and Cyber Essentials where relevant, a technical write-up with reproduction steps, and unlimited free retesting.
20+ CREST-accredited testing services in one place
Web, mobile, API, cloud, AI, infrastructure, red team. Pick the test that fits your environment.
Get a fixed price for your Azure DevOps review
Tell us how many projects, pipelines and service connections are in scope and whether self-hosted agents are in play. Fixed-price quote within one business day.
