ISO 27034

ISO 27034 checklist: Assess application security compliance

Applications are at the center of modern business operations. Organizations use them to manage customer information, process payments, connect business systems, and deliver digital services. However, as application environments grow, maintaining consistent security practices becomes increasingly difficult.

A company may have documented security policies, regular vulnerability scans, and established development procedures. Yet important questions can remain unanswered. Who is responsible for approving application security risks? Are security controls verified before deployment? Can the organization demonstrate that critical applications follow approved security practices?

These gaps can create serious problems during security assessments, internal audits, and customer compliance reviews.

An ISO 27034 checklist helps organizations evaluate whether their application security governance processes are clearly defined, consistently implemented, and supported by reliable evidence.

ISO/IEC 27034 provides an international framework for integrating security into application management processes. It helps organizations manage application security across internally developed software, purchased applications, and outsourced development arrangements.

This guide provides a practical ISO 27034 assessment checklist covering governance, application inventories, risk assessments, security controls, verification, documentation, and ongoing oversight. It also explains how to score assessment results, prioritize weaknesses, and prepare a corrective action plan.

What is an ISO 27034 checklist?

An ISO 27034 checklist is a structured assessment tool used to evaluate how effectively an organization manages application security governance, risks, controls, and supporting evidence.

It helps security teams, application owners, compliance professionals, and internal auditors review whether important application security activities are documented and operating as intended.

The checklist draws on the main concepts of the ISO/IEC 27034 series, including the Organization Normative Framework (ONF), Application Normative Framework (ANF), Application Security Management Process (ASMP), and Application Security Controls (ASCs).

It can be used during internal reviews, security program assessments, application onboarding, and improvement planning.

Is ISO 27034 a certification standard?

ISO 27034 is a multipart application security standards series. It does not provide a generally recognized standalone accredited organizational certification scheme comparable to ISO/IEC 27001.

Individual parts of ISO 27034 contain guidance and, where applicable, specific process requirements. Organizations should consult the relevant publications when evaluating conformity with a particular part.

Therefore, the checklist in this article should be treated as a practical assessment framework rather than a complete list of mandatory ISO requirements.

Its purpose is to help organizations identify weaknesses, improve application security practices, and demonstrate stronger governance.

How to prepare for an ISO 27034 assessment

Before using the checklist, organizations should establish a clear assessment scope and identify the information needed to evaluate application security.

An assessment without a defined scope can produce incomplete results or create unnecessary work.

Define the applications included in the assessment

Start by identifying which applications will be evaluated. The scope may include customer-facing applications, internal business systems, mobile applications, APIs, cloud-based platforms, and externally managed software.

Organizations should consider business criticality, sensitive information, regulatory obligations, and the potential consequences of an application security incident.

For an initial assessment, prioritizing high-risk applications can provide useful findings without requiring every application to be reviewed simultaneously.

Identify relevant stakeholders

Application security governance involves several functions, and the assessment should reflect their responsibilities.

Relevant stakeholders may include:

  • Information security and GRC teams responsible for policies, risk management, and oversight.
  • Application owners responsible for business requirements and risk decisions.
  • Development teams responsible for implementing application security measures.
  • IT operations teams responsible for deployment, maintenance, and operational controls.
  • Internal auditors responsible for evaluating control design and effectiveness.
  • Procurement or vendor management teams responsible for third-party application relationships.

Each stakeholder should provide evidence relevant to their responsibilities.

Establish assessment criteria

Determine how assessment results will be evaluated before reviewing individual controls.

For example, the organization may distinguish between documented policies, implemented activities, and verified control effectiveness.

This prevents a common assessment problem where the existence of a policy is treated as sufficient evidence that a security practice is working.

ISO 27034 checklist: 12 essential assessment areas

The following 12 assessment areas provide a structured way to evaluate application security governance and management practices.

They are practical assessment categories developed for this guide, not official ISO 27034 clause numbers.

1. Application security governance and accountability

Application security governance defines how decisions are made, responsibilities are assigned, and security expectations are enforced.

An assessment should determine whether application security has clear ownership and appropriate management oversight.

Assessment checklist:

  • Application security policies have been formally approved.
  • Roles and responsibilities are documented for relevant stakeholders.
  • Critical applications have designated business and technical owners.
  • Security risk acceptance decisions follow an approved process.
  • Application security issues can be escalated to appropriate management personnel.

Evidence to review: Approved policies, responsibility matrices, application ownership records, risk acceptance approvals, and governance meeting records.

Assessment guidance: Interview application owners to confirm that documented responsibilities match actual practices. A policy alone does not demonstrate that accountability is effective.

2. Organization Normative Framework (ONF)

The ONF provides a centralized foundation for managing application security information and expectations across the organization.

ISO/IEC 27034-2:2015 describes the ONF and provides guidance for its implementation.

The assessment should determine whether the organization maintains a consistent reference for application security governance.

Assessment checklist:

  • A documented ONF or equivalent centralized application security framework exists.
  • Relevant application security policies and practices are incorporated.
  • Applicable legal, regulatory, and contractual considerations are identified.
  • Application Security Control information is maintained consistently.
  • Responsibilities for maintaining and updating the framework are assigned.

Evidence to review: ONF documentation, application security standards, control libraries, framework ownership records, and change histories.

Assessment guidance: Select two development teams and compare how they obtain approved application security requirements. Significant differences may indicate that the framework is not being applied consistently.

3. Application inventory and classification

Organizations need reliable information about the applications they own, operate, or depend on.

An incomplete application inventory can prevent security teams from identifying critical systems and assigning appropriate safeguards.

Assessment checklist:

  • An inventory of relevant applications is maintained.
  • Each application has an identified owner.
  • Applications are classified according to business importance.
  • Sensitive information processed by applications is identified.
  • Important application dependencies are documented.

Evidence to review: Application inventory records, data classification information, architecture diagrams, and dependency documentation.

Assessment guidance: Compare the application inventory against deployment platforms, cloud subscriptions, and procurement records to identify potentially unrecorded applications.

4. Application security risk assessment

Risk assessments help organizations determine which applications require stronger security controls and more extensive verification.

The assessment should evaluate whether risk decisions reflect actual application characteristics rather than generic assumptions.

Assessment checklist:

  • Application security risks are assessed using a defined methodology.
  • Relevant threats, vulnerabilities, and business impacts are considered.
  • Risk assessments are approved by appropriate stakeholders.
  • Risk treatment decisions are documented.
  • Significant application changes trigger risk reassessment when appropriate.

Evidence to review: Risk assessment reports, threat models, risk registers, treatment plans, and approval records.

Assessment guidance: Review a recently modified critical application and determine whether its risk assessment reflects the current architecture and exposure.

5. Application Normative Framework (ANF)

The ANF translates relevant organizational security expectations into information and controls applicable to an individual application.

It provides an important connection between the organization’s governance framework and application-specific security decisions.

Assessment checklist:

  • Critical applications have documented application-specific security requirements.
  • Relevant organizational security expectations are reflected in application documentation.
  • Selected security controls correspond to identified application risks.
  • Application security decisions and exceptions are recorded.
  • Application-specific security information is maintained when requirements change.

Evidence to review: Application security requirements, ANF documentation, control selection records, exception approvals, and application security plans.

Assessment guidance: Trace one significant application risk through the selected controls and associated verification evidence. Missing connections can indicate weaknesses in application-level governance.

6. Secure application development and acquisition

Applications can introduce security weaknesses through insecure design decisions, development errors, or insufficient supplier oversight.

The assessment should evaluate whether security expectations are incorporated into application development and acquisition activities.

Assessment checklist:

  • Security requirements are considered during application planning.
  • Relevant secure development practices are documented.
  • Security reviews are performed at appropriate development stages.
  • Purchased applications are evaluated against relevant security expectations.
  • Outsourced development arrangements include appropriate security responsibilities.

Evidence to review: Development procedures, design review records, procurement assessments, supplier agreements, and security acceptance criteria.

Assessment guidance: Review a recently delivered application and identify when security requirements were established. Requirements introduced only near release may indicate an ineffective development process.

7. Application Security Controls (ASCs)

Application Security Controls provide a structured way to describe security activities and associated verification measures.

The assessment should determine whether controls are appropriate for the risks they address and whether their implementation can be demonstrated.

Assessment checklist:

  • Application security controls are selected based on relevant risks.
  • Control descriptions and responsibilities are documented.
  • Verification methods are defined for important controls.
  • Control implementation evidence is maintained.
  • Identified control weaknesses are assigned for remediation.

Evidence to review: ASC records, security control documentation, implementation records, verification results, and remediation tickets.

Assessment guidance: Select a sample of high-risk controls and request evidence demonstrating that each control was implemented and verified. Control descriptions without supporting evidence should not automatically receive a satisfactory rating.

8. Security testing and verification

Security testing provides information about application weaknesses, but effective assurance requires more than performing occasional scans.

Organizations should establish verification activities that reflect application risks and security objectives.

Assessment checklist:

  • Security testing expectations are defined for relevant applications.
  • Testing methods are appropriate for application architecture and risk.
  • Significant security findings are documented and classified.
  • Required remediation activities are verified after completion.
  • Security testing evidence is retained according to organizational requirements.

Evidence to review: Penetration testing reports, code review findings, vulnerability assessment results, retesting records, and security acceptance approvals.

Assessment guidance: Review whether critical findings were resolved before release or formally accepted through an authorized risk decision.

9. Application change and release management

Application changes can introduce new vulnerabilities, modify security controls, or invalidate earlier risk assessments.

The assessment should determine whether security implications are considered during significant changes.

Assessment checklist:

  • Application changes follow an approved change management process.
  • Security impacts are considered before significant releases.
  • Changes affecting important controls receive appropriate review.
  • Emergency changes are documented and reviewed afterward.
  • Release decisions account for unresolved security findings.

Evidence to review: Change requests, release approvals, deployment records, security review results, and emergency change documentation.

Assessment guidance: Select a production release and verify that its approval records reflect any material security risks identified during development or testing.

10. Third-party application security governance

Organizations often depend on external software vendors, cloud service providers, and development partners.

These relationships can create application security risks that are not directly controlled by internal development teams.

Assessment checklist:

  • Third-party applications are included in relevant security assessments.
  • Supplier security responsibilities are defined.
  • Appropriate security assurance evidence is requested from vendors.
  • Significant supplier security findings are tracked.
  • Changes in important supplier relationships trigger appropriate reviews.

Evidence to review: Supplier risk assessments, contracts, security questionnaires, assurance reports, and third-party remediation records.

Assessment guidance: Determine whether the organization understands which security responsibilities belong to the supplier and which remain with the application owner.

11. Security incident and vulnerability response

Application security governance should support timely decisions when vulnerabilities or security incidents are identified.

The assessment should examine whether relevant teams can identify, escalate, and address application security issues.

Assessment checklist:

  • Application security incidents follow defined reporting procedures.
  • Vulnerabilities are prioritized according to risk.
  • Remediation responsibilities and timelines are established.
  • Significant incidents inform future application security decisions.
  • Relevant application owners receive appropriate incident and vulnerability information.

Evidence to review: Incident records, vulnerability management procedures, remediation histories, escalation records, and post-incident reviews.

Assessment guidance: Examine a previously resolved security incident and determine whether lessons learned resulted in meaningful improvements to application security practices.

12. Application security monitoring and management reporting

Management needs reliable information to understand whether application security governance is effective.

Reporting should help stakeholders identify important weaknesses, evaluate progress, and make informed risk decisions.

Assessment checklist:

  • Application security performance indicators are defined.
  • Significant risks and unresolved findings are reported to appropriate stakeholders.
  • Application security exceptions are monitored.
  • Periodic reviews evaluate the effectiveness of security practices.
  • Improvement actions are assigned and tracked to completion.

Evidence to review: Security dashboards, management reports, exception registers, review records, and improvement plans.

Assessment guidance: Review the latest management report and determine whether it identifies actionable issues, responsible owners, and the status of important corrective actions.

ISO 27034 checklist summary table

The following table provides a consolidated view of the 12 assessment areas and their primary evaluation objectives.

Assessment areaMain assessment objectivePriority
Security governanceConfirm accountability and oversightHigh
Organization Normative FrameworkEvaluate centralized security governanceHigh
Application inventoryIdentify and classify relevant applicationsHigh
Application risk assessmentEvaluate risk identification and treatmentHigh
Application Normative FrameworkVerify application-specific security expectationsHigh
Secure development and acquisitionAssess security integration into delivery processesHigh
Application Security ControlsEvaluate control selection and verificationHigh
Security testingConfirm appropriate technical assurance activitiesHigh
Change managementEvaluate security oversight during application changesMedium
Third-party application securityAssess external application dependenciesHigh
Incident and vulnerability responseEvaluate response and remediation practicesHigh
Monitoring and reportingAssess management visibility and improvementMedium

These priority levels are illustrative. Organizations should adjust them according to application criticality, regulatory obligations, and their own risk tolerance.

How to score your ISO 27034 assessment

A consistent scoring method helps organizations compare findings across applications and identify improvement priorities.

Rather than relying on subjective judgments, assessors should use defined criteria supported by evidence.

Suggested assessment scoring model

ScoreAssessment statusMeaning
0Not establishedNo relevant process or reliable evidence exists
1Partially establishedSome activities exist, but implementation is inconsistent
2ImplementedThe process is documented and generally operating
3VerifiedImplementation is supported by appropriate verification evidence
4Managed and improvedThe process is monitored, evaluated, and improved using results

This is an illustrative maturity model developed for internal assessment purposes. It is not an official ISO 27034 scoring system.

Calculate your assessment score

Organizations can calculate a simple percentage using the following formula:

Assessment score (%) = (Total points achieved ÷ Total possible points) × 100

For example, if an organization evaluates 12 assessment areas using the five-point scale from 0 to 4, the maximum possible score is 48.

If the organization receives 30 points, its overall score would be 62.5%.

This result provides a general indication of implementation maturity, but it should not be interpreted as an official ISO compliance percentage.

A high overall score can also conceal serious weaknesses in individual critical applications. Organizations should therefore review significant findings separately rather than relying only on the aggregate score.

How to prioritize gaps found during an ISO 27034 assessment

After completing the checklist, the next step is to convert findings into a practical improvement plan.

Not every gap requires the same level of attention.

Evaluate findings based on business risk

Assessment findings should be prioritized according to their potential consequences.

For example, missing application ownership documentation may create accountability problems, while an unaddressed critical authentication weakness in a customer-facing application may present an immediate security exposure.

Organizations should consider the application’s business importance, exploitability, exposure, affected information, and existing safeguards.

Assign corrective action owners

Every significant finding should have a clearly identified owner responsible for coordinating remediation.

The corrective action record should explain the issue, required improvement, expected completion date, and verification approach.

This helps prevent findings from remaining unresolved after the assessment is complete.

Verify that corrective actions work

Closing a remediation ticket does not necessarily demonstrate that the underlying issue has been resolved.

Organizations should verify completed actions using appropriate evidence.

For example, a corrected access control weakness may require retesting, while a governance issue may require evidence that the revised approval process has been implemented.

Example: ISO 27034 assessment of a customer portal

Consider a fictional organization operating a customer portal that allows users to access personal information, submit requests, and manage account settings.

The organization performs an ISO 27034-aligned internal assessment to evaluate application security governance.

Initial assessment findings

The assessment identifies three important issues.

First, the customer portal has a designated technical owner but no clearly assigned business risk owner.

Second, application security testing is performed before major releases, but the organization does not consistently document how findings influence release decisions.

Third, application security requirements have not been updated following a significant integration with an external service provider.

These findings represent different types of governance weaknesses rather than a single technical vulnerability.

Corrective action plan

The organization establishes the following actions:

FindingCorrective actionResponsible function
Missing business risk ownerAssign and document application risk ownershipBusiness management
Incomplete release security evidenceUpdate release approval procedures to record relevant security decisionsDevelopment management
Outdated application security requirementsReview integration risks and update application-specific security documentationApplication security team

After implementing the improvements, the organization reviews the updated records and verifies that the revised processes are being followed.

This example illustrates how a checklist can support practical improvements without requiring a complete redesign of the organization’s security program.

What evidence should you keep for an ISO 27034 assessment?

Reliable evidence allows organizations to demonstrate that application security activities are being performed.

The quality of evidence is often more important than the volume of documents collected.

Governance evidence

Governance evidence demonstrates how security expectations are established and approved.

Examples include approved policies, framework documentation, responsibility assignments, and risk acceptance decisions.

Application-level evidence

Application-level evidence shows how security expectations are applied to individual applications.

Relevant records may include application security requirements, risk assessments, selected controls, architecture reviews, and security verification results.

Operational evidence

Operational evidence demonstrates how application security activities are maintained during normal business operations.

Examples include change approvals, vulnerability remediation records, incident reviews, and periodic management reports.

Evidence should be current, traceable to the relevant application or control, and accessible to authorized reviewers.

Organizations should also apply appropriate access restrictions and retention practices because some security assessment records contain sensitive information.

How often should organizations perform an ISO 27034 assessment?

The appropriate assessment frequency depends on application risk, business requirements, and the rate of change within the application environment.

A practical approach is to combine scheduled governance reviews with event-driven assessments.

Scheduled assessments

Organizations may perform periodic assessments to evaluate application security governance and identify changes in control effectiveness.

For example, an organization might conduct an annual program-level review while assessing higher-risk applications more frequently.

These intervals are examples, not mandatory ISO 27034 review periods.

Event-driven assessments

Additional assessments may be appropriate following significant application changes, major security incidents, new third-party integrations, or changes in legal and contractual requirements.

Event-driven reviews help organizations respond to changes that could affect previously approved security decisions.

Continuous oversight

Between formal assessments, organizations can monitor important risks, overdue remediation actions, and control verification results.

This provides management with more timely information and reduces dependence on occasional reviews.

Conclusion: Simplify application security governance with CyberArrow GRC

An ISO 27034 checklist helps organizations evaluate application security governance, identify control weaknesses, and improve accountability across their application portfolios.

However, completing an assessment is only the beginning. Organizations also need a reliable way to manage findings, maintain evidence, and monitor corrective actions.

At CyberArrow, we help organizations simplify these activities through our CyberArrow GRC platform. Our solution supports centralized risk assessments, policy and control management, compliance workflow automation, evidence management, and remediation tracking.

By bringing these governance activities together, we help security and compliance teams improve visibility and reduce manual administrative work.

Ready to strengthen application security governance? Book a free CyberArrow GRC demo and discover how we can help simplify your risk and compliance management processes.

FAQs

Can an ISO 27034 checklist be used for SaaS applications?

Yes. Organizations can use an ISO 27034 checklist to evaluate the governance of SaaS applications. However, the assessment should reflect the shared responsibilities between the customer and the SaaS provider. Organizations may need to rely on supplier assurance reports, contractual commitments, and configuration evidence where direct technical testing is not permitted.

Who should approve the results of an ISO 27034 assessment?

Assessment results should be reviewed and approved according to the organization’s governance arrangements. This may involve the application owner, information security leadership, or an authorized risk owner. Significant unresolved risks should be escalated to individuals with the authority to make risk treatment or acceptance decisions.

Can organizations reuse evidence from ISO 27001 audits?

Yes, when the evidence is relevant, current, and sufficiently detailed for the application security assessment. For example, an ISO 27001 audit may already include approved secure development policies or risk treatment records. However, additional application-specific evidence may be needed to demonstrate how those expectations are implemented for individual applications.

What should an organization do when an application cannot meet a selected security control?

The organization should document the limitation, assess the resulting risk, and consider alternative safeguards or other treatment options. Any decision to accept the remaining risk should follow an authorized approval process. The organization should also determine whether the limitation requires future remediation, architectural changes, or application replacement.

Is a spreadsheet enough to manage ISO 27034 assessments?

A spreadsheet may be sufficient for a small application portfolio with limited assessment activity. However, larger organizations may find it difficult to maintain ownership, evidence, remediation status, and reporting across multiple teams using separate spreadsheets. A centralized GRC platform can help coordinate these activities and improve visibility into outstanding actions.

Avatar photo
CyberArrow team