Discuss a project

DL-052 · Case study

Amazon SP-API security and restricted data readiness for a SaaS platform

An Amazon software provider needed to strengthen its security architecture before expanding features requiring restricted buyer information.

Client
Name withheld
Location
Israel
Industry
B2B eCommerce SaaS
Capabilities
01Audit04Secure
01

Challenge

  • Buyer information moved through multiple services without sufficiently documented access boundaries.
  • Existing security documentation did not fully describe data retention and incident-response procedures.
02

Environment

  • Amazon SP-API, AWS-hosted services and multi-tenant databases.
  • Customer authorization workflows and restricted-data processing requirements.
03

Intervention

  • Reviewed infrastructure, access controls, encryption and data processing paths.
  • Designed least-privilege access boundaries and retention policies.
  • Prepared technical controls, evidence requirements and remediation priorities for compliance review.
04

Outcome

  • A documented restricted-data security architecture.
  • A prioritized remediation plan supporting future independent assessment and Amazon review.
Authorization, controlled API access, encrypted processing and retention enforcement.SELLER AUTHAuthorizationSP-APIRestricted dataACCESS LAYERLeast privilegeENCRYPTED STOREProcessingRETENTIONPolicy
  1. 01SELLER AUTHAuthorizationSP-APIRestricted data
  2. 02SP-APIRestricted dataACCESS LAYERLeast privilege
  3. 03ACCESS LAYERLeast privilegeENCRYPTED STOREProcessing
  4. 04ENCRYPTED STOREProcessingRETENTIONPolicy
Fig. 01Restricted data boundariesAuthorization, controlled API access, encrypted processing and retention enforcement.Scale NTS

Stack and services.

Stack02

  • Amazon SP-API
  • AWS

Services used02

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