Standard security requirements Sample Clauses

The "Standard security requirements" clause sets out the baseline obligations for maintaining the security of information, systems, or premises involved in a contract. Typically, it requires parties to implement reasonable technical and organizational measures to protect against unauthorized access, data breaches, or other security threats. For example, this may include requirements for password protection, encryption, regular security audits, or compliance with recognized security standards. The core function of this clause is to ensure that all parties uphold a minimum level of security, thereby reducing the risk of data loss or compromise and clarifying expectations regarding the protection of sensitive information.
Standard security requirements. The standard security and safety requirements are rather pertaining to elements to be present in the implementation of the Plan, not to minimum security standards: • Both the host Member State on one side and EASO on the other shall appoint a single point of contact responsible for security matters under the Plan both at central and local level (hereafter ‘security responsible’). • The host Member State shall ensure that the working conditions for the performance of the activities under the Plan are compliant with the national occupational health and safety norms and regulations. • A pre-deployment briefing programme, drafted in close cooperation with the respective national authorities, focusing both on general security rules and awareness, as well as on specific security aspects for each deployment will be provided. With regards to the 21 Article 93 of Management Board Decision No 54 of 14 August 2019 on the EASO Financial Regulation (as amended by Management Board Decision No 74 of 28 July 2021). The MB Decision nr 54 of 14 August 2019 remains in force despite EASO being replaced by the EUAA. Any references in the EASO Financial Regulation to ‘EASO’ or the ‘EASO Regulation’, should therefore be construed as references to the ‘EUAA’ or equivalent provisions in the ‘EUAA Regulation’, respectively. 22 Decision of the Executive Director No 61 of 12 April 2021 on the Security Governance Framework. decentralised nature of deployments, the use of e-learning and other distance-based training techniques should be considered. • Emergency (evacuation) plan. Certain operational activities, such as operations in field locations, require that staff shall have clear guidance and training on how to evacuate quickly in case of emergencies. In a more general context, there could be a need to evacuate from the operational area as well. Emergency plans shall be drafted and maintained up-to-date by the competent authority/person(s), whereas they shall be made available to the concerned parties and exercised regularly. A security responsible shall maintain updated information on the availability of evacuation plans and routes. • Communication tools. As considered relevant by the EASO Security sector, EASO operational staff shall have access to independent radio communication equipment. If possible, the equipment shall be interoperable with the local law enforcement in charge of the security of the operation. • Security of information. Sensitive non-classified and classified ...
Standard security requirements. The standard security and safety requirements are rather pertaining to elements to be present in the implementation of the Plan, not to minimum security standards: • Both the host Member State on one side and EASO on the other shall appoint a single point of contact responsible for security matters under the Plan both at central and local level (hereafter ‘security responsible’). • The host Member State shall ensure that the working conditions for the performance of the activities under the Plan are compliant with the national occupational health and safety norms and regulations. • A pre-deployment briefing programme, drafted in close cooperation with the respective national authorities, focusing both on general security rules and awareness, as well as on specific security aspects for each deployment will be provided. With regards to the decentralised nature of deployments, the use of e-learning and other distance-based training techniques should be considered. • Emergency (evacuation) plan. Certain operational activities, such as operations in field locations, require that staff shall have clear guidance and training on how to evacuate quickly in case of emergencies. In a more general context, there could be a need to evacuate from the operational area as well. Emergency plans shall be drafted and maintained up-to-date by the competent authority/person(s), whereas they shall be made available to the concerned parties and exercised regularly. A security responsible shall maintain updated information on the availability of evacuation plans and routes. • Communication tools. As considered relevant by the EASO Security sector, EASO operational staff shall have access to independent radio communication equipment. If possible, the equipment shall be interoperable with the local law enforcement in charge of the security of the operation. • Security of information. Sensitive non-classified and classified information shall be protected adequately, in accordance with the applicable legal framework23. ▇▇▇▇’s security responsible shall be involved in supporting the proper classification of relevant information. 22 Decision of the Executive Director No 61 of 12 April 2021 on the Security Governance Framework.

Related to Standard 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.

  • 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.

  • City Requirements Design, construction, materials, sizing, other specifications, permitting, inspections, testing, documentation and furnishing of as-built drawings, and acceptance of completed infrastructure shall be in accordance with City Requirements. Design and construction shall be by professionals licensed in the state of North Carolina to do the relevant work. City approval of the design of the Improvements shall be required prior to construction, as set forth in City Requirements. If Developer is connecting to the County sewer system, the City may require Developer to furnish the contract providing for such connection.

  • Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.