Operational Security Requirements Sample Clauses

The Operational Security Requirements clause sets out the standards and procedures that must be followed to protect sensitive information and maintain secure operations within an organization or between contracting parties. It typically outlines specific security measures such as access controls, data encryption, incident response protocols, and regular security assessments that must be implemented. By establishing clear expectations for safeguarding operational environments, this clause helps prevent unauthorized access, data breaches, and other security incidents, thereby reducing risk and ensuring compliance with relevant regulations.
Operational Security Requirements. 2.1 Objective System state means the operational state of the transmission system in relation to the operational security limits which can be normal state, alert state, emergency state, blackout state and restoration state. The increased system coordination achieved by monitoring the system state contributes to a coherent and coordinated behaviour of the interconnected transmission systems, both in each TSO’s control area and between control areas.
Operational Security Requirements. 2.1 Objective The increased system coordination achieved by monitoring the system state contributes to a coherent and coordinated behaviour of the interconnected transmission systems, both in each TSO’s control area and between control areas.

Related to Operational Security Requirements

  • Security Requirements 7.1 The Authority will review the Contractor’s Security Plan when submitted by the Contractor in accordance with the Schedule (Security Requirements and Plan) and at least annually thereafter.

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • Data Security Requirements Without limiting Contractor’s obligation of confidentiality as further described in this Contract, Contractor must establish, maintain, and enforce a data privacy program and an information and cyber security program, including safety, physical, and technical security and resiliency policies and procedures, that comply with the requirements set forth in this Contract and, to the extent such programs are consistent with and not less protective than the requirements set forth in this Contract and are at least equal to applicable best industry practices and standards (NIST 800-53).

  • Facility Requirements 1. Maintain wheelchair accessibility to program activities according to governing law, including the Americans With Disabilities Act (ADA), as applicable. 2. Provide service site(s) that will promote attainment of Contractor’s program objectives. Arrange the physical environment to support those activities. 3. Decrease program costs when possible by procuring items at no cost from County surplus stores and by accepting delivery of such items by County.

  • Safety Requirements Prior to setting sail the Operator of the Sector 43 Vessel shall detail and identify any vessel safety operating procedures and 44 other important information to the assigned ASM. The Sector Member 45 acknowledges that an ASM must complete a pre‐trip vessel safety checklist 46 as provided by NMFS prior to leaving port. An ASM cannot be deployed on 1 a vessel that has failed to review the safety issues, and such vessel is 2 prohibited from leaving port without the ASM on board (unless a waiver is 3 granted). For the safety of the vessels captain, crew and the ASM; the ASM 4 will not be allowed on deck any time that gear is being deployed. 5 6 The Sector and its Members note that each ASM must be provided with all 7 the equipment specified by the NEFOP. It is the responsibility of the 8 individual ASM and its employer to ensure that all equipment is in good