3 ms·
> GuardDuty’s role as a required control for PCI DSS and NIST.800-53.r5 This isn't true and the link to the source is a 404 page. It was already too much conte
by arpinum 2y ago
> GuardDuty’s role as a required control for PCI DSS and NIST.800-53.r5
This isn't true and the link to the source is a 404 page. It was already too much content marketing, no need to read beyond that line.
- ramimac 2y agoNot sure how the link got munged, but the root is https://docs.aws.amazon.com/securityhub/latest/userguide/guardduty-controls.html#guardduty-1 https://docs.aws.amazon.com/securityhub/latest/userguide/gua... It's definitely a bit of a simplification - although I'm not aware of large orgs using anything else to meet the relevant PCI requirement The whitepaper AWS commissioned helping explain GuardDuty to auditors[1] is definitely a large component there [1] https://d1.awsstatic.com/certifications/foregenix_amazon_guardduty_security_review_07-2020.pdf https://d1.awsstatic.com/certifications/foregenix_amazon_gua...
- acdha 2y agoThat doesn’t mean that they’re saying Guard Duty is required but rather that it’s one way to satisfy that need. If you picked a different product, you could disable that control in Security Hub.