Step 2: Conducting a Security and Threat Assessment for AWS | stackArmor “Security by Design“

October 9, 2018
stackArmor

Establishing a strong cybersecurity and compliance program is critical to ensuring the confidentiality, integrity and availability of digital assets. The cloud makes this easy due to readily available tools and automation services. Organizations looking to adopt security standards like FISMA, FedRAMP, HIPAA, PCI-DSS or NIST Cybersecurity Framework need to follow a “Security By Design” methodology right from the beginning to avoid costly remediations later.

stackArmor’s Security by Design methodology includes three key steps:

1. Creating a compliant application and data architecture that uses certified cloud services.

2. Conducting a security and compliance assessment

3. Continuous monitoring and management.

As part of Step 2, you can start by actually doing a simple, and rapid Security and Threat Self-Assessment in 10 minutes or less. stackArmor’s cybersecurity and cloud architecture experts have this initial assessment tool to help benchmark and assess your current state.

Watch this simple video to learn how you use the security self-assessment tool:

MOST RECENT

Beyond the Patch: A Real-World Look at FedRAMP Vulnerability Response

What happens when a critical vulnerability threatens a FedRAMP-authorized environment, but the patch isn’t available? Explore how real-time visibility, immediate mitigation, and vendor coordination transformed a vulnerability response into a practical example of risk-based security operations.

Dear Agencies: Let’s Make CR26 Work

FedRAMP’s Consolidated Rules for 2026 move federal cloud compliance toward structured, machine-readable certification data. The transition depends on agencies modernizing their own processes while preserving reciprocity and risk-based security.

209 Controls, 46 KSIs, and One Very Avoidable Compliance Catastrophe

FedRAMP is moving toward 20x, but federal agencies still rely on NIST SP 800-53 Rev. 5 evidence for authorization decisions. Johann Dettweiler explores how CSPs can use one evidence layer, KSI-to-control mapping, and automation to support both.