Directive on Security Management

Aims to achieve efficient, effective and accountable management of security within departments and agencies.
Date modified: 2019-07-01

Supporting tools

Mandatory procedures:

More information

Topic:

Print-friendly XML
The Directive on Security Management and its Mandatory Procedures took effect on July 1, 2019. It replaced the Directive on Departmental Security Management, as well as the Operational Security Standard - Business Continuity Planning (BCP) Program, the Operational Security Standard on Physical Security, the Operational Security Standard - Readiness Levels for Federal Government Facilities, and the Operational Security Standard: Management of Information Technology Security (MITS).

Appendix F: Mandatory Procedures for Security in Contracts and Other Arrangements Control

F.1 Effective date

  • F.1.1These procedures take effect on July 1, 2019.

F.2 Procedures

  • F.2.1These procedures provide details on the requirements to support the deputy head accountability.

    The procedures and subsections are as follows:

    Procedure Subsection
    Security in the procurement or arrangement process F.2.2
    Security requirements for contracts and information-sharing arrangements F.2.3
    Verifying compliance F.2.4
    Monitoring and corrective actions F.2.5
  • F.2.2Security in the procurement or arrangement process: Define, document and maintain departmental security practices for procurement and the establishment of information- or asset-sharing arrangements:
    • F.2.2.1Define department-wide security requirements that should apply to all contracts or arrangements;
    • F.2.2.2Establish a process for identifying security requirements for a specific contract or arrangement;
    • F.2.2.3Establish a process for verifying and monitoring continued compliance with security requirements, including any permitted exceptions and risk mitigation measures, as applicable; and
    • F.2.2.4Integrate security considerations into departmental procurement processes and into information management, asset management and program management processes, while considering information- and asset-sharing arrangements.
  • F.2.3Security requirements for contracts and information-sharing arrangements: Identify and document security requirements for all contracts and arrangements:
    • F.2.3.1Determine security requirements based on the sensitivity of information, assets or sites to which individuals will require access; the location and the type of work to be performed; the need for the supplier, partner or department to safeguard, process or produce sensitive information or assets at its facilities or in its information systems; and other relevant factors:
      • F.2.3.1.1Security screen individuals who require access to sensitive information, assets or sites in the performance of their work; individuals who need to be relied on to produce and deliver the goods and services being procured; and individuals who, because of their position, could gain access to sensitive information, assets or sites or could adversely affect the delivery of goods and services, including supplier security points of contact and, for certain contracts, suppliers’ key senior officials;
      • F.2.3.1.2Verify and obtain assurance of the appropriate implementation of;
        1. Physical security controls in facilities that are used to store or produce sensitive information or assets or that need to be relied on to produce or deliver the goods or services being procured;
        2. Security controls to protect information systems that are used to electronically process or transmit sensitive information or that are relied on to produce or deliver the goods or services being procured;
        3. Administrative and operational security controls (including designation of security points of contact, governance, planning, management of subcontracts or arrangements with third parties, security awareness and training, and security event monitoring, reporting and response, as applicable);
        4. Any other specific security requirements to meet statutory, regulatory or other obligations (for example, requirements for the management of COMSEC material; international or defence contracts that are subject to negotiated treaties, international agreements and multinational arrangements; and requirements where duties or access to information, assets or facilities are related to or directly support security and intelligence functions); and
        5. Risk-based approach for verifying and monitoring supplier, partner and departmental compliance with security requirements, as applicable.
    • F.2.3.2Identify security requirements in the documentation associated with a contract or arrangement:
      • F.2.3.2.1For contracts and other arrangements with suppliers, document security requirements in the Security Requirements Check List or an equivalent document and in other documentation associated with the contract or arrangement;
      • F.2.3.2.2For other types of arrangements, document security requirements in the arrangement;
      • F.2.3.2.3For contracts or arrangements involving a subcontractor or another third party, identify in the contract or arrangement the need for the supplier or partner to extend applicable security requirements to any other entity involved in fulfilling the contract or arrangement; and
      • F.2.3.2.4For contracts or arrangements that do not involve any security requirements, include an attestation to that effect in the documentation of the contract or the arrangement.
  • F.2.4Verifying compliance: Confirm and document compliance with security requirements before awarding a contract or entering into an arrangement and before granting access to sensitive information, assets or sites, as applicable:
    • F.2.4.1Verify compliance with, and obtain assurance of the implementation of, the security requirements using the risk-based approach defined for the contract or arrangement. To avoid duplication, where possible and in accordance with privacy requirements and other legal or policy obligations:
      • F.2.4.1.1Provide the security records of Government of Canada suppliers to internal enterprise service organizations and other departments; and
      • F.2.4.1.2Consult the security records of Government of Canada suppliers when verifying supplier compliance;
    • F.2.4.2Implement and document risk mitigation measures when security requirements to limit access to sensitive information, assets or sites cannot be fully met before awarding a contract or entering into an arrangement, subject to approval by an individual who has the required authority; and
    • F.2.4.3Establish documented arrangements that define respective security responsibilities for contracts or arrangements managed for or by another organization.
  • F.2.5Monitoring and corrective actions: Monitor supplier, partner and departmental compliance with security requirements throughout the contracting or arrangement process, using the risk-based approach defined for the contract or arrangement, and take corrective actions to address issues of non-compliance, security incidents or other security events.
Date modified: