Security Policies and Exception Process. Security policies must be documented, reviewed, and approved, with management oversight, on a periodic basis, following industry best practices.
Security Policies and Exception Process Sample Clauses
Related to Security Policies and Exception Process
SECURITY POLICIES AND NOTIFICATIONS State Security Policies and Procedures The Contractor and its personnel shall review and be familiar with all State security policies, procedures and directives currently existing or implemented during the term of the Contract, including ITS Policy NYS-P03-002 Information Security Policy (or successor policy). Security Incidents Contractor shall address any Security Incidents in the manner prescribed in ITS Policy NYS-P03-002 Information Security Policy (or successor policy), including the New York State Cyber Incident Reporting Procedures incorporated therein or in such successor policy.
Violence Policies and Procedures The Employer agrees to have in place explicit policies and procedures to deal with violence. The policy will address the prevention of violence, the management of violent situations, provision of legal counsel and support to employees who have faced violence. The policies and procedures shall be part of the employee's health and safety policy and written copies shall be provided to each employee. Prior to implementing any changes to these policies, the employer agrees to consult with the Association.
Security Policies IBM maintains privacy and security policies that are communicated to IBM employees. IBM requires privacy and security training to personnel who support IBM data centers. We have an information security team. IBM security policies and standards are reviewed and re-evaluated annually. IBM security incidents are handled in accordance with a comprehensive incident response procedure.
Security Policy for Contractors 1. The Department for Work and Pensions treats its information as a valuable asset and considers that it is essential that information must be protected, together with the systems, equipment and processes which support its use. These information assets may include data, text, drawings, diagrams, images or sounds in electronic, magnetic, optical or tangible media, together with any Personal Data for which the Department for Work and Pensions is the Data Controller.
Policies and Procedures i) The policies and procedures of the designated employer apply to the employee while working at both sites.
Security Policy As part of PCI DSS, the Card Organizations require that you have a security policy that covers the security of credit card information.
Anti-‐Abuse Policy i. Registry Operator’s Anti-‐Abuse Policy will be required under the Registry Registrar Agreement and posted on the Registry Operator’s web site.
Fair Use Policy Betty Blocks has a fair use policy in relation to accessing and using the Services. For the purpose of this fair use policy, Client may not vary from the average in a disproportionate manner, having regard to the amount of CPU power, data storage and data traffic used by Client. In such event, Betty Blocks is entitled to temporarily limit or restrict access to the Services and/or require that Client to purchase additional Services, such as extra storage capacity.
Overpayment Policies and Procedures Within 90 days after the Effective Date, Xxxxx shall develop and implement written policies and procedures regarding the identification, quantification and repayment of Overpayments received from any Federal health care program.
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
