Security at Enreship

Enreship's application requires authenticated access and applies role-based authorization to protected functions. Connected marketplace authorization uses platform OAuth flows where supported. Amazon Information is processed within an AWS VPC. Databases, storage, and internal services use private subnets without public database access.

Public traffic enters through ALB or API Gateway endpoints protected by security groups, network ACLs, AWS WAF, AWS Network Firewall, and AWS Shield. Administrative access requires SSO, MFA, least-privilege IAM, and time-limited VPN or SSM sessions. AWS Config and CloudWatch monitor configuration changes. Managed endpoints use disk encryption, endpoint protection, screen locks, and security patching.

SP-API, LWA, database, and carrier credentials are encrypted in AWS Secrets Manager using KMS, least-privilege IAM, MFA for administrators, access logging, and scheduled rotation. They are never hard-coded, committed to repositories, shared through chat or tickets, or stored in plaintext. CI/CD secret scanning blocks exposed credentials, and suspected credentials are revoked and rotated immediately.

Access to seller and shipping information is limited to the workflow and personnel that require it. Each approved employee uses a unique SSO and IAM identity; shared accounts are prohibited and MFA is mandatory. Least-privilege role-based access is denied by default, and production elevation is approved and time-limited.

Access is reviewed quarterly and removed within 24 hours of a termination or role change. AWS CloudTrail records user, role, API, and administrative activity for at least 12 months.

Only company-managed, encrypted endpoints may access systems processing Amazon Information. Central endpoint security and data-loss-prevention controls enforce device compliance, anti-malware, screen locks, removable-media blocking, and restrictions on mobile and unapproved file transfers. Connection, USB, and DLP events are sent to centralized monitoring and violations generate real-time security alerts. Personal devices are denied access.

Shipping information may include recipient name, delivery address, phone number when provided, order and shipment identifiers, parcel details, labels, and tracking events. It is used for order and delivery operations, not for advertising or buyer profiling.

For the planned Amazon integration, Amazon Restricted PII is limited and deleted as described in the Privacy Policy and planned SP-API data handling page.

Amazon Information stored in AWS RDS, S3, volumes, caches, and backups is encrypted at rest with AES-256 using AWS KMS-managed keys. Keys are kept separate from encrypted data, restricted by least-privilege IAM, audited through CloudTrail, rotated at least annually, and revoked immediately upon suspected compromise. SP-API and carrier credentials are encrypted in AWS Secrets Manager.

AES-256/KMS-encrypted backups are replicated from the United States to a geographically separate European AWS Region. Access is restricted to approved administrators and logged. Quarterly restore tests validate infrastructure recovery, data integrity, and the PII-deletion process. Recovery targets are a four-hour RPO and one-hour RTO, and PII-bearing backups expire within 30 days.

CloudTrail, VPC Flow Logs, RDS audit logs, CloudWatch, and sanitized Sentry events are centrally monitored. Logs capture identities, timestamps, access attempts, configuration changes, failures, and alerts while excluding PII and secrets. Logs are KMS-encrypted, tamper-protected, retained for at least 12 months, and reviewed manually at least every two weeks. Automated alerts notify the security team and investigations preserve evidence and track containment through closure.

Enreship conducts vulnerability scans at least every 30 days and an independent penetration test at least annually. Findings are risk-rated with CVSS and tracked in Jira with an owner and due date. Critical findings are contained within one hour and fixed within 24 hours; high findings are fixed within seven days and medium findings within 30 days. Closure requires documented rescanning or retesting.

SonarQube scans every pull request and blocks releases with new Critical or Blocker findings. AWS Inspector, GuardDuty, Config, and Security Hub monitor runtime risks. Changes are tested in a dedicated environment, peer-reviewed, approved by authorized personnel, rescanned, and deployed from clean images through controlled CI/CD.

Enreship maintains an incident-response plan with defined roles and reviews it at least every six months. CloudWatch, GuardDuty, Macie, CloudTrail, and RDS audit alerts support detection. The response team revokes credentials, ends sessions, isolates resources, blocks malicious traffic, preserves evidence, determines scope, repairs the cause, rotates credentials, and restores clean systems. Amazon is notified at security@amazon.com within 24 hours of detecting an incident involving Amazon Information.

This page does not represent an Amazon approval or security certification. Control evidence is maintained separately for assessment and audit purposes.

Please report suspected vulnerabilities, unauthorized access, or privacy incidents to info@enreship.com. Include enough detail to reproduce or investigate the issue, but do not send passwords, access tokens, or customer PII by email.