ISO/IEC 27034 Lead Application Security Auditor — Lesson 3: Audit Execution, Interviews, Testing, Findings, Nonconformities, and Conclusions

Learning Objectives

• Interpret the requirements, principles, roles, and dependencies shaping audit execution, interviews, testing, findings, nonconformities, and conclusions.
• Apply a practical workflow and create a reviewable application security findings register.
• Evaluate the exception where control effectiveness is inferred from policy documents and determine proportionate follow-up.

Detailed Topics

• Audit Execution applied to the course scenario and expected evidence.
• Interviews applied to the course scenario and expected evidence.
• Testing applied to the course scenario and expected evidence.
• Findings applied to the course scenario and expected evidence.
• Nonconformities applied to the course scenario and expected evidence.
• and Conclusions applied to the course scenario and expected evidence.

Instructor Demonstration

The instructor traces a case involving a software portfolio undergoing assurance across product governance, secure development, cloud deployment, and maintenance. The demonstration links decisions to objective evidence, records the result in application security findings register, and tests the condition where control effectiveness is inferred from policy documents.

Hands-On Exercise

Complete a controlled exercise covering Audit Execution, Interviews, Testing, Findings, Nonconformities, and Conclusions. Confirm scope and responsibilities, examine the stated exception, reach a supported conclusion, and preserve the outcome in application security findings register.

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 security findings register 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 “control effectiveness is inferred from policy documents” 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 security findings register 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 Audit Execution, Interviews, Testing, Findings, Nonconformities, and Conclusions, explain the reasoning used, and defend the result through application security findings register.