Standard security requirements Sample Clauses

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. 25 Decision of the Executive Director No 61 of 12 April 2021 on the Security Governance Framework. • Security of information. Sensitive non-classified and classified information shall be protected adequately, in accordance with the applicable legal framework26. XXXX’s security responsible shall be involved in supporting the proper classification of relevant information. • Security of IT and communication equipment. EASO IT equipment is adequately prepared to protect the information level it has been foreseen to process. • Personal security behavior shall be included in the pre-deployment training, led by operational teams and pe...
Sample 1See All (4)
AutoNDA by SimpleDocs
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 current by competent authority/person, 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.
Sample 1

Related to Standard security requirements

  • Security Requirements 11.1 The Supplier shall comply, and shall procure the compliance of the Suppliers Personnel, with the Security Policy and the Security Plan and the Supplier shall ensure that the Security Plan produced by the Supplier fully complies with the Security Policy.

  • Data Security Requirements A. Data Transport. When transporting Confidential Information electronically, including via email, the data will be protected by:

  • Information Security Requirements In cases where the State is not permitted to manage/modify the automation equipment (server/computer/other) that controls testing or monitoring devices, the Contractor agrees to update and provide patches for the automation equipment and any installed operating systems or applications on a quarterly basis (at minimum). The Contractor will submit a report to the State of updates installed within 30 days of the installation as well as a Plan of Actions and Milestones (POA&M) to remediate any vulnerabilities ranging from Critical to Low. The contractor will provide an upgrade path or compensatory security controls for any operating systems and applications listed as beyond “end-of-life” or EOL, within 90 days of the EOL and complete the EOL system’s upgrade within 90 days of the approved plan.

  • Facility Requirements 1. Maintain wheelchair accessibility to program activities according to governing law, including the Americans With Disabilities Act (ADA), as applicable.

  • Payment Security Requirements A. Unless Company has maintained an agreement similar to this Agreement with Authority during the 18 months prior to the effective date of this Agreement without the occurrence of any act or omission that would have been a default under this Agreement, Company will provide Authority on or before the commencement date of this Agreement with an acceptable bond, irrevocable letter of credit or other similar security acceptable to Authority in an amount equal to the estimate of three months’ Rents, fees and charges, payable by Company under this Agreement, to guarantee the faithful performance by Company of its obligations under this Agreement and the payment of all Rents, fees, tax assessments, and charges due hereunder (hereinafter referred to as “Payment Security”). Company will be obligated to maintain such Payment Security in effect until the expiration of 18 consecutive months during which Company commits no default under this Agreement. Such Payment Security will be in a form and with a company acceptable to Authority and licensed to do business in the State of Florida. In the event that any such Payment Security is for a period less than the full period required under this Agreement or if such Payment Security is canceled, Company will provide a renewal or replacement Payment Security for the remaining required period at least 60 days prior to the date of such expiration or cancellation. Such Payment Security will require notice by the surety to Authority at least 60 days prior to any cancellation.

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

  • Additional security requirements The following provisions apply in respect of any Additional Security provided:

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

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

  • E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!