14.3.13.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD NOT [CID:1622] Users SHOULD NOT store web site authentication credentials (userID and password) on workstations, remote access devices (such as laptops) or BYO devices. 14.3.13.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD NOT [CID:1623] Users SHOULD NOT use the same password for multiple websites. 14.4. Software Application Development Objective 14.4.1. Secure programming methods and testing are used for application development in order to minimise the number of coding errors and introduction of security vulnerabilities. Context Scope 14.4.2. This section covers information relating to the development, upgrade and maintenance of application software used on agency systems. References 14.4.3. Additional information relating to software development is contained in: Reference ISO/IEC 27001:2013 Title Publisher Source A.12.5, Security in Development ISO https://www.iso.org/standard/54534. and Support Processes OWASP Secure Coding Practices html OWASP - Quick Reference Guide Secure Code Review https://www.owasp.org/index.php/O WASP_Secure_Coding_Practices__Quick_Reference_Guide MITRE Corporation https://www.mitre.org/publications/s ystems-engineeringguide/enterpriseengineering/systems-engineeringfor-mission-assurance/secure-codereview Build Security In DHS – US-CERT https://www.us-cert.gov/bsi Application Security - US Defense Information Security Application Security & Development A To Z Agency (DISA) security/appsecurity/Pages/index.aspx Writing Secure Code - Michael Microsoft Press ISBN Book 978-0-7356-1722-3 Howard and David LeBlanc http://iase.disa.mil/stigs/app- ISBN eBook 978-0-7356-9146-9 Rationale & Controls 14.4.4. Software development environments 14.4.4.R.01. Rationale Recognised good practice segregates development, testing and production environments to limit the spread of malicious code and minimise the likelihood of faulty code being put into production. Limiting access to development and testing environments will reduce the information that can be gained by an attacker. 14.4.4.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1635] Agencies SHOULD ensure that software development environments are configured such that: there are at least three separate environments covering: development; testing; and production. information flow between the environments is strictly limited according to a defined and documented change policy, with access granted only to system users with a clear business requirement; new development and modifications only take place in the development environment; and write access to the authoritative source for the software (source libraries & production environment) is disabled. 14.4.5. Secure programming 14.4.5.R.01. Rationale Designing software to use the lowest privilege level needed to achieve its task will limit the privileges an attacker could gain in the event they subvert the software security. 14.4.5.R.02. 194 Rationale Version_3.5__January-2022

Select target paragraph3

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