AWS marketplace medium security documentation change
Summary
Updated AMI and container deployment requirements to mandate publishing as separate Marketplace products with CVE scanning
Security assessment
Added explicit requirements for vulnerability scanning (CVEs) and security compliance checks for AMI/container products. This directly addresses security controls by enforcing Marketplace scanning before deployment.
Diff
diff --git a/marketplace/latest/userguide/saas-guidelines.md b/marketplace/latest/userguide/saas-guidelines.md index 8de5b0fd2..5ea4b53bc 100644 --- a//marketplace/latest/userguide/saas-guidelines.md +++ b//marketplace/latest/userguide/saas-guidelines.md @@ -140 +140 @@ You must include an architecture diagram for review. You can't make the diagrams - * If Amazon Machine Images (AMIs) are deployed into the buyer's AWS account, they must comply with [AWS Marketplace policies for AMIs](https://docs.aws.amazon.com/marketplace/latest/userguide/product-and-ami-policies.html). Your AMIs must [pass the AMI scanner](https://docs.aws.amazon.com/marketplace/latest/userguide/best-practices-for-building-your-amis.html#self-service-scanning) in the AWS Marketplace Management Portal (seller portal). When [requesting your product to be public](https://docs.aws.amazon.com/marketplace/latest/userguide/saas-product-settings.html#saas-update-visibility), you must also [contact AWS Marketplace operations](https://aws.amazon.com/marketplace/management/contact-us) and provide proof of scan results. + * If an Amazon Machine Image (AMI) is deployed into the buyer's AWS account, it must comply with the [AMI-based product requirements for AWS Marketplace](./product-and-ami-policies.html). You must publish the AMI as a separate AMI-based product in AWS Marketplace and indicate that it's an add-on product as required in the [Product usage policies](./product-and-ami-policies.html#product-usage). You can price your AMI-based product as BYOL because it's an extension of your SaaS offering. AWS Marketplace scans AMI-based products for unpatched common vulnerabilities and exposures (CVEs) and security requirements. Your buyers must also subscribe to your AMI-based product before deploying it. @@ -142 +142 @@ You must include an architecture diagram for review. You can't make the diagrams - * If container images are deployed into a buyer's AWS account, the images must comply with [AWS Marketplace policies for containers](https://docs.aws.amazon.com/marketplace/latest/userguide/container-product-policies.html). Your container images can be hosted outside of AWS, but they must be [scanned in Amazon Elastic Container Registry (Amazon ECR)](https://docs.aws.amazon.com/AmazonECR/latest/userguide/manual-scan.html) and be free of critical vulnerabilities. When [requesting your product to be public](https://docs.aws.amazon.com/marketplace/latest/userguide/saas-product-settings.html#saas-update-visibility), you must also [contact AWS Marketplace operations](https://aws.amazon.com/marketplace/management/contact-us) and provide proof that the container passed the scan. + * If a container image is deployed into a buyer's AWS account, it must comply with the [Container-based product requirements for AWS Marketplace](./container-product-policies.html). You must publish the container image as a separate container-based product in AWS Marketplace and indicate that it's an add-on product as required in the [Product usage requirements](./container-product-policies.html#container-usage-requirements). You can price your container-based product as BYOL because it's an extension of your SaaS offering. AWS Marketplace scans container-based products for unpatched common vulnerabilities and exposures (CVEs) and security requirements. Your buyers must also subscribe to your container-based product before deploying it.