Implement Strong Access Control Measures Sample Clauses

Implement Strong Access Control Measures. 1.1 Do not provide your credit reporting agency Subscriber Codes or passwords to anyone. No one from the credit reporting agency will ever contact you and request your Subscriber Code number or password. 1.2 Proprietary or third party system access software must have credit reporting agency Subscriber Codes and password(s) hidden or embedded. Account numbers and passwords should be known only by supervisory personnel. 1.3 You must request your Subscriber Code password be changed immediately when: • any system access software is replaced by another system access software or is no longer used; • the hardware on which the software resides is upgraded, changed or disposed of 1.4 Protect credit reporting agency Subscriber Code(s) and password(s) so that only key personnel know this sensitive information. Unauthorized personnel should not have knowledge of your Subscriber Code(s) and password(s). 1.5 Create a separate, unique user ID for each user to enable individual authentication and accountability for access to the credit reporting agency’s infrastructure. Each user of the system access software must also have a unique logon password. 1.6 Ensure that user IDs are not shared and that no Peer-to-Peer file sharing is enabled on those users’ profiles. 1.7 Keep user passwords Confidential. 1.8 Develop strong passwords that are: • Not easily guessable (i.e. your name or company name, repeating numbers and letters or consecutive numbers and letters) • Contain a minimum of seven (7) alpha/numeric characters for standard user accounts 1.9 Implement password protected screensavers with a maximum fifteen (15) minute timeout to protect unattended workstations. 1.10 Active logins to credit information systems must be configured with a 30 minute inactive session, timeout. 1.11 Restrict the number of key personnel who have access to credit information. 1.12 Ensure that personnel who are authorized access to credit information have a business need to access such information and understand these requirements to access such information are only for the permissible purposes listed in the Permissible Purpose Information section of your membership application. 1.13 Ensure that you and your employees do not access your own credit reports or those reports of any family member(s) or friend(s) unless it is in connection with a credit transaction or for another permissible purpose. 1.14 Implement a process to terminate access rights immediately for users who access credit reporting a...
AutoNDA by SimpleDocs
Implement Strong Access Control Measures. 1.1 All credentials such as User names/identifiers/account numbers (user IDs) and user passwords must be kept confidential and must not be disclosed to an unauthorized party. No one from ACRAnet will ever contact you and request your credentials. 1.2 If using third party or proprietary system to access ACRAnet’s systems, ensure that the access must be preceded by authenticating users to the application and/or system (e.g. application based authentication, Active Directory, etc.) utilized for accessing ACRAnet data/systems. 1.3 If the third party or third party software or proprietary system or software, used to access ACRAnet data/systems, is replaced or no longer in use, the passwords should be changed immediately. 1.4 Create a unique user ID for each user to enable individual authentication and accountability for access to ACRAnet’s infrastructure. Each user of the system access software must also have a unique logon password. 1.5 User IDs and passwords shall only be assigned to authorized individuals based on least privilege necessary to perform job responsibilities. 1.6 User IDs and passwords must not be shared, posted, or otherwise divulged in any manner. 1.7 Develop strong passwords that are:  Not easily guessable (i.e. your name or company name, repeating numbers and letters or consecutive numbers and letters)  Contain a minimum of eight (8) alphabetic and numeric characters for standard user accounts  For interactive sessions (i.e. non system-to-system) ensure that passwords/passwords are changed periodically (every 90 days is recommended) 1.8 Passwords (e.g. user/account password) must be changed immediately when:  Any system access software is replaced by another system access software or is no longer used  The hardware on which the software resides is upgraded, changed or disposed  Any suspicion of password being disclosed to an unauthorized party (see section 4.3 for reporting requirements) 1.9 Ensure that passwords are not transmitted, displayed or stored in clear text; protect all end user (e.g. internal and external) passwords using, for example, encryption or a cryptographic hashing algorithm also known as “one-way” encryption. When using encryption, ensure that strong encryption algorithm are utilized (e.g. AES 256 or above). 1.10 Implement password protected screensavers with a maximum fifteen (15) minute timeout to protect unattended workstations. Systems should be manually locked before being left unattended. 1.11 Active logins to...
Implement Strong Access Control Measures. Protect access code(s) and password(s) so that only key personnel know them. • Ensure that user IDs are not shared and that no peer-to-peer file sharing is enabled on those users’ profiles. • Implement password protected screensavers with a maximum fifteen (15) minute timeout to protect unattended workstations. • Implement physical security controls to prevent unauthorized entry to MUIS’s facility and access to systems containing Trust Data. • Cause personnel and others who receive Trust Data to strictly abide by these obligations. • Restrict access to Trust Data only to those individuals who have a need to know or otherwise access the Trust Data to enable MUIS to perform its obligations for the Trusts, or as otherwise permitted by the Trusts. No terminated employees are permitted access to any MUIS records containing Trust Data.
Implement Strong Access Control Measures. 1.1 Do not provide your passwords to anyone. No one from the credit reporting agency will ever contact you and request your password.
Implement Strong Access Control Measures. 1.1 All credentials such as User names/identifiers/account numbers (user IDs) and user passwords must be kept confidential and must not be disclosed to an unauthorized party. 1.2 If using third party or proprietary system to access RPS’s systems, ensure that the access must be preceded by authenticating users to the application and/or system (e.g. application based authentication, Active Directory, etc.) utilized for accessing RPS data/systems. 1.3 If the third party or third party software or proprietary system or software, used to access RPS’s data/systems, is replaced or no longer in use, the passwords should be changed immediately. 1.4 Create a unique user ID for each user to enable individual authentication and accountability for access to RPS’s infrastructure. Each user of the system access software must also have a unique logon password. 1.5 User IDs and passwords shall only be assigned to authorized individuals based on least privilege necessary to perform job responsibilities. 1.6 User IDs and passwords must not be shared, posted, or otherwise divulged in any manner. 1.7 Develop strong passwords that are: • Not easily guessable (i.e. your name or company name, repeating numbers and letters or consecutive numbers and letters) • Contain a minimum of eight (8) alphabetic and numeric characters for standard user accounts • For interactive sessions (i.e. non system-to-system) ensure that passwords/passwords are changed periodically (every 90 days is recommended) 1.8 Passwords (e.g. user/account password) must be changed immediately when: • Any system access software is replaced by another system access software or is no longer used • The hardware on which the software resides is upgraded, changed or disposed • Any suspicion of password being disclosed to an unauthorized party (see section 4.3 for reporting requirements) 1.9 Ensure that passwords are not transmitted, displayed or stored in clear text; protect all end user (e.g. internal and external) passwords using, for example, encryption or a cryptographic hashing algorithm also known as “one-way” encryption. When using encryption, ensure that strong encryption algorithms are utilized (e.g. AES 256 or above). 1.10 Implement password protected screensavers with a maximum fifteen (15) minute timeout to protect unattended workstations. Systems should be manually locked before being left unattended. 1.11 Active logins to credit information systems must be configured with a 30-minute inactive session time...
Implement Strong Access Control Measures. 1. Restrict access to cardholder data to ensure critical data can only be accessed by authorized personnel, systems and processes based on the least amount of data and privileges needed to perform a job 2. Assign a unique identification ("ID") to each person with computer access to maintain accountability and traced actions taken on critical data and systems to known and authorized users · 3. Restrict physical access to cardholder data

