System Classification(s): All Classifications; Compliance: SHOULD
14.5.6.C.01. Control
[CID:1661]
Agencies SHOULD review all active content on their Web servers for known information security issues.
14.5.7.
Segregation of Web application components
14.5.7.R.01.
Rationale
Web applications are typically very exposed services that provide complex interactions with system users. This greatly increases the security
risk of being compromised. By segregating components, the impact of potential application flaws or attacks is limited.
14.5.7.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1664]
Agencies SHOULD minimise connectivity and access between each Web application component.
14.5.8.
Web applications
14.5.8.R.01.
Rationale
The Open Web Application Security Project guide provides a comprehensive resource to consult when developing Web applications.
14.5.8.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1667]
Agencies SHOULD follow the documentation provided in the Open Web Application Security Project guide to building secure Web applications
and Web services.
15. Email security
15.1. Email Applications
Objective
15.1.1. Email messages have appropriate protective markings to facilitate the application of handling instructions.
Context
Scope
15.1.2. This section covers information on email policy and usage as it applies to content and protective markings. Information on email infrastructure is
located in Section 15.2 - Email Infrastructure.
Automatically generated emails
15.1.3. The requirements for emails within this section equally apply to automatically and manually generated emails.
Exceptions for receiving unmarked email messages
15.1.4. Where an agency receives unmarked non-government emails as part of its business practice the application of protective markings can be automated.
References
15.1.5. Further references can be found at:
Reference
SP 800-45
Title
Publisher
NIST publication SP 800-45 v2,
Source
NIST
http://csrc.nist.gov/publications/ni
Guidelines on Electronic Mail
stpubs/800-45-version2/SP800-
Security
45v2.pdf
Detecting socially engineered
ASD
http://www.asd.gov.au/publicatio
emails August 2012
ns/csocprotect/Socially_Engineered_
Email.pdf
PSR references
15.1.6. Relevant PSR requirements can be found at:
Reference
Title
Source
PSR Mandatory
GOV2, GOV3, GOV4, INFOSEC1, INFOSEC2,
http://www.protectivesecurity.govt.nz
Requirements
INFOSEC3, INFOSEC4, PHYSEC1 and PHYSEC2
https://www.protectivesecurity.govt.nz/governance/mandatory-requirements-2/
https://www.protectivesecurity.govt.nz/information-security/mandatoryrequirements-2/
https://www.protectivesecurity.govt.nz/physical-security/physical-securitymandatory-requirements-2/
PSR content
Management protocol for information security
https://www.protectivesecurity.govt.nz/information-security/management-protocol/
protocols
Management protocol for physical security
https://www.protectivesecurity.govt.nz/physical-security/management-protocol/
196
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents