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

ISO 27001 Annex : A.14.2 Security in Development and Support Processes It’s objective is ensuring the creation and implementation of information security in the information system development process.

A.14.2.1 Secure Development Policy

Control- Regulations for software and system development should be laid down and applied to organizational developments.

Implementation Guidance – Secure development includes a safe infrastructure, architecture, software, and system to be developed. The following considerations should be taken into account in a stable technology policy:

Environmental development security;
security guidelines for the life cycle of software development:

security in the methodology for software development;
Secure guidelines on code for each language of programming used;

Design-phase protection requirements;
Security control points within the milestones of the project;
secure repositories;
Version control security;
Necessary security knowledge of application;
The ability of the developers to avoid, identify and fix vulnerabilities.

secure programming technology can be used for both software development and code replication situations where development requirements are not established or in line with existing best practices. The secure and, if applicable, mandatory coding criteria for use should be taken into account. Developers should be trained and their use should be verified for testing and code review.

The organization will be confident if development is outsourced that it complies with these principles of safe development.

Other information – Applications like office software, scripts, browsers, and databases can also be developed.

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 Protecting Application Software and their maintenance. 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

A.14.2.2 System Change Control Procedures

Control- Changes to processes can be managed through the implementation of structured change control procedures within the software lifecycle.

Implementation Guidance – Formal protocols for monitoring of transition from early design to future maintenance activities should be recorded and implemented to ensure the quality of the systems, software, and products.

A systematic process of planning, specification, testing, quality assurance, and control implementation will be introduced for the introduction of new systems and significant improvements to existing systems.

The process should include risk assessment, impact assessment, and security control requirements.

The process will also ensure that there is no modification to already defined security and control protocols, that only certain parts of a system required for their work are accessed by support programmers and that any improvements are officially accepted.

Wherever possible, control procedures for application and operational change should be integrated. The protocols for approval of changes will include:

Keep a record of agreed levels of authorization;
Ensure that authorized users submit changes;
evaluate processes and procedures of integrity to ensure that changes do not compromise them;
Identifying any modification software, information, database entities, and hardware;
Identification and testing of sensitive security code in order to reduce the risk of identified security vulnerabilities;
Formal approval for detailed proposals prior to commencement of work;
Ensure registered users accept changes before they are implemented;
Ensuring that system documentation has been updated and that old documents are archived or removed upon completion of each amendment;
Maintenance of version control for all updates of software;
Keep an audit trail for all requests for changes;
ensure that operational documentation and user procedures are modified to remain appropriate if necessary;
ensure that improvements are introduced on schedule so that the business processes involved are not interrupted.

Also Read : ISO 27001 Annex : A.14.1.3 Protecting Application Services Transactions

Other Information – Software changes may impact and vice versa the operating environment.

Good practice includes the testing of new software in an environment that is both manufactured and developed. This offers a way to control new software and to further safeguard operational information that is used for testing. Patches, service packages and other updates should include

In the case of automated updates, a risk to system integrity and availability is weighed against the advantages of quick update deployment. Automated updates on critical systems should not be used because certain updates will result in a failure of critical applications.

Questions related to this topic

What are the three types of security?
How do you implement security control?
What is application level security?
Which testing is not applicable for application security?
What is ISO 27001 Annex : A.14.2 Security in Development and Support Processes?
How do you implement ISO 27001 Annex : A.14.2 Security in Development and Support Processes control?

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.