Related to Implement Strong Access Control Measures

  • Access Control Supplier will maintain an appropriate access control policy that is designed to restrict access to Accenture Data and Supplier assets to authorized Personnel. Supplier will require that all accounts have complex passwords that contain letters, numbers, and special characters, be changed at least every 90 days, and have a minimum length of 8 characters.

  • Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage.

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization.

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

  • Physical Access Control Unauthorized persons are prevented from gaining physical access to premises, buildings or rooms where data processing systems that process and/or use Personal Data are located.

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

  • Access Controls The system providing access to PHI COUNTY discloses to 20 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 21 must use role based access controls for all user authentications, enforcing the principle of least privilege.

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall xxxx the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor

  • Safety Measures Awarded vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Awarded vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage.

  • Interim Measures Notwithstanding any requirements for alternative dispute resolution procedures as set forth in Articles 18(B), any party to the Dispute may apply to a court for interim measures (i) prior to the constitution of the arbitral tribunal (and thereafter as necessary to enforce the arbitral tribunal’s rulings); or (ii) in the absence of the jurisdiction of the arbitral tribunal to rule on interim measures in a given jurisdiction. The Parties agree that seeking and obtaining such interim measures shall not waive the right to arbitration. The arbitrators (or in an emergency the presiding arbitrator acting alone in the event one or more of the other arbitrators is unable to be involved in a timely fashion) may grant interim measures including injunctions, attachments and conservation orders in appropriate circumstances, which measures may be immediately enforced by court order. Hearings on requests for interim measures may be held in person, by telephone, by video conference or by other means that permit the parties to the Dispute to present evidence and arguments.

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