|
|
| Line 23: |
Line 23: |
| | | | |
| | |} | | |} |
| − | </div>{{TOCright}} | + | </div>{{Delete|reason=Expired Content}} |
| − | | |
| − | == Overview ==
| |
| − | The IT threat landscape for the Government of Canada (GC) is ever-changing – new threats emerge, destructive exploits proliferate, and our adversaries are always on the offensive. In order to maintain an effective public service in the face of rising risk, the GC proposes an IT Integrated Risk Management (IRM) program. Treasury Board of Canada Secretariat (TBS), defines IRM in Framework for the Management of Risk as “a continuous, proactive and systematic process to understand, manage and communicate risk from an organization-wide perspective”. The GC Digital Operations Strategic Plan for Information Management and Information Technology (IM/IT) 2017 to 2021 lays out the GC’s vision to have a centralized capability to conduct IRM management activities in order to gain a holistic picture of cyber-related business risks in the GC. A consolidated view of cyber risks is vital to enhance awareness of cyber threats and risks at the enterprise level. In addition, it supports strategic decision-making which contributes to the achievement of an organization's overall objectives.
| |
| − | | |
| − | The TBS proposes an IRM program that is aligned with the Canadian Centre for Cyber Security (CCCS)’s IT Security Risk Management Framework (ITSG-33), and is comprised of dedicated resources, purpose-specific technology, and integrated automated processes. IRM builds on and rebrands the umbrella term of Governance, Risk and Compliance (GRC).
| |
| − | | |
| − | <br>
| |
| − | | |
| − | == Alignment with GC Enterprise Security Architecture ==
| |
| − | The GC Enterprise Security Architecture Description Document (ESADD) Annex D for Security Operations highlights the concept of risk identification and risk management, and the management of security-related risk to the GC Enterprise. IRM provides a platform to implement automation for the risk identification and management process described in this ESADD.
| |
| − |
| |
| − | Departments currently manage IT security risks independently using their own set of disparate tools and methodologies. Every department must assess information system risk following the ITSG-33 methodology; however, each department has a different risk appetite, applies the methodology slightly differently and tracks it in various forms, including Word documents, Excel spreadsheets, Risk Registrars and other formats. The resulting departmental risk data exists in isolation and is not shared or viewable in an enterprise GC context. Results from recent audits and Management Accountability Framework (MAF) assessments have provided evidence of these inconsistencies and reinforced the need for the GC to work toward more standardized and consolidated cyber risk management.
| |
| − | | |
| − | <br>
| |
| − | | |
| − | == GC IRM Vision ==
| |
| − | The GC IRM vision is to gain a holistic enterprise view of cyber risks by consolidating data feeds from multiple GC resources. An iterative and modular implementation approach is planned in order to develop competencies and data sources while expanding the organization’s view of cyber risk.
| |
| − | | |
| − | === GC IRM Approach ===
| |
| − | To overcome the current challenges, the GC vision will focus on people, processes, and technology within an IRM program. At an operational level, the IRM program will require multiple, specialized resources to perform system administration, risk analysis support, process and enterprise data source onboarding, data warehouse management, and continuous risk monitoring. The program will work to automate business processes by developing use cases towards a federated model. It will also identify gaps and develop tools to assist departments in streamlining and standardizing their processes and reporting. The technical solution will help automate workflows and notifications in order to reduce dependence on manual processes and to drive consistency and trusted results into the enterprise systems IRM program. In its ideal end state, the IRM technical solution will recognize the interconnected nature of risk across the GC enterprise.
| |
| − | | |
| − | [[File:GC IRM Approach.jpg|thumb|521x521px|GC IRM Approach|center]]
| |
| − | <br>
| |
| − | == IRM Concepts ==
| |
| − | | |
| − | Gartner defines IRM as “a set of practices and processes supported by a risk-aware culture and enabling technologies, that improves decision making and performance through an integrated view of how well an organization manages its unique set of risks”. IRM is typically viewed in the context of a framework or suite of tools which enable a comprehensive approach to all governance and compliance functions within an organization, allowing it to create a standardized structure and take a risk-based approach to objectively prioritize activities across all functions and levels.
| |
| − | There are many areas of risk that may be included in the IRM IT Security program. The traditional risk domains addressed by IRM platforms are illustrated in Notional IRM Suite diagram below.
| |
| − | | |
| − | [[File:Notional IRM Suite.jpg|thumb|600x600px|Notional IRM Suite|center]]
| |
| − | | |
| − | The TBS IRM concept paper and entity relationship diagram focuses on IT Security IRM. Other areas of risk will be added at a later date. Key areas of IT security that contribute to the holistic view for the IT Security risks are captured in the High Level Entity Model Diagram below.
| |
| − | | |
| − | [[File:High Level IT Security Entity Model Diagram.jpg|thumb|750x650px|High Level IT Security Entity Model Diagram|center]]
| |
| − | <br>
| |
| − | | |
| − | For more information about the IRM initiative, please refer to the [[Media:GC_IT_IRM_(GRC)_Concept.pdf|GC IT IRM (GRC) Concept Paper]], [[Media:ERD - GC Integrated Risk Management v0.9.pdf|Entity Model - GC Integrated Risk Management Diagram]] and the [[Media:ERD-Lite - GC Integrated Risk Management v0.9.pdf|Entity Model Lite - GC Integrated Risk Management Diagram]].
| |
| − | <br>
| |
| − | | |
| − | | |
| − | == References ==
| |
| − | * [[Media:GC_IT_IRM_(GRC)_Concept.pdf|GC IT IRM (GRC) Concept Paper]]
| |
| − | * [[Media:ERD - GC Integrated Risk Management v0.9.pdf|Entity Model - GC Integrated Risk Management Diagram]]
| |
| − | * [[Media:ERD-Lite - GC Integrated Risk Management v0.9.pdf|Entity Model Lite - GC Integrated Risk Management Diagram]]
| |
| − | * [https://www.canada.ca/en/treasury-board-secretariat/corporate/risk-management/guide-integrated-risk-management.html GC, Guide to Integrated Risk Management]
| |
| − | * [https://www.canada.ca/en/government/system/digital-government/digital-operations-strategic-plan-2018-2022.html GC, Digital Operations Strategic Plan 2018-2022]
| |
| − | * [https://www.cyber.gc.ca/en/guidance/it-security-risk-management-lifecycle-approach-itsg-33 Canadian Centre for Cyber Security, IT Security Risk Management: A Lifecycle Approach (ITSG-33), 2012]
| |
| − | * [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=19422 GC, Framework for the Management of Risk]
| |
| − | * [http://www.gcpedia.gc.ca/wiki/ESA_Architecture_Definition_Document_(ESADD) GC, Enterprise Security Architecture Description Document (ESADD) - Annex D Security Operations, 2017. ]
| |
| − | * [https://gcconnex.gc.ca/groups/profile/47045926/, GRC/IRM IT Security Working Group]
| |
