Role Based Access Control Sample Clauses

Role Based Access Control. (RBAC) Roles Resources Subjects Role 1 Role 2 Role 3 Figure 14: RBAC model Permission User Role
Sample 1
AutoNDA by SimpleDocs
Role Based Access Control a) Initial permission definitions, and changes to permissions associated with logical access roles are approved by appropriate personnel. b) Access that allows modification to source code is restricted to authorized personnel. c) Role based and context based access to data is modeled on the concept of least privilege. d) Adobe restricts the use of shared service account authentication credentials via the use of a shared secret solution. Authentication credentials for shared service accounts are reset every 90 days.
Sample 1
Role Based Access Control. Client’s designated account administrator is responsible for role administration. Client may self-manage role administration via the DD web applications.
Sample 1
Role Based Access Control. All COUNTY staff and poll workers permitted access shall be issued user names and passwords and shall be grouped in the system by role, and granted access based upon their designated role.
Sample 1
Role Based Access Control. Your designated administrator is responsible for role administration. You may self-manage role administration via the Hotlink Control Panel. When making permission changes with Role-Based Access Control, there may be a delay before the implementation of changes, including self-managed changes. Some changes may require you to logout and login again to start a fresh session for the changes to take effect. HSPL is not responsible for any loss that may occur due to the delayed implementation of changes.
Sample 1
Role Based Access Control. (RBAC) 1. Role Assignment: a subject (e.g. person) must be member of a specific role in order to get access to a specific resource.
Sample 1
Role Based Access Control. Microsoft Cloud 4.1. Where Opus provides Microsoft cloud services to the Customer, they agree to Opus maintaining RBAC (Role Based Access Control) into the Customer’s Microsoft cloud tenancy, systems and Azure subscriptions, in order that Opus can provide support and be the commercial transaction partner for Microsoft cloud services, for the entire Initial Term of the relevant Order and/or Agreement and any subsequent extensions.
Sample 1
AutoNDA by SimpleDocs

Related to Role Based Access Control

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

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

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

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

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

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

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

  • Interconnection Customer Compensation for Actions During Emergency Condition The CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff for its provision of real and reactive power and other Emergency Condition services that the Interconnection Customer provides to support the CAISO Controlled Grid during an Emergency Condition in accordance with Article 11.6.

  • Signaling protocol 4.1.3.1 SS7 Signaling is AT&T-21STATE’s preferred method for signaling. Where MF signaling is currently used, the Parties agree to use their best efforts to convert to SS7. If SS7 services are provided by AT&T-21STATE, they will be provided in accordance with the provisions of the applicable access tariffs. 4.1.3.2 Where MF signaling is currently used, the Parties agree to interconnect their networks using MF or dual tone MF (DTMF) signaling, subject to availability at the End Office Switch or Tandem Switch at which Interconnection occurs. The Parties acknowledge that the use of MF signaling may not be optimal. AT&T-21STATE will not be responsible for correcting any undesirable characteristics, service problems or performance problems that are associated with MF/SS7 inter-working or the signaling protocol required for Interconnection with CLEC employing MF signaling.

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

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