Guidelines for Software Development Application development Types of application development These guidelines are applicable to both traditional application development and mobile application development. Development, testing and production environments Segregating development, testing and production environments, and associated data, can limit the spread of malicious code and minimises the likelihood of faulty code being introduced into a production environment. Furthermore, protecting the authoritative source for software is critical to preventing malicious code being surreptitiously introduced into software. Security Control: ISM-0400; Revision: 5; Updated: Aug-20; Applicability: All; Essential Eight: N/A Development, testing and production environments are segregated. Security Control: ISM-1419; Revision: 1; Updated: Sep-18; Applicability: All; Essential Eight: N/A Development and modification of software only takes place in development environments. Security Control: ISM-1420; Revision: 4; Updated: Mar-22; Applicability: All; Essential Eight: N/A Data from production environments is not used in a development or testing environment unless the environment is secured to the same level as the production environment. Security Control: ISM-1422; Revision: 3; Updated: Sep-18; Applicability: All; Essential Eight: N/A Unauthorised access to the authoritative source for software is prevented. Secure software design and development Secure-by-design principles and secure programming practices, supported by threat modelling, are an important part of application development as they can assist with the identification and mitigation of at risk software components and risky programming practices. Security Control: ISM-0401; Revision: 5; Updated: Mar-22; Applicability: All; Essential Eight: N/A Secure-by-design principles and secure programming practices are used as part of application development. Security Control: ISM-1238; Revision: 4; Updated: Mar-22; Applicability: All; Essential Eight: N/A Threat modelling is used in support of application development. Software bill of materials A software bill of materials is a list of open source and commercial software components used in application development. This can assist in providing greater cyber supply chain transparency for consumers by allowing for easier identification and management of security risks associated with individual software components used by applications. Security Control: ISM-1730; Revision: 0; Updated: Dec-21; Applicability: All; Essential Eight: N/A A software bill of materials is produced and made available to consumers of software. Application testing and maintenance Application testing and maintenance activities can lessen the likelihood of security vulnerabilities in applications being introduced into a production environment. Robust application testing can be performed using both static testing, such as code analysis, as well as dynamic testing, such as input validation and fuzzing. Vulnerability scanning tools can also 100

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents