ISO 27001 Annex : A.14.2.3 Technical Review of Applications after Operating Platform Changes , A.14.2.4 Restrictions on Changes to Software Packages & A.14.2.5 Secure System Engineering Principles

In this article explain ISO 27001 Annex : A.14.2.3 Technical Review of Applications after Operating Platform Changes , A.14.2.4 Restrictions on Changes to Software Packages & A.14.2.5 Secure System Engineering Principles this controls.

A.14.2.3  Technical Review of Applications after Operating Platform Changes

Control- In changing operating platforms, critical applications of business should be revised and tested to ensure no adverse impacts on business or security.

Implementation Guidance – The following points should be covered in the process:

  • Review of application control and processes of integrity to ensure that changes to the operating platform have not compromised them;
  • Ensure that operating platform changes are communicated at the right time to enable proper tests and reviews prior to implementation;
  • Ensuring that the business continuity plans are properly amended.

Other Information – Operating environments are operating systems, databases, and applications for middleware. API modifications should also be tracked.

Related Product : ISO 27001 Lead Auditor Training And Certification ISMS

A.14.2.4  Restrictions on Changes to Software Packages

Control- Software package modifications should be discouraged, restricted to the modifications necessary, and all changes controlled strictly.

Implementation Guidance – The vendor-supplied software packages should be used without alteration to the extent necessary and feasible. The following points should be considered where a software package needs to be modified:

  • the possibility of conflict with built-in controls and processes of integrity;
  • Whether Vendor’s consent has been obtained;
  • the opportunity, in regular system updates, to receive the necessary vendor changes;
  • impacts when the organization becomes responsible as a result of changes for the future maintenance of software;
  • Additional software compatibility in use.

The original software should be kept if changes are necessary and the modifications applied to the specified copy. To ensure that the most up to date approved patches and application updates are installed for all permitted software, a software update management process should be implemented. All modifications should be carefully checked and reported, in order to reapply to potential software updates if necessary. If required, a separate evaluation body will check and verify the modifications.

A well-known ISO 27001 Lead Auditor and ISO 27001 Lead Implementer certificate that mainly covers information security clauses and their implementation, i.e., controls which should be implemented by the organization to preserve the CIA triad, Confidentiality, Integrity, and Availability to maintain their critical, sensitive information in a secure manner.  Infosavvy, an institute in Mumbai conducts training and certification for multiple domains in Information Security which includes IRCA CQI ISO 27001:2013 Lead Auditor (LA), ISO 27001 Lead Implementer (LI) (TÜV SÜD Certification). Infosavvy will help you to understand and recognize the full scope of your organization’s security checks to protect your organization’s activities and information equipment (assets) from attacks, and also to illustrate the controls for securing system engineering principles and also controls for changes in software packages. We have trainers with extensive expertise and experience to ensure the efficient handling of the security of information. Consequently, the applicant will gain the necessary skills for the ISMS audit by using commonly agreed audit concepts, procedures and techniques.

Also Read : ISO 27001 Annex : A.14.2 Security in Development and Support Processes

A.14.2.5  Secure System Engineering Principles

Control- In the implementation of any information system implementation project, standards for secure system engineered must be established, documented, maintained, and implemented.

Implementation Guidance – Secure IT Engineering procedures based on the principles of security engineering should be established, documented, and applied in in-house IT Engineering. The need for data security and accessibility should be balanced in all architecture layers (e.g., business, data, applications, and technology).   New technology for security threats needs to be evaluated and the design for documented attack patterns should be reviewed.

Such principles and the developed engineering processes should be reviewed periodically, to ensure that they contribute effectively to improved safety standards in the engineering phase. They should also be reviewed on a regular basis to ensure that they remain relevant as concerning the combat against any new potential threats and remain applicable to technical advancements and implemented solutions.

Where appropriate, the established principles of security engineering should be applied to outsourced information systems through the agreements and other binding agreements between the organization and its suppliers to whom the organization outsources.   The business must ensure that the rigor of the security engineering standards of suppliers is comparable to its own.

Other Information – Procedures for the creation of applications which have input and output interfaces should apply secure engineering techniques. Secure engineering techniques provide guidance on user authentication, secure control of the session, and validation of data, sanitation and removal of debugging codes.

Questions related to this topic

  1. How do I secure an application software?
  2. ISO 27001 Annex : A.14.2.3 Technical Review of Applications which of the control used?
  3. What is an application security engineer?
  4. What are the applications of cyber security?
  5. What are some security concerns when using different application software?
  6. What is ISO 27001 Annex : A.14.2.3 Technical Review of Applications after Operating Platform Changes?

ISO 27001 Requirements


