the related technology.
3.4.6.
Assertions are formal statements by management or system owners. They are claims on the completeness, accuracy and validity of events,
presentations, disclosure, transactions and related assurance, risk and governance aspects of certification and accreditation.
3.4.7.
It is the responsibility of the management (or system owner) to prepare and validate assertions relating to the governance, assurance and security of
information systems, in accordance with national policy and related standards.
3.4.8.
When such assertions are made it means management (or system owners) have presented and disclosed information appropriately giving a true, fair
and balanced view of the activities. In preparing assertions, implicit and explicit claims are made on the validity and completeness of the assertions.
3.4.9.
Assertions are typically characterised as follows:
Transactions and events
Occurrence — the activities recorded have actually taken place.
Completeness — all aspects are properly recorded.
Accuracy — the assets and activities are accurately allocated and recorded.
Cutoff — the activities have been recorded in the correct time period.
Classifications — are accurate and appropriate.
Position on project completion
Existence — assets, liabilities and equity balances exist.
Rights and Obligations — the entity legally controls rights to its assets and its liabilities and accurately records obligations.
Completeness — all aspects are properly recorded.
Valuation and Allocation — costs and assets appropriately valued and allocated.
Presentation and disclosure
Occurrence — the events and implementations have actually occurred.
Rights and Obligations — contracts, licences, support and supply agreements
Completeness — all disclosures have been included in the statements.
Classification — statements are clear and appropriately presented.
Accuracy and Valuation — information is disclosed at the appropriate amounts.
Rationale & Controls
3.4.10.
Requirement for system owners
3.4.10.R.01.
Rationale
The system owner is responsible for the overall operation of the system, including any directly related support or outsourced service such as
cloud. They may delegate the day-to-day management and operation of the system to a system manager or managers.
3.4.10.R.02.
Rationale
All systems should have a system owner in order to ensure IT governance processes are followed and that business requirements are met.
3.4.10.R.03.
Rationale
It is strongly recommended that a system owner be a member of the Senior Executive Team or in an equivalent management position,
however this does not imply that the system manager(s) should also be at such a level.
3.4.10.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:442]
Each system MUST have a system owner who is responsible for the operation and maintenance of the system.
3.4.10.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:443]
System owners SHOULD be a member of the Senior Executive Team or an equivalent management position, for large or critical agency
systems.
3.4.11.
Accreditation responsibilities
3.4.11.R.01.
Rationale
The system owner is responsible for the operation of their system and as such they need to ensure that systems are accredited to meet the
agency’s operational requirements. If modifications are undertaken to a system the system owner will need to ensure that the changes are
undertaken in an appropriate manner, documented adequately and that any necessary reaccreditation activities are completed.
3.4.11.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:446]
System owners MUST obtain and maintain accreditation of their system(s).
3.4.12.
Documentation responsibilities
3.4.12.R.01.
Rationale
The system owner is responsible for ensuring the development, maintenance and implementation of Systems Information Security
documentation, in particular the Security Risk Management Plans (SRMPs), System Security Plans (SSPs) and Standard Operating Procedures
(SOPs).
3.4.12.R.02.
Rationale
The system owner should involve security personnel in the process of developing, redeveloping or updating Systems Information Security
documentation, to ensure that a holistic approach to information security is mapped to the system owner’s understanding of security risks for
27
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents