< Previous standard ^ Up a level ^ Next standard >
ISO/IEC 27034:2011+ — Information technology — Security techniques — Application security (7 parts, most published except for part 4 in DRAFT)
ISO/IEC 27034 offers guidance on information security to those specifying, designing and programming or procuring, implementing and using application systems, in other words business and IT managers, developers and auditors, and ultimately the end-users of ICT. The aim is to ensure that computer applications deliver the desired or necessary level of security in support of the organisation’s Information Security Management System, adequately addressing many ICT security risks.
Scope and purpose
This multi-part standard provides guidance on specifying, designing/selecting and implementing information security controls through a set of processes integrated throughout an organisation’s Systems Development Life Cycle/s. It is process-oriented.
It covers software applications developed internally, by external acquisition, outsourcing/offshoring or through hybrid approaches.
It addresses all aspects from determining information security requirements, to protecting information accessed by an application as well as preventing unauthorized use and/or actions of an application.
The standard is SDLC-method-agnostic: it does not mandate one or more specific development methods, approaches or stages but is written in a general manner to be applicable to them all. In this way, it complements other systems development standards and methods without conflicting with them.
One of the key driving principles is that it is worth investing more heavily in specifying, designing, developing and testing software security controls or functions if they are reusable across multiple applications, systems and situations, albeit at the risk of propagating vulnerabilities more widely than might otherwise be the case. In a nutshell, “Do it properly, do it once, and reuse it”. The approach may seem a little idealistic, but some far-sighted organisations are already successfully using it: it is more than just an academic interest.
ISO/IEC 27034-1:2011 — Information technology — Security techniques — Application security — Part 1: Overview and concepts
- Abstract: “Provides guidance to assist organisations in integrating security into the processes used for managing their applications. This International Standard presents an overview of application security. It introduces definitions, concepts, principles and processes involved in application security.” [Source: SC 27 Standing Document 11 (2021)]
- As with other multipartite ISO27k standards, the first part sets the scene for the remainder, providing a general introduction and outlining the remaining parts;
- ~80 pages long with quite a bit of detail;
- States explicitly that this is not a software application development standard, an application project management standard, nor a software development cycle standard. Its purpose is to provide general guidance on application security that will be supported, in turn, by more detailed methods and standards in those other areas;
- Explicitly takes a process approach to specifying, designing, developing, testing, implementing and maintaining security functions and controls in application systems. For instance it defines application security not as the state of security of an application system (the results of the process) but as “a process an organisation can perform for applying controls and measurements to its applications in order the manage the risk of using them”;
- Uses the concept of defining a Targeted Level of Trust (similar to a security plan) for an application, designing and building the application to meet it, and then validating the application against it;
- Draws on concepts such as auditing and certification of application systems similar in style to the Common Criteria and similar schemes primarily used for government and military systems. The text tends to emphasize deliberate threats arising from external adversaries implying the importance of confidentiality controls, arguably downplaying insider and accidental threats and the need for integrity and availability controls, but the process described ostensibly takes account of the full spectrum of security risks and controls;
- Status: part 1 was published in 2011. Three minor corrections plus a revised figure were published in 2014 as a technical corrigendum.
ISO/IEC 27034-2:2015 — Information technology — Security techniques — Application security — Part 2: organisation normative framework
- Abstract: “Provides a detailed description of the organisation Normative Framework and provides guidance to organisations for its implementation.” [Source: SC 27 Standing Document 11 (2021)]
- Explains the structure, relationships and interdependencies between processes in the organisation Normative Framework - a suite of application security-related policies, procedures, roles and tools;
- The standard is intended to guide organisations in designing, implementing, operating and auditing their ONF;
- The approach is formal and bureaucratic e.g. a committee is needed to oversee the ONF, hence it is most likely to suit organisations who have or want a highly structured way of securing applications they develop;
- Status: part 2 was published in 2015.
ISO/IEC 27034-3:2018 — Information technology — Security techniques — Application security — Part 3: Application security management process
- Abstract: “Provides a detailed description and implementation guidance for the Application Security Management Process.” [Source: SC 27 Standing Document 11 (2021)]
- Describes the Application Security Management Process i.e. “the overall process for managing security on each specific application used by an organisation”;
- This may be the most broadly applicable and useful part of this standard;
- Status: part 3 was published in 2018.
ISO/IEC 27034-4 — Information technology — Security techniques — Application security — Part 4: Application security validation [DRAFT]
- Abstract: “Provides a detailed description of an Application security validation process used to audit and verify Application Security.” [Source: SC 27 Standing Document 11 (2021)]
- Part 4 will describe an application security validation and certification process to assess and compare the ‘level of trust’ of an application system against its previously stated [information security] requirements;
- ~40 pages long in some detail;
- Status: the part 4 project was cancelled ... and then resurrected, zombie style. The resurrected standard reached Draft International Standard stage before being cancelled once more at the end of 2020 following objections from CASCO (ISO’s conformity assessment committee). It started over a third time in 2021 as a Preliminary Work Item, the project team this time liaising with CASCO.
- A new scope has been proposed: “This document gives guidance to help an organisation specify how the implementation of its application security frameworks, processes and controls are able to be verified and validated through the provision of objective evidence. Note: it is important to note that verification and validation refers to the normal systems engineering processes,and not conformity assessment (as used in ISO/IEC/IEEE 15288)”.
- A new title too: “ISO/IEC 27034-4, Information technology - Application security - Part 4: Verification and validation”
- This zombie project is doomed. It has been cancelled once again, this time shot with a silver bullet, cremated and scattered to the four winds.
ISO/IEC 27034-5:2017 — Information technology — Security techniques — Application security — Part 5: Protocols and application security control data structure
- Abstract: “Outlines and explains the minimal set of essential attributes of Application Security Controls (ASCs) and details the activities and roles of the Application Security Life Cycle Reference Model (ASLCRM).” [Source: SC 27 Standing Document 11 (2021)]
- Defines the Application Security Control data structure, providing requirements, descriptions, graphical representations and XML schema for the data model. The XML schema, based on ISO/TS 15000: Electronic business eXtensible Markup Language ebXML, is designated as the standard interchange format for ASCs;
- Part 5 facilitates the implementation of the ISO/IEC 27034 application security framework and the communication and exchange of ASCs by defining a formal structure for ASCs and certain other components of the framework;
- Part 5 enables the establishment of libraries of reusable application security functions that may be shared both within and between organisations;
- It explains a minimal set of essential attributes of ASCs and the Application Security Life Cycle Reference Model;
- Status: part 5 was published in 2017.
ISO/IEC TS 27034-5-1:2018 — Information technology — Security techniques — Application security — Part 5-1: Protocols and application security control data structure, XML schemas
- Abstract: “Defines XML Schemas that implement the minimal set of information requirements and essential attributes of Application Security Controls (ASCs) and the activities and roles of the Application Security Life Cycle Reference Model (ASLCRM) from Part 5.” [Source: SC 27 Standing Document 11 (2021)]
- The XML schemas implement the minimal set of information requirements and essential attributes of ASCs and the activities and roles of the Application Security Life Cycle Reference Model from part 5.
- Status: part 5 dash 1 was published in 2018 as a Technical Specification.
ISO/IEC 27034-6:2016 — Information technology — Security techniques — Application security — Part 6: Case studies
- Abstract: “Provides usage examples of Application Security Controls (ASCs) for specific applications.” [Source: SC 27 Standing Document 11 (2021)]
- Provides examples of how ASCs might be developed and documented, defining how information security is to be handled in the course of software development
- Status: part 6 was published in 2016.
ISO/IEC 27034-7:2018 — Information technology — Security techniques — Application security — Part 7: Assurance prediction framework
- Abstract: “Provides the criteria and guidance for the extension of security attributes in one application to a different but related application. Additionally, the prediction will state the conditions under which the prediction is valid and invalid.” [Source: SC 27 Standing Document 11 (2021)]
- Concerns a framework to deliver the assurance necessary to place trust in a computer program’s security arrangements, for example when one program (such as an application) relies on another (e.g. a database management system, utility, operating system or companion program) to perform critical security functions (such as user authentication, logical access control or cryptography), or when an organisation updates or patches a trusted program;
- Encourages users to consider, determine/specify and document the trust or criticality (called “security predictability” in the formalities of the standard) as the basis for rational decisions by them and by software suppliers concerning the way software is designed, developed, tested, delivered, managed, operated and maintained;
- Specifies minimum requirements when the required activities specified by an Application Security Control are replaced with a Prediction Application Security Rationale. The ASC mapped to a PASR defines the Expected Level of Trust for a subsequent application.
- The use of PASRs is applicable to project teams which have a defined Application Normative Framework and an original application with an Actual Level of Trust.
- Status: part 7 was published in 2018.
- Personal comment: part 7 is extremely formal and stilted in its use of language (e.g. “An application security claim is a claim that the application team implemented certain security controls and those controls mitigate specific security risks to an acceptable level. A security prediction is the transfer of confidence in the original claim to a claim that the same security controls are also present in a subsequent version of the application and mitigate, to the same acceptable level, the same specific security risks.” - got that?).
All parts of the standard should conform with JTC 1/SC 17’s standards on software engineering, and the terminology should align with ISO 31000 (fingers crossed).
The ability to generate and share libraries of reusable, parameterized, well-engineered security functions is a remarkable achievement, with the potential to facilitate the global adoption of good security practices in software development.
< Previous standard ^ Up a level ^ Next standard >