Amazon SP-API DPP Penetration Testing
Cybersecify is a penetration testing company that performs the Amazon SP-API Data Protection Policy penetration test required by clause 2.7.2, for Solution Providers holding restricted roles. We are founder-led, based in Bengaluru, India, and we test for clients in any country. We produce the test, the report and the letters a submission takes. Amazon alone decides the submission.
Three situations bring people to this page, and all three carry a date. You are listing an app or adding a restricted role, and the security answers are due. Your annual renewal is coming round under the 365 day cycle. Or Amazon has removed or restricted your app after a deadline passed, and every week it stays down costs you. The next section sets out what each one asks for and what we produce.
What you need is a scope that matches what clause 2.7.2 actually asks for, a price that does not move after you commit, and a date you can hold someone to. All three are on this page, before you talk to us.
Three situations: listing, renewal, or removed
One policy, three different engagements. What changes is what starts the clock, what Amazon is reading when it looks at you, and which document carries the weight. Find yours here and the rest of this page reads in that order.
Listing your app, or adding a restricted role
What starts it. You are registering an SP-API application, or applying for one of the five restricted roles on an application you already have. Adding a role is what pulls an application into section 2 of the Data Protection Policy for the first time, and clause 2.7.2 binds you, the Solution Provider, rather than the selling partner who authorises you.
What Amazon asks for. The submission is your developer profile: Contact Information, Data Access, Roles, Use Cases and Security Controls. Amazon publishes one to two weeks for a standard review where no restricted role is involved. A restricted role review runs in three stages, business, security and technical, and Amazon publishes no duration for it. There is no approved vendor list and no tester certification named anywhere in the policy.
What we produce. The clause 2.7.2 test across the categories your estate actually puts in scope, the v1.0 report, the Letter of Engagement that accompanies a submission, and the Letter of Attestation signed after the retest. Teams at this stage usually want the test finished before they answer the Security Controls questions, so the answers describe controls that exist and the 365 day clock starts from a real test. Amazon decides the approval. We produce the test and the evidence.
Next step. Tell us you are in this situation when you ask for an estimate, so the scoping call starts in the right place. What the policy binds you to, and who it binds, is in the DPP pentest requirement guide, and what to do when a submission comes back rejected.
Annual renewal, with the 365 day clock coming round
What starts it. Your roles are approved and your last penetration test is approaching 365 days old. Clause 2.7.2 reads that the Solution Provider must perform penetration testing at least every 365 days using an industry-recognized methodology, so it is the test that must not age out, whatever date your own calendar reminder carries.
What Amazon asks for. That clause, plus the two either side of it. 2.7.1 asks for vulnerability scanning at least every 30 days and after significant network, application or infrastructure changes. 2.7.3 sets remediation at 7 days for critical findings and 30 days for high, counted from discovery, with no stated timeline for medium or low. Section 3 asks you to keep the records that verify compliance and to certify compliance in writing on request.
What we produce. A current test across the four categories clause 2.7.2 enumerates, a v1.0 report naming the standard against each finding, the Letter of Engagement, the Letter of Attestation, the free retest and the v2.0 report recording the closed state, and 12 hours of founder-led consulting. The retest earns its place here more than anywhere, because 2.7.3 starts a clock on the findings the moment they exist.
Next step. Tell us you are in this situation when you ask for an estimate, so the scoping call starts in the right place. What changes at a reassessment, and what does not, is in the annual reassessment guide, and the 2.7.1 scanning requirement.
Amazon has removed or restricted your app after a deadline passed
What starts it. An assessment deadline or a remediation deadline went by and Amazon has pulled or restricted your access. This is not a faster version of a renewal. The work starts at the finding that ran out of time rather than at a fresh scope list, and the document that carries the most weight is the one showing the fixed state.
What Amazon asks for. Amazon decides what it wants to see and Amazon decides whether access comes back. The obligations you can point at are the ones already written down: the 2.7.3 clocks the deadline came from, and section 3 records plus written certification on request. Amazon guidance pages, which sit outside the Data Protection Policy and state that they create no commitments, describe a retest after remediation. We attribute that as guidance, because that is what it is.
What we produce. An assessment of the application in the state it is actually in, starting where the finding was, with reproduction steps and a severity a reader outside your company can recompute. Then remediation guidance specific enough for your engineers to act on, and verification of the fixed state once they have. In reinstatement work we have delivered, the fixed state evidence is the part a reviewer reads hardest. What nobody can sell you is the decision: we have no visibility into it and we do not quote a success rate for it.
Next step. Tell us you are in this situation when you ask for an estimate, so the scoping call starts in the right place. What a findings deadline actually asks of you is in the assessment findings deadline guide, and the DPP pentest requirement guide.
Tell us which one you are in, and we will scope against that rather than against a template. All three run on the Compliance Plan, and the price is further down this page before you talk to us.
Five things about the DPP that get buyers oversold
These are from the policy text itself. Knowing them means nobody can sell you work Amazon never asked for, including us.
- The DPP contains no SOC 2 and no ISO 27001 requirement. Control mapping to those frameworks is useful for your own auditors and for enterprise customers, and we include it, but Amazon does not ask for it in a DPP submission.
- The stated encryption minimum at rest is AES 128 or RSA 2048, not AES 256. If a quote is priced around meeting AES 256 for the DPP, the premise is wrong.
- The report is evidence you hold, not evidence you file. There is no clause requiring you to upload it. Section 3 requires you to keep records and to certify compliance on written request, with a right to audit.
- There is no Amazon-issued DPP certificate and no approved assessor list. Any vendor implying otherwise is describing a programme that does not exist.
- The DPP is not the policy that ends your API access, and a pentest cannot touch the one that does. That is the Acceptable Use Policy: 44 numbered clauses against the DPP's 16, and its clause 3.13 pulls the DPP inside it. The AUP governs what your product may do with Amazon data rather than how you protect it, so it is decided on your roadmap and leaves nothing in your infrastructure to test. Of the 26 AUP clauses that bind a provider's product or process, a test contributes input on seven and evidences none outright. We sell the clause 2.7.2 test. Nobody can sell you an AUP pass.
Full detail, including what the policy leaves open, is in our guide to the DPP pentest requirement.
What clause 2.7 actually asks for
Start here, because this clause does not apply to every application. It is section 2 of the Data Protection Policy that mandates the testing, and section 2 applies where a restricted role handles personally identifiable information. Amazon's roles documentation marks five roles as restricted:
| Restricted role | What it is used for |
|---|---|
| Direct-to-Consumer Shipping | Shipping orders directly to customers; order reports, order tracking reports, EasyShip |
| Professional Services | Add-on services such as assembly and installation, via the Services API |
| Selling Partner Support | Seller support cases and related correspondence |
| Tax Invoicing | Generating tax invoices to comply with tax regulation |
| Tax Remittance | Calculating and remitting sales taxes |
Roles such as Pricing, Product Listing and Inventory and Order Tracking are not restricted. If your application holds none of the five, clause 2.7.2 is not your obligation and you should not be buying a test to satisfy it. Check the roles your application is actually approved for in your developer profile in the Solution Provider Portal before you plan around this page, and read the roles your next feature will need, because adding one is what pulls an application into section 2 for the first time.
If one of the five does apply, three clauses carry obligations, and all three have a document or a deadline attached.
| 2.7.1 | Vulnerability scanning at least every 30 days, and after significant network, application or infrastructure changes. The change-triggered half has no interval attached, so a fixed-cadence contract alone does not satisfy it. |
| 2.7.2 | A penetration test at least every 365 days, using an industry-recognized methodology, across four scope categories. This is the clause this page is about. |
| 2.7.3 | Critical findings remediated within 7 days, high within 30. A clock, which is why the retest matters as much as the test. |
Quoted from the Amazon Services Data Protection Policy. Full analysis, including what the policy does not require, is in our guide to the DPP pentest requirement.
The four categories, and what we scope against each
The application layer is two scopes, the web application and the API backend, reported together, because the effort, the test cases and the threat surface differ in each. This is the part most quotes leave vague until after you have signed.
Network infrastructure
Perimeter enumeration, edge configuration, transport security, email authentication posture, and the internal boundaries the clause names.
Cloud environments
IAM and least privilege, encryption at rest against the policy minimum, environment separation, and logging and monitoring as audit evidence.
Application layer assets
Authentication, session handling, tenant authorisation, business logic, injection classes, and Login with Amazon token issuance, refresh, storage and rotation.
Other in-scope systems
Anything else that retrieves, stores or processes Amazon data, which in practice is usually a desktop or mobile client.
What a DPP engagement costs, before you talk to us
The plan is the Compliance Plan, which covers two scopes at INR 1,79,999, with each additional scope at INR 74,999. It is the Compliance Plan because a platform reviewer reads findings against controls, and per-finding control mapping and the Letter of Attestation are Compliance Plan deliverables. A DPP engagement is commonly four scopes, though the count follows your estate rather than the category list, and moves both ways.
Your situation moves the shape more than the plan does. A first listing and a renewal both follow the estate. An app Amazon has removed usually needs more, because the assessment has to start where the finding was as well as cover the categories. We confirm the count after you have walked us through the product and we have verified access, and the formal quote comes after that rather than before it. It can move down as readily as up.
| Three scopes | INR 2,54,998 |
| Four scopes | INR 3,29,997 |
Every one of those engagements includes the Letter of Engagement that accompanies your submission, the Letter of Attestation signed by the lead tester after the retest, a free retest with a full v2.0 report, and 12 hours of founder-led consulting. None of it is priced separately.
Prices exclude taxes. A scope is six business days, five testing and one writing the report, so the report lands inside the window rather than after it. For larger estates we confirm the schedule when we scope it. Full terms on our pricing page.
What you receive
Three reports from one engagement
The web application and its API backend are tested as separate scopes and reported together, so a four scope engagement arrives as three documents: application layer, network, and cloud. Each carries reproduction steps, business impact, remediation guidance and severity.
Letter of Engagement
Evidences that a firm was engaged to perform the test, issued on our letterhead. This is the document that accompanies a submission.
Letter of Attestation
Signed by the lead tester after the retest, confirming what was tested and the state it ended in. Included in every DPP engagement.
A free retest, and a v2.0 report
Triggered once your fixes are in, and no later than one month from the v1.0 report. The retest produces a full v2.0 report with updated status columns and fresh per-finding evidence of the fixed state, not a status email.
The evidence set from a delivered engagement is published, covering the clause 2.7.2 scope categories. We send the PDFs on request rather than putting client deliverables on a download link. Request the SP-API evidence set, or ask for the DPP evidence checklist, which sets out what Amazon asks you to produce for the Solution Provider Security Assessment and which items a penetration test evidences for you.
Is this the Amazon SP-API security audit?
No. The audit is Amazon's. Section 3 of the Data Protection Policy reserves Amazon the right to "audit, assess and inspect" the systems that handle Amazon data, "either itself or through an independent certified public accounting firm it selects". The assessing party is chosen by Amazon and answers to Amazon. No penetration testing firm can appoint itself to that role.
Clause 2.7.2 puts the other half on you: perform the test, every 365 days, to an industry-recognized methodology. That is the part we do, and the evidence it produces is what an assessment reads.
If a vendor offers to conduct your Amazon audit, ask which Amazon document appoints them. Section 3 names who selects the assessor, and it is not the vendor.
The industry-recognized methodology, named
Clause 2.7.2 requires an industry-recognized methodology. A report that does not say which one it followed leaves a reviewer to take it on trust. Ours names the standard against each finding.
- Application layer: OWASP WSTG v4.2 and the OWASP API Security Top 10 2023, with findings carrying their OWASP Top 10:2025 category.
- Engagement overall: PTES, the Penetration Testing Execution Standard.
- Cloud: IAM and least privilege, encryption at rest against the policy minimum, environment separation, logging and monitoring as audit evidence.
- Network: perimeter enumeration, edge configuration, transport security, email authentication posture.
- Mobile, where in scope: OWASP MASVS.
Testing is manual exploitation by a named tester. Every engagement is led by Rathnakara GN (M.Sc Cyber Security, OSCP), with Ashok Kamat hands-on alongside him. You can see the standard of the deliverable before you buy: a real anonymized report and the engagement process.
Amazon SP-API DPP pentest questions
Is this the Amazon SP-API security audit?
No, and the distinction is worth getting right before you buy anything, because some vendors sell "the SP-API audit" as though it were theirs to perform. The audit is Amazon's. Section 3 of the Data Protection Policy reserves Amazon the right to audit, assess and inspect the books, records, facilities, operations and security of all systems involved in retrieving, storing or processing Amazon data, and it says Amazon may do that either itself or through an independent certified public accounting firm it selects. So the assessing party is chosen by Amazon and works for Amazon. A penetration testing firm cannot appoint itself to that role, and neither can we. What we do is the other side of it. Clause 2.7.2 obliges you, the Solution Provider, to perform a penetration test at least every 365 days using an industry-recognized methodology. We perform that test and produce the evidence: the report, the Letter of Engagement that shows an independent firm was engaged, and the Letter of Attestation after the retest. That evidence is what the assessment reviews. If a vendor tells you they will conduct your Amazon audit, ask them which Amazon document appoints them, because section 3 names the selector and it is not them.
What does the Amazon SP-API Data Protection Policy require for penetration testing?
Clause 2.7.2 states that the Solution Provider must perform penetration testing at least every 365 days using an industry-recognized methodology, and it enumerates four scope categories: network infrastructure, cloud environments, application-layer assets, and other in-scope systems. It sits alongside 2.7.1, which requires vulnerability scanning at least every 30 days and scanning after significant network, application or infrastructure changes, and 2.7.3, which requires critical findings remediated within 7 days and high within 30. Section 2 applies where a restricted role handles personally identifiable information. Source: the Data Protection Policy on sellercentral.amazon.com.
Do we need the penetration test before Amazon approves a restricted role?
Amazon publishes no rule saying the test must be complete before approval, and we are not going to invent one. What the application asks for is a Security Controls section in your developer profile, alongside Contact Information, Data Access, Roles and Use Cases, and a restricted role review runs in three stages: business, security and technical. Amazon publishes one to two weeks for a standard review where no restricted role is involved, and publishes no duration at all for the restricted role review. So the practical answer is a scheduling one rather than a compliance one. Teams who test first describe controls that exist rather than controls they intend to build, and their 365 day clock under clause 2.7.2 starts from a real test. Teams who test after approval are still inside the policy, because the clause binds the Solution Provider once a role handles personally identifiable information, and they carry the risk that the first test finds something while the application is already live. Neither route is a shortcut past the clause.
Amazon has removed our app after a deadline passed. Can you get it reinstated?
No, and nobody can. Amazon decides whether access comes back, we have no visibility into that decision, and we do not quote a success rate for it. What we can do is produce the evidence the decision reads. That means an assessment of the application in the state it is actually in, starting at the finding that ran out of time rather than at a fresh scope list, with reproduction steps and a CVSS vector string a reader outside your company can recompute, remediation guidance specific enough for your engineers to act on, and verification of the fixed state once they have acted. Clause 2.7.3 is where the deadline came from: critical findings inside 7 days and high inside 30, counted from discovery, with no stated timeline for medium or low. Amazon guidance pages, which sit outside the Data Protection Policy and state that they create no commitments, describe a retest after remediation, and we attribute it that way rather than calling it policy. In reinstatement work we have delivered, the fixed state evidence is the document that gets read hardest. Treat any vendor who promises reinstatement, or quotes a rate for it, as pricing someone else's decision.
How much does an Amazon SP-API DPP penetration test cost?
Our published price. The plan for a DPP submission is the Compliance Plan at INR 1,79,999, which covers two scopes, and each additional scope is INR 74,999. Clause 2.7.2 enumerates four scope CATEGORIES, which is not the same as four scopes: how many sit inside each depends on what you run and what touches Amazon data. Application-layer alone is enumerated in the plural, web applications, APIs, databases and storage systems. Four is the common shape, one each for the web application, the API backend, the cloud environment and the network, and it moves both ways. A seller on managed hosting with no cloud account and no internal network has fewer categories in play; a larger estate has more. We confirm the count at scoping. That is INR 3,29,997. Where the estate allows the work to come to three scopes it is INR 2,54,998. Both figures exclude taxes and both include 12 hours of founder-led consulting and one free retest. We publish this rather than quote the two scope price and raise it once we have seen your architecture.
How long does an SP-API DPP penetration test take?
A scope is six business days, five days of testing and one day writing the report. One scope is 6 and two is 12. A DPP engagement normally covers more surfaces than that, and we confirm the full schedule when we scope the estate. Business days are Monday to Friday; the weekend is a quality buffer and is not counted. The retest itself takes one to three business days.
What methodology do you test against for an SP-API submission?
Clause 2.7.2 requires an industry-recognized methodology, and we name ours in the report rather than asserting it. Application-layer testing follows OWASP WSTG v4.2 and the OWASP API Security Top 10 2023, with findings carrying their OWASP Top 10:2025 category. The engagement overall follows PTES. Cloud work covers IAM and least privilege, encryption at rest against the policy minimum, environment separation, and logging. The report names the standard against each finding, so a reviewer can see which methodology was applied rather than taking the word for it.
Do you have experience with SP-API DPP submissions specifically?
Yes. Two Amazon Solution Providers have engaged Cybersecify for the clause 2.7.2 penetration test under signed statements of work, and we have completed DPP renewal work for a Solution Provider. We also publish the evidence set from a DPP engagement of our own: three reports covering the clause 2.7.2 scope categories, available on request. Two limits in the same breath, because a number without them is worth less than no number. We quote no approval rate and have none to quote: Amazon decides submissions, we are not in that room, and one outcome would not be a rate in any case. And we describe our own work rather than any customer's situation, so you will not find a client named here or an account of what any of them were going through. What we can show you is the work. We also publish what the policy requires in detail, including the parts that are commonly misread, such as the fact that the DPP contains no SOC 2 or ISO 27001 requirement and that its stated encryption minimum at rest is AES 128 or RSA 2048 rather than AES 256.
Does Amazon require a SOC 2 or ISO 27001 report as part of the DPP?
No. The Data Protection Policy contains no SOC 2 and no ISO 27001 requirement. Control mapping to those frameworks is useful for your own auditors and for enterprise customers asking security questions, and we include it on the Compliance Plan, but it is not something Amazon asks for in a DPP submission. Treat anyone selling it as an Amazon requirement with caution.
Do I need to send Amazon the penetration test report?
Not routinely. The policy has no clause requiring you to upload or send the report as a matter of course. Section 3 requires that you maintain the books and records needed to verify compliance during the agreement and for 12 months afterwards, and that upon written request you certify in writing that you are compliant, with Amazon reserving a right to audit. So the report is evidence you hold rather than evidence you file, which is why the quality of the document and the methodology it names matter.
What happens if findings come back critical?
Clause 2.7.3 sets the clock: critical findings remediated within 7 days and high within 30. Your report is ordered so the items on those clocks are unambiguous, each with reproduction steps and specific remediation guidance rather than a generic recommendation. The free retest then confirms the fixes and produces a v2.0 report recording the closed state, which is the document you want on file when section 3 is invoked.
Start with your situation, then your architecture
Listing an app, renewing under the 365 day clock, or getting back an app Amazon has removed. Those three need different scopes and different documents, and the difference is worth settling before you commit. Then tell us what the integration touches, because how many of the four categories apply depends on your estate, and that is the difference between three scopes and four. Both co-founders are on the call.
Where these requirements come from
Everything this page says about the platform's requirements is taken from the platform's own published documentation, linked below and last checked on 2026-09-30. We quote the requirement rather than our reading of it wherever the difference matters.
- Amazon Selling Partner API: Data Protection Policy (clause 2.7.2)
- Amazon SP-API: guidance to address key security controls
- Amazon SP-API: vulnerability management
The Data Protection Policy text behind the clause 2.7 requirements on this page was last read in full on 2026-09-30. A re-check on 2026-10-03 could not load Amazon's documentation host, so the earlier date is the one stated rather than carried forward silently.
Our aim is to describe these requirements as accurately and as currently as we can, and to show you where to check us. We are reading someone else's documentation: a platform can revise it without an announcement, and our reading of it can be imprecise or go out of date.
How we source, draft and review what we publish, including where software sits in the drafting, is set out in our editorial policy. A page like this is only as good as the date on it, so we re-read the sources on a standing audit, date what we checked, and update the page when a source moves or when we can state something more precisely.
If something here no longer matches the source, tell us at errors@cybersecify.com. We will review it against the source and tell you what we decide; where it needs changing we change it and date the change.
This page is published for information. It is a best-effort account of someone else's published requirements, not a commitment about your engagement: what we deliver, and what it costs, is set out in the Statement of Work both parties sign, and our terms state that where website content and a signed agreement differ, the signed agreement governs.