Amazon Web Services
Amazon Web Services offers a portfolio covering assessing cloud exposure or protecting running workloads, identifying and prioritizing security weaknesses, understanding sensitive information and controlling its exposure, protecting availability during malicious traffic floods and applying security rules to application requests. The entries in this catalog include Amazon GuardDuty, Amazon Inspector, Amazon Macie, AWS Security Hub, AWS Shield and AWS WAF. Amazon GuardDuty focuses on cloud threat detection and suspicious activity monitoring. Amazon Inspector focuses on cloud workload vulnerability assessment. Amazon Macie focuses on cloud data discovery and sensitive data detection. When reviewing Amazon Web Services, compare the named products individually: a platform family, a specific module and a managed service can have different scopes and purchasing requirements. Selection should account for enabled protection plans, permissions, finding triage and the downstream response workflow. Portfolio detail - Amazon GuardDuty: the catalog lists AWS account threat findings, Cloud security posture management, Vulnerability prioritization. - Amazon Inspector: the catalog lists EC2 workload assessment, ECR container image assessment, Lambda vulnerability assessment. - Amazon Macie: the catalog lists Amazon S3 sensitive-data assessment, S3 data protection findings, Sensitive data discovery. - AWS Security Hub: the catalog lists AWS security findings aggregation, Cloud security posture management, Vulnerability prioritization. - AWS Shield: the catalog lists AWS DDoS protection scope, DDoS attack detection, Network-layer protection. - AWS WAF: the catalog lists Web ACL administration, Managed rule groups, Web request filtering. For procurement, map each required capability to a named offering and confirm the edition, dependencies and delivery responsibility with the vendor. Product-level entries below provide the operational context and evaluation questions for that comparison.
Documented Software Products (6)
Amazon GuardDuty
Amazon GuardDuty from Amazon Web Services focuses on cloud threat detection and suspicious activity monitoring. It is cloud threat detection service used for detecting suspicious activity across supported AWS security signals. Capabilities - AWS account threat findings: Analyzes the AWS security signals documented for this managed threat-detection service. - Cloud security posture management: Finds cloud configuration risks so teams can prioritize corrections across connected environments. - Vulnerability prioritization: Helps order remediation work using the risk context available in the platform. Use and operational context Amazon GuardDuty is relevant to security teams monitoring AWS accounts and workloads when the requirement centers on detecting suspicious activity across supported AWS security signals. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review enabled protection plans, permissions, finding triage and the downstream response workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Amazon GuardDuty focuses on detecting suspicious activity across supported AWS security signals. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Amazon Inspector
Amazon Inspector from Amazon Web Services focuses on cloud workload vulnerability assessment. It is cloud vulnerability assessment service used for assessing supported AWS workloads and software assets for vulnerabilities. Capabilities - EC2 workload assessment: Assesses the Amazon EC2 workloads included in the configured vulnerability assessment scope. - ECR container image assessment: Brings supported Amazon ECR image assets into the vulnerability assessment workflow. - Lambda vulnerability assessment: Addresses supported AWS Lambda assets under the scanning options documented by AWS. - Vulnerability scanning: Finds potential weaknesses that can be reviewed and prioritized for remediation. - Risk-based prioritization: Uses the available risk context to help order remediation work. - Configuration assessment: Identifies configuration issues as a separate source of security exposure. - Exposure reporting: Provides views for communicating the assessed exposure and progress of remediation work. - Cloud exposure assessment: Brings the connected cloud environments into the documented exposure assessment scope. Use and operational context Amazon Inspector is relevant to teams remediating weaknesses in their AWS estate when the requirement centers on assessing supported AWS workloads and software assets for vulnerabilities. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review asset coverage, scanning settings, finding prioritization and ownership of workload remediation. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Amazon Inspector focuses on assessing supported AWS workloads and software assets for vulnerabilities. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Amazon Macie
Amazon Macie from Amazon Web Services focuses on cloud data discovery and sensitive data detection. It is sensitive-data discovery service used for assessing sensitive information stored in supported Amazon S3 data. Capabilities - Amazon S3 sensitive-data assessment: Focuses the documented sensitive-data discovery workflow on supported Amazon S3 data. - S3 data protection findings: Connects sensitive-data discovery with findings relevant to how the assessed S3 data is protected. - Sensitive data discovery: Finds protected information so teams can establish where it is stored or used. - Data access visibility: Shows who or what can access the covered data assets. - Data protection policy management: Gives teams a way to administer data protection rules across the product's supported scope. Use and operational context Amazon Macie is relevant to AWS teams overseeing the protection of S3 data when the requirement centers on assessing sensitive information stored in supported Amazon S3 data. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review bucket scope, discovery-job configuration, data identifiers and who investigates a sensitive-data finding. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Amazon Macie focuses on assessing sensitive information stored in supported Amazon S3 data. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
AWS Security Hub
AWS Security Hub from Amazon Web Services focuses on cloud security findings and posture assessment. It is cloud security findings technology used for aggregating and assessing security findings in AWS. Capabilities - AWS security findings aggregation: Consolidates the security findings supplied by the supported AWS services and integrations. - Cloud security posture management: Finds cloud configuration risks so teams can prioritize corrections across connected environments. - Vulnerability prioritization: Helps order remediation work using the risk context available in the platform. Use and operational context AWS Security Hub is relevant to teams coordinating AWS security posture and alert review when the requirement centers on aggregating and assessing security findings in AWS. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review enabled controls, connected findings sources, regional coverage and how findings reach the responsible team. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? AWS Security Hub focuses on aggregating and assessing security findings in AWS. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
AWS Shield
AWS Shield from Amazon Web Services focuses on cloud DDoS protection and mitigation. It is DDoS mitigation technology or service used for protecting availability during malicious traffic floods. Capabilities - AWS DDoS protection scope: Provides the AWS-managed attack protection approach described for the selected Shield service tier. - DDoS attack detection: Identifies traffic associated with distributed denial-of-service activity. - Network-layer protection: Addresses the network-layer attack scope stated by the vendor. - Application-layer protection: Addresses application-focused availability attacks where included in the offering. - Attack visibility and reporting: Provides information for assessing observed attack traffic and mitigation activity. - Mitigation orchestration: Supports applying the mitigation approach documented for the deployment. Use and operational context AWS Shield is relevant to organizations safeguarding network or application availability when the requirement centers on protecting availability during malicious traffic floods. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review traffic routing, attack coverage, mitigation activation and communication arrangements during an attack. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? AWS Shield focuses on protecting availability during malicious traffic floods. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
AWS WAF
AWS WAF from Amazon Web Services focuses on web request filtering and application attack protection. It is web application firewall service used for applying access rules to requests received by supported AWS web resources. Capabilities - Web ACL administration: Organizes web request protection through the web access control lists documented by AWS. - Managed rule groups: Supports evaluating vendor-managed rules alongside the organization's own web traffic policies. - Web request filtering: Applies protection rules to requests reaching the web applications covered by the deployment. - DDoS mitigation integration: Can be evaluated within the vendor's documented application availability and attack mitigation scope. Use and operational context AWS WAF is relevant to teams protecting AWS application endpoints when the requirement centers on applying access rules to requests received by supported AWS web resources. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review web ACL association, rule groups, request inspection settings and legitimate-traffic testing before enforcement. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? AWS WAF focuses on applying access rules to requests received by supported AWS web resources. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.