Regular Review of Access Controls Sample Clauses

The "Regular Review of Access Controls" clause requires that an organization periodically evaluates and updates the permissions and mechanisms governing access to its systems and data. In practice, this means conducting scheduled audits to ensure that only authorized individuals have the appropriate level of access, and promptly revoking or modifying access when roles or personnel change. This clause helps maintain security by minimizing the risk of unauthorized access and ensuring that access rights remain aligned with current organizational needs and personnel responsibilities.
Regular Review of Access Controls. Convercent maintains a process to review access controls on a minimum annual basis for all Convercent systems that contain Customer Data, including any system that, via any form of communication interface, can connect to the system on which Customer Data is stored. These access processes and the process to establish and delete individual accounts will be documented in, and will be in compliance with, Convercent’s security policies and standards referenced in Article 3.1 above. Convercent maintains the same processes of review and validation for any third party hosted systems it uses that contain Customer Data.
Regular Review of Access Controls. Market Logic will maintain a process to review access controls on a minimum annual basis for all Market Logic systems that contain Subscriber Data, including any system that, via any form of communication interface, can connect to the system on which Subscriber Data is stored. These access processes and the process to establish and delete individual accounts will be documented in, and will be in compliance with, Market Logic’s security policies and procedures.
Regular Review of Access Controls. You will maintain a process to review access controls on a minimum annual basis for all of your systems that contain eBay Content and Personal Information, including any system that, via any form of communication interface, can connect to the system on which eBay Content is stored. These access processes and the process to establish and delete individual accounts will be documented in, and will be in compliance with your security policies and standards referenced in Section 3.1 above. You will maintain the same processes of review and validation for any third party hosted systems you use that contain eBay Content.
Regular Review of Access Controls. Convercent maintains a process to review access controls on a minimum annual basis for all Convercent systems that contain Customer Data, including any system that, via any form of communication interface, can connect to the system on which Customer Data is stored. These access processes and the process to establish and delete individual accounts will be documented in, and will be in compliance with, Convercent's security policies and standards referenced in the Security Management: Scope and Contents Sub‐section, above. Convercent maintains the same processes of review and validation for any third party hosted systems it uses that contain Customer Data.

Related to Regular Review of Access Controls

  • Access Controls a. Authorized Access - DST shall have controls that are designed to maintain the logical separation such that access to systems hosting Fund Data and/or being used to provide services to Fund will uniquely identify each individual requiring access, grant access only to authorized personnel based on the principle of least privileges, and prevent unauthorized access to Fund Data. b. User Access - DST shall have a process to promptly disable access to Fund Data by any DST personnel who no longer requires such access. DST will also promptly remove access of Fund personnel upon receipt of notification from Fund.

  • Log Reviews All systems processing and/or storing PHI COUNTY discloses to 11 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 12 must have a routine procedure in place to review system logs for unauthorized access.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐▇▇▇▇▇▇-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • Performance Tests Contractor shall perform Performance Tests in accordance with Section 11.2 of the Agreement and Attachment S.