ISO/IEC 27034 Lead Application Security Implementer — Lesson 2: Application Risk Assessment, Security Requirements, Architecture, and Control Selection

Learning Objectives

• Interpret the requirements, principles, roles, and dependencies shaping application risk assessment, security requirements, architecture, and control selection.
• Apply a practical workflow and create a reviewable application risk and requirements specification.
• Evaluate the exception where architecture decisions omit high-risk data-flow threats and determine proportionate follow-up.

Detailed Topics

• Application Risk Assessment applied to the course scenario and expected evidence.
• Security Requirements applied to the course scenario and expected evidence.
• Architecture applied to the course scenario and expected evidence.
• and Control Selection applied to the course scenario and expected evidence.

Instructor Demonstration

The instructor traces a case involving a software organization integrating security into product governance, architecture, development, testing, release, and maintenance. The demonstration links decisions to objective evidence, records the result in application risk and requirements specification, and tests the condition where architecture decisions omit high-risk data-flow threats.

Hands-On Exercise

Complete a controlled exercise covering Application Risk Assessment, Security Requirements, Architecture, and Control Selection. Confirm scope and responsibilities, examine the stated exception, reach a supported conclusion, and preserve the outcome in application risk and requirements specification.

1. Define the objective, boundaries, stakeholders, criteria, and expected work product.
2. Perform the activity while recording assumptions, observations, evidence, and decisions.
3. Test normal operation, the exception, and an escalation or follow-up condition.
4. Document conclusions, owners, deadlines, verification methods, and review triggers.

Scenario Analysis

• Identify the requirement or control with the strongest influence on the scenario outcome.
• Compare two defensible responses and explain their risk, operational, and evidence trade-offs.
• Decide how the application risk and requirements specification should be approved, retained, reviewed, and updated.

Troubleshooting Guidance

Start where expected practice and observed evidence first diverge. Separate a missing record from an ineffective process, distinguish unclear ownership from a control failure, and treat “architecture decisions omit high-risk data-flow threats” as a hypothesis until tested against the applicable criteria and intended outcome.

Validation Checklist

• Scope, roles, criteria, stakeholders, dependencies, and intended outcomes are explicit.
• The application risk and requirements specification connects conclusions to objective, reviewable support.
• Normal operation, the stated exception, escalation, and follow-up were evaluated.
• Owners, due dates, verification methods, review triggers, and improvement actions are clear.

Lesson Outcome

Learners can apply Application Risk Assessment, Security Requirements, Architecture, and Control Selection, explain the reasoning used, and defend the result through application risk and requirements specification.