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.

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

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

ISO 27001 Requirements

Clause 4.2 Understanding the needs and expectations of interested parties

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

About ISO 27002

This Blog Article is posted by

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

Contact us – www.infocerts.com

https://goo.gl/maps/mHkyURHmeFXyGiVw5

Upcoming Training :- ISO27001 LA T. D.:-Coming soon.. ISO42001 LI T. D.:-16th,17th Nov 2024.