Contentstack Integration Security Review
Contentstack issues four token types with different access levels, and the wrong one leaks draft content. We test which tokens you shipped, how roles are scoped, and what each can reach. CREST-certified testers, fixed price from £2,540 for a 2-day single-integration scope, quoted within 24 hours.
- Unlimited retesting
- Unlimited pre-retesting
- No hidden fees
“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.”
“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.”
A management token can create and delete content, a delivery token can only read what has been published, and the preview token beside it can return drafts your editors have not approved.
Four token types decide what your integration can see and change
Every Contentstack stack has an Owner, and everyone else fits into Admin, Developer, Content Manager or a Custom Role, the same pattern most headless CMS platforms use. Admins and Developers can both create and manage delivery tokens, but only the Owner and Admin can create a management token, the credential that can create, edit and delete content through the API.
Delivery tokens are scoped to a single environment and can be further restricted to a branch or an alias, so a token generated for staging should never work against production. We check which environment each token in your build actually reaches, and whether a lower-environment token has quietly been given access to live content.
Preview tokens sit next to delivery tokens and exist for one purpose: showing draft content in a live preview panel before it is published. If a preview token ends up in a public bundle instead of the delivery token it was meant to accompany, visitors can see entries your editors have not signed off, so we test where each token type is exposed and what it returns.
SCOPE
What we pen test on a Contentstack integration
Token type and scope
We identify every authtoken, management token, delivery token and preview token in use, and check whether the wrong one has ended up somewhere it should not be, the same review we run for comparable headless CMS platforms.
Role and custom role boundaries
We test what a Content Manager or Custom Role can actually reach, since custom roles can be scoped to specific environments and locales but are easy to leave broader than intended.
Environment isolation
We confirm that a token generated for a development or staging environment cannot be used to read or write content in production.
Preview token exposure
We check whether a preview token has leaked into a public build, which would let anyone see unpublished draft entries before your editors approve them.
Content Management API abuse
Where a management token is reachable, we test what it can do through the Content Management API, including creating, editing and deleting entries and content types.
Webhook endpoint trust
We test whether the endpoint that receives your Contentstack webhooks verifies the request came from Contentstack before acting on it.
Branch and alias access
For stacks using branches, we test whether a delivery token restricted to one branch or alias can be used to reach content on another.
Audit log and change visibility
We check who can view the audit log and whether a role without audit log access could still make configuration changes that are hard to trace back.
Frontend token exposure
We inspect the client-side code that calls Contentstack’s APIs to confirm it ships a delivery token rather than a management token or a personal authtoken.
Invite and SSO controls
We test the user invite flow, since Owner, Admin and Developer roles can all add new collaborators, and check whether SSO is enforced for the organisation.
OUR PROCESS
Contentstack Integration Security Review: From Scope to Attestation
Stack and token intake
You give us the stack API key and a list of the tokens, roles and environments in use, not your Owner login.
Role and token mapping
We map every token and role to what it is meant to reach before any active testing begins.
Active testing
We attempt to reach content, settings and environments outside each token’s and role’s intended boundary.
Report and free retest
You get findings mapped to the specific token or role involved, then a free retest once fixes are in.
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 Contentstack 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 WilcocksonFounder, 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 written so your team can reference the report against each framework 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 Contentstack Integration Security Review Pricing
Pricing depends on the number of roles, integrations and environments in scope. See our pricing page for how we quote.
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 quoteSECTORS
Sectors We Test Contentstack For
Sector-specific scoping for regulated UK organisations.
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 Contentstack Integration 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
What access do you need to test our Contentstack stack?
We work from a management token scoped to the stack under test, or read-only access plus a list of the delivery and preview tokens in use. We do not need your Owner login.
Will testing touch live production content?
We test against development or staging environments wherever the token setup allows it, and confirm with you before any check that could touch a production environment or its published content.
How long does a Contentstack integration review take?
The 2-day single-integration scope above covers one stack and one integration. A stack with several environments, branches or custom apps in scope can need more time, which we confirm during scoping.
Is Contentstack self-hosted, and does that change what you test?
No, Contentstack is delivered as SaaS. We test your stack’s roles, tokens, webhooks and the code that consumes them, not Contentstack’s own hosting infrastructure.
What is out of scope?
Contentstack’s own infrastructure and the shared platform are out of scope. We focus on your stack configuration, custom apps, tokens and how your application consumes them.
Does Contentstack have a customer penetration testing policy?
Vendor testing terms can change, so we confirm Contentstack’s current policy for the stack under test during scoping and work within it.
Do you need our source code?
It is not required, but sharing the frontend code that calls the Content Delivery API speeds up the token and role review.
Are your testers CREST certified?
Yes. Every Contentstack integration review is carried out by CREST-certified, UK-based testers.
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 Contentstack integration
Contentstack issues four token types with different access levels, and the wrong one leaks draft content. We test which tokens you shipped, how roles are scoped, and what each can reach. CREST-certified testers, fixed price from £2,540 for a 2-day single-integration scope, quoted within 24 hours.
