“Cramming for FISMA”: How to Launch a NIST 800-53 Moderate System in 180 Days
Johannes Wiklund, VP of IT and Cyber Security, Somos What do you do when a federal agency asks your company to build a new system in 180 days and throws in “FISMA compliance” as a requirement? Based on real-world experience from the trenches, this session will cover potential pitfalls in deploying a system that must meet the NIST 800-53 security controls, and give actionable advice on how to overcome challenges and be ready for a FISMA Assessment. Pre-Requisites: Basic understanding of of AWS service architecture and compliance frameworks and a high-level knowledge of system architecture and operations.
▶︎
Humanizing Privacy with Power of User Experience (UX)
▶︎
Implementing a Quantitative Cyber-Risk Framework: A FinSrv Case Study
▶︎
AWS re:Inforce 2019: Aligning to the NIST Cybersecurity Framework in the AWS Cloud (GRC203-R)
▶︎
The First 6 Months as a CISO Determines Success or Failure
▶︎
Understanding FISMA and FedRamp
▶︎
NIST Cybersecurity Framework Full Tutorial | Step-by-Step Implementation Guide for Beginners
▶︎
Understanding the 2024 Updates to the NIST Cybersecurity Framework
▶︎
A Deep Dive on the NIST 800-53 Rev.4 to Rev. 5 Transition - Part 1
▶︎
A Cloud Security Architecture Workshop
▶︎
NIST Cybersecurity Framework and PCI DSS
▶︎
eMASS, the True Story
▶︎
Conducting a cybersecurity risk assessment
▶︎
Virtual Session: NIST Cybersecurity Framework Explained
▶︎
The 20 Critical Security Controls: From Framework to Operational to Implementation
▶︎
NIST 800-171 assessment, from an auditor's perspective
▶︎
RMF Security Control Testing Hands On (Using SP 800-53 and 800-53A)
▶︎
GRC | NIST 800-30 Guide for Conducting Risk Assessments. Enterprise Organizational Risk Security
▶︎
Accelerating FedRAMP, FISMA, and CMMC Compliance on Cloud
▶︎
Phil Venables on AI for Security & Security for AI: the Future of Agentic Risk | NHIcon 2026
▶︎