| AWS re:Inforce 2024 - Elevate your AWS security with CloudFastener, assisted by gen AI (APS225-S) |
2024-06-14 |
| AWS re:Inforce 2024 - Verifying code using automated reasoning (APS402) |
2024-06-14 |
| AWS re:Inforce 2024 - Keeping your code secure (APS401) |
2024-06-14 |
| AWS re:Inforce 2024 - Building a secure MLOps pipeline, featuring PathAI (APS302) |
2024-06-14 |
| AWS re:Inforce 2024 - How to fail at building a security champions program (APS326) |
2024-06-14 |
| AWS re:Inforce 2024 - I don’t always do AppSec testing, but when I do, it’s in production (APS324-S) |
2024-06-13 |
| AWS re:Inforce 2024 - Securing cloud innovation: Lessons learned (APS223-S) |
2024-06-12 |
| AWS re:Inforce 2024 - Innovate w/ confidence across your AI-powered software supply chain (APS227-S) |
2024-06-12 |
| AWS re:Inforce 2024 - Security lifecycle management in a multicloud world (APS222-S) |
2024-06-12 |
| AWS re:Inforce 2024 - Cloud security reimagined: The generative AI advantage (APS221-S) |
2024-06-12 |
| AWS re:Inforce 2024 - Accelerate securely: The Generative AI Security Scoping Matrix (APS201) |
2024-06-12 |
| AWS re:Inforce 2024 - Supply chain security: AWS Signer for build attribution (APS323) |
2024-06-12 |
| AWS re:Inforce 2024 - Enhance AppSec: Generative AI integration in AWS testing (APS301) |
2024-06-12 |
| AWS re:Inforce 2024 - Deep dive into Amazon Bedrock security architecture (APS224) |
2024-06-12 |
| AWS re:Inforce 2024 - Using generative AI to create more secure applications (APS321) |
2024-06-12 |
| AWS re:Inforce 2024 - Strengthen open source software supply chain security: Log4Shell to xz (APS303 |
2024-06-11 |