Clause 4.4 Information security management system
Clause 4.3 Determining the scope of the information security management system
Clause 5.1 Leadership and commitment
Clause 5.2 Policy
Clause 5.3 Organizational roles, responsibilities and authorities
Clause 6.1 Actions to address risks and opportunities
Clause 6.1.2 Information security risk assessment process
Clause 6.1.3 Information security risk treatment
Clause 6.2 Information security objectives & planning
Clause 7.1 Resources
Clause 7.2 Competence
Clause 7.3 Awareness
Clause 7.4 Communication
Clause 7.5 Documented information Implementation Guideline
Clause 8.1 Operational planning & control
Clause 8.2 Information security risk assessment
Clause 8.3 Information security risk treatment
Clause 9.1 Performance evaluation Monitoring, measurement, analysis & evaluation
Clause 9.2 Internal audit
Clause 9.3 Management review
Clause 10.1 Non conformity and corrective action
Clause 10.2 Continual Improvement 

ISO 27001 Annex A Controls


Annex A.5 Information Security Policies
Annex A.6 Organization of Information Security
Annex A.6.2 Mobile Devices and Teleworking
Annex A.7 Human Resource Security
Annex A.7.2 During Employment
Annex A.7.3 Termination and Change of Employment
Annex A.8 Asset Management
Annex A.8.1.3 Acceptable Use of Assets & A.8.1.4 Return of Assets
Annex A.8.2 Information Classification
Annex A.8.2.2 Labeling of Information & A.8.2.3 Handling of Assets
Annex A.8.3 Media Handling
Annex A.9 Access Control
Annex A.9.1.2 Access to Networks and Network Services
Annex A.9.2 User Access Management
Annex A.9.2.3 Management of Privileged Access Rights  
Annex A.9.2.4 Management of Secret Authentication Information of Users
Annex A.9.2.5 Review of User Access Rights 
Annex A.9.2.6 Removal or Adjustment of Access Rights
Annex A.9.3 User Responsibilities
Annex A.9.4 System and Application Access Control
Annex A.9.4.4 Use of Privileged Utility Programs 
Annex A.9.4.5 Access Control to Program Source Code
Annex A.10 Cryptography
Annex A.11 Physical and Environmental Security
Annex A.11.2 Equipment
Annex A.11.1.3 Securing Offices, Rooms and Facilities
Annex A.11.1.4 Protecting Against External and Environmental Threats
Annex A.11.1.5 Working in Secure Areas
Annex A.11.1.6 Delivery and Loading Areas
Annex A.11.2.4 Equipment Maintenance
Annex A.11.2.5 Removal of Assets
Annex A.11.2.6 Security of Kit and Assets Off-Premises
Annex A.11.2.7 Secure Disposal or Re-use of Equipment
Annex A.11.2.8 Unattended User Equipment
Annex A.11.2.9 Clear Desk and Clear Screen Policy
Annex A.12 Operations Security
Annex A.12.2 Protection from Malware
Annex A.12.3 Backup
Annex A.12.4 Logging and Monitoring
Annex A.12.5 Control of Operational Software
Annex A.12.6 Technical Vulnerability Management
Annex A.12.7 Information Systems Audit Considerations
Annex A.13 Communications Security
Annex A.13.2 Information Transfer
Annex A.13.2.3 Electronic Messaging
Annex A.13.2.4 Confidentiality or Non-Disclosure Agreements
Annex 14 System Acquisition, Development and Maintenance
Annex A.14.1.2 Securing Application Services on Public Networks
Annex A.14.1.3 Protecting Application Services Transactions
Annex A.14.2 Security in Development and Support Processes
Annex A.14.2.3 Technical Review of Applications after Operating Platform Changes
Annex A.14.2.4 Restrictions on Changes to Software Packages
Annex A.14.2.5 Secure System Engineering Principles
Annex A.14.2.6 Secure Development Environment
Annex A.14.2.7 Outsourced Development
Annex A.14.2.8 System Security Testing
Annex A.14.2.9 System Acceptance Testing
Annex A.14.3 Test data
Annex A.15 Supplier Relationships
Annex A.15.1.2 Addressing Security Within Supplier Agreements
Annex A.15.1.3 Information and Communication Technology Supply Chain
Annex A.15.2 Supplier Service Delivery Management
Annex A.16 Information Security Incident Management
Annex A.16.1.2 Reporting Information Security Events
Annex A.16.1.3 Reporting Information Security Weaknesses
Annex A.16.1.4 Assessment of and Decision on Information Security Events
Annex A.16.1.5 Response to Information Security Incidents
Annex A.16.1.6 Learning from Information Security Incidents
Annex A.16.1.7 Collection of Evidence
Annex A.17 Information Security Aspects of Business Continuity Management
Annex A.17.1.3 Verify, Review and Evaluate Information Security Continuity
Annex A.18 Compliance
Annex A.18.1.3 Protection of Records
Annex A.18.1.4 Privacy and Protection of Personally Identifiable Information
Annex A.18.1.5 Regulation of Cryptographic Controls
Annex 18.2 Information Security Reviews

About ISO 27002



This Blog Article is posted by

Infosavvy, 5B 306 Riverside Greens, Panvel, Raigad 410206 Maharashtra, India

Contact us – www.infocerts.com

Leave a Comment

Your email address will not be published. Required fields are marked *

Open Whatsapp chat
Whatsapp Us
Chat with us for faster replies.