Information Security Policy

1. Purpose

Define baseline controls to protect Shopedge systems and customer data.

All production infrastructure, services, environments, and any personnel with production access.

Production access is restricted to authorized personnel only (currently: founder and approved team members).
Access is managed through AWS console/IAM with least-privilege permissions and role-based access where applicable.
Access is removed when no longer needed.
Administrative actions and access events are logged using AWS auditing capabilities (e.g., CloudTrail) where enabled.

In transit: TLS is used for data transmitted between clients and Shopedge services and for service-to-service communication where applicable.
At rest: data stored in AWS services is encrypted at rest using AWS-managed encryption with AWS KMS-managed keys.

Credentials and secrets are stored in managed configuration/secret mechanisms and are not embedded in source code.
Secret access is limited to services/roles that require it.

Operational logs are collected to support troubleshooting and security investigation.
Monitoring/alerting is used for key application and infrastructure errors where feasible.
Logs are retained according to operational needs.

Dependencies and services are updated regularly, prioritizing security fixes based on severity and exposure.
Current state: vulnerability management is handled through routine dependency updates and maintenance.
Planned improvement: introduce structured dependency scanning and a defined review cadence for vulnerabilities.

Security incidents are triaged, contained, and remediated.
Incidents are documented (timeline, impact, remediation, preventive actions).
Customer/partner notifications occur when required by law, contract, or incident impact.

Shopedge is hosted on AWS managed services designed for high durability.
DynamoDB Point-in-Time Recovery (PITR) is enabled for critical production tables to protect against accidental writes/deletes and support recovery for up to the configured retention window.
Restoration is performed by restoring to a new table and following an internal recovery procedure to resume service.
Non-critical tables may not have PITR enabled during the MVP phase; coverage is reviewed periodically and expanded based on risk.

Shopedge relies on AWS for underlying infrastructure security controls.
Third-party tools are used only as needed; access is scoped to the minimum required.

Personnel with production access are expected to follow secure handling practices (credentials, access, data handling).
Planned improvement: introduce periodic security awareness refreshers as the team grows.

Exceptions must be documented and approved by the Security Owner, including compensating controls and a remediation plan.