This page has been archived.
Information identified as archived on the Web is for reference, research or recordkeeping purposes. It has not been altered or updated after the date of archiving. Web pages that are archived on the Web are not subject to the Government of Canada Web Standards. As per the Communications Policy of the Government of Canada, you can request alternate formats on the "Contact Us" page.
|
Security |
Indicator(s) |
Use of the common infrastructure Adequate steps by departments and agencies to ensure that transactions are secure Citizens/clients perceive that on-line services are secure |
Measurement Level and Technique |
Measurement at the "whole of government" level using citizen/client feedback, and at the service level using self-assessments, client feedback, and tracking of how they engage the federal government |
Primary tool(s)/data source(s) |
1) Omnibus surveys – includes, e.g., EKOS' Information Highway studies 2) Secure Channel roadmap, outlining plans for the provision and use of Secure Channel services 3) Departmental reporting on GOL plans and progress – the reporting includes two types of data related to security: data on what type of IM/IT infrastructure is required by which date; and information on threat risk assessment, certification and accreditation, and business continuity planning 4) Discussions among departmental security coordinators and departments and agencies with a lead role in this area |
Summary of results achieved in 2003 |
Mostly positive – Canadians have more confidence in governments than either the banks or the private sector in terms of offering safe on-line services. However, they have significantly more comfort in applying on-line for a program or service than for making an e-payment. The current take-up of on-line federal services also provides evidence of Canadians' increasing confidence – the proportion of clients who completed transactions on-line increased from 21% in 2002 to 24% in 2003. In general, departments and agencies are meeting the security expectations of their clients. A reliable "whole of government" incident handling process is in place to respond to external threats. The Secure Channel now offers authentication and e-payment services, both of which Canadians and businesses are using in increasing numbers. Secure Channel is developing and implementing services for which there is strong departmental demand, enabling the federal government to conduct secure on-line transactions with clients. Departments and agencies are at various stages in implementing the Government Security Policy, which requires threat and risk assessments and business continuity plans for federal services. |
Raw data
|
Perceptions of on-line service delivery
– 62% agree (20% disagree) that governments would not offer the choice of doing things as filing taxes through the Internet unless it was safe to do so, up from 59% in 2002 – In contrast, 59% agree (24% disagree) that banks would not offer the choice of banking on-line unless it was safe to do so, and 38% agree (39% disagree) that companies would not offer the choice of doing things such as buying products through the Internet unless it was safe to do so
– Internet users have a higher level of comfort than Canadians in general – 60% of Internet users have a moderate (32%) to high (28%) level of comfort with providing their credit card number on-line in order to make a payment to the federal government Security coordination
– Secure Channel Information Protection Centre (IPC) – PWGSC IPC – PSEP (formerly OCIPEP) Coordination Centre – Cyber Incident Coordination System triage unit – Alerts and advisories from PSEP and other government and non-government organisations
The common, secure infrastructure
– SCNet, which is advanced IP/VPNe network inter-connecting 130 departments and agencies, certified to "Protected A" and scaleable to "Protected B" (see the end of this section for definitions) – Security and authentication services, including ePass, which control access to on-line applications, protect privacy, and secure IT infrastructure from hackers – Payment services
Government Security Policy
– There is some evidence suggesting that there is a lack of understanding of what is expected and, thus, that an awareness program and/or direct support may be required; training is either being set up, or is available for federal employees – Note that the Secure Channel has completed its TRA, BCP, and C&A
|
Plans for improvement
|
– Enhancing the Secure Channel IPC – Building interoperability and coordination capabilities among the Secure Channel IPC, the PWGSC IPC, and PSEP (formerly OCIPEP) – Developing common analysis services and solutions with an infrastructure overlay that will assist departments and agencies in establishing or enhancing their own detect and respond capabilities – Developing an intrusion detection standard – if passed, Bill C14 will give departments and agencies the legal framework for intrusion detection, acknowledging the responsibility of the federal government both to securely manage their IM/IT assets and to respect individual privacy rights (note that while some guidance is currently available, the standard will not be finalised until Bill C14 is passed)
– Detection, Analysis, and Response Infrastructure Model, led by PSEP, which will provide a comprehensive, secure infrastructure to support the detection, analysis, and response to cyber incidents within the federal government – Threat and Vulnerability Analysis System, led by CSE, which will support the identification of and response to current and emerging safety and security cyber threats, and improve the monitoring and mitigation of risks to federal services – Cyber Incident Coordination System, led by PSEP, which supports the coordination of incident management across the federal government
|
Terminology
"Protected A" – if its compromise could reasonably be expected to cause a low level of injury to private or non-national interests, for example, disclosure of an exact salary figure
"Protected B" – if its compromise could reasonably be expected to cause a medium level of injury to private or non-national interests; such information concerns an individual or an organisation, and is considered to be particularly sensitive
Security risk management
1. Threat and Risk Assessment (TRA), including a Statement of Sensitivity (SOS) identifying and categorising assets in terms of their confidentiality, integrity, availability, and value based on the Operational Standard for the Identification and Categorisation of Assets
2. Business Continuity Plan (BCP), including a Business Impact Assessment (BIA) documenting the relative priority/criticality of services and systems, and the maximum/minimum allowable down-time
3. Certification and Accreditation (C&A) of systems and services, confirming that the security requirements have been fulfilled, and signifying that management has authorised the system or service for operation
4. Vulnerability Assessments, which identify inherent vulnerabilities and recommend remedial action
5. Active Defence, one based on the Protect-Detect-Respond-Recover cycle