Course contentsShow
← Security
Lesson 2028 of 3,05241. Secure Development LifecycleFree lesson

Security Requirements Elicitation

Learn to identify and document security requirements early by analyzing business context, regulatory needs, and threat landscape.

Security Requirements Elicitation

What you'll learn: How to systematically discover and document the security needs of your cloud infrastructure before you build it.


What Is Security Requirements Elicitation?

Security requirements elicitation is the disciplined process of identifying, gathering, and documenting what security controls and properties your system must have—before writing a single line of code or deploying infrastructure. Instead of bolting on security after problems arise, you're discovering security needs upfront by analyzing three key dimensions: business context, regulatory obligations, and threat landscape.

Think of it like a home builder consulting with you about locks, alarms, and fire safety before breaking ground—not after you move in and discover you needed a safe room.

The Three Pillars

  1. Business Context Analysis: What does this system do? What data does it handle? Who are the users? What would happen if it were compromised? A public marketing site has vastly different security needs than a patient health portal.

  2. Regulatory and Compliance Needs: What laws, standards, or frameworks apply? HIPAA for healthcare data, PCI DSS for payment cards, GDPR for EU customer data? These aren't optional—they dictate baseline security requirements like encryption, access logging, and data retention.

  3. Threat Landscape Assessment: What attacks are realistic for your environment? If you're deploying Kubernetes with public APIs, you need to consider container escape threats. If using IaC with Terraform state files, you must protect secrets in that state.

How It Works in Practice

During elicitation, you work with stakeholders—developers, compliance officers, business owners—to extract requirements like:

  • "All database connections must use TLS 1.3 or higher"
  • "User authentication requires MFA for privileged roles"
  • "Infrastructure drift must be detected within 24 hours"

These become testable, enforceable criteria in your Secure Development Lifecycle.

Key Takeaway: Security requirements elicitation transforms vague "be secure" goals into concrete, actionable controls by systematically analyzing business needs, compliance mandates, and realistic threats before deployment begins.