DL-038 · Case study
Security readiness review for a multi-tenant SP-API app
A SaaS for Amazon sellers faced Amazon's data-protection assessment. We reviewed its cloud setup, tested a dev environment and checked tenant isolation first.
- Client
- Name withheld
- Location
- Israel
- Industry
- SaaS for Amazon sellers
- Capabilities
- 01Audit04Secure
01
Challenge
- Amazon's data-protection assessment was coming for a multi-tenant SP-API app.
- The team wanted an outside view before the assessor's questions arrived.
- Many sellers' data shares one platform, so isolation had to be proven.
02
Environment
- Multi-tenant SaaS holding SP-API data for many seller accounts.
- Production and development environments on AWS.
- Fixed, time-boxed review scope agreed up front.
03
Intervention
- Read-only review of the AWS account: access, network, storage and logging.
- Penetration test of the development environment, never production.
- Tenant-isolation tests: can one seller's session reach another's data?
- Mapped the review against Amazon's Data Protection Policy requirements.
04
Outcome
- A written report the team can act on before the assessment.
- Each item tied to the Amazon requirement it affects.
- Production stayed untouched throughout the review.
- 01SP-APISeller data→PRODUCTIONRead-only review
- 02REVIEWScope + tests- -PRODUCTIONRead-only reviewread-only
- 03REVIEWScope + tests→DEV ENVPentest targetpentest
- 04REVIEWScope + tests→TENANTS A / BIsolation tests
- 05REVIEWScope + tests→REPORTWritten
Stack and services.
Tell us what has to work.
A senior engineer reads every brief. Describe the system, what it runs on today and what happens when it fails.
Discuss a project→