Vulnerabilities and Testing Scenarios Sample Clauses

Vulnerabilities and Testing Scenarios. Given the sensitivity of data processed in the MES and the high threat of the web environment, it is critically important that the security of web applications deployed meet the present-day known Final Draft Centers for Medicare & Medicaid Services security attack vectors and situations. The Open Web Application Security Project (OWASP)3 keeps an up-to-date list that identifies such attacks and situations. In addition to the mandated security and privacy controls, the independent SCA requires penetration tests to determine vulnerabilities associated with known attacks and situations obtained from the current OWASP Top 10 – The Ten Most Critical Web Application Security Risks. The assessment should adjust the SCA scope to address current OWASP list of vulnerabilities. The state should regularly review the following list to determine the current vulnerabilities in the OWASP Top 10, including, but not limited to: • Injection; • Broken Authentication; • Sensitive Data Exposure; • XML External Entity (XXE); • Broken Access Control; • Security Misconfiguration; • Cross-Site Scripting (XSS); • Insecure Deserialization; • Using Components with Known Vulnerabilities; and • Insufficient Logging and Monitoring.
Sample 1
AutoNDA by SimpleDocs

Related to Vulnerabilities and Testing Scenarios

  • Non-Grievability No dispute over a claim for any benefits extended by this Health and Welfare Fund shall be subject to the grievance procedure.

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Vulnerability Management BNY Mellon will maintain a documented process to identify and remediate security vulnerabilities affecting its systems used to provide the services. BNY Mellon will classify security vulnerabilities using industry recognized standards and conduct continuous monitoring and testing of its networks, hardware and software including regular penetration testing and ethical hack assessments. BNY Mellon will remediate identified security vulnerabilities in accordance with its process.

  • Substance Abuse Testing The Parties agree that it is in the best interest of all concerned to promote a safe working environment. The Union has no objection to pre-employment substance abuse testing when required by the Employer and further, the Union has no objection to voluntary substance abuse testing to qualify for employment on projects when required by a project owner. The cost and scheduling of such testing shall be paid for and arranged by the Employer. The Union agrees to reimburse the Employer for any failed pre-access Alcohol and Drug test costs.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Performance Testing 7.2.1 The Design-Builder shall direct and supervise the tests and, if necessary, the retests of the Plant using Design-Builder’s supervisory personnel and the Air Emissions Tester shall conduct the air emissions test, in each case, in accordance with the testing procedures set forth in Exhibit A (the “Performance Tests”), to demonstrate, at a minimum, compliance with the Performance Guarantee Criteria. Owner is responsible for obtaining Air Emissions Tester and for ensuring Air Emissions Tester’s timely performance. Design-Builder shall cooperate with the Air Emissions Tester to facilitate performance of all air emissions tests. Design-Builder shall not be held responsible for the actions of Owner’s employees and third parties involved in the Performance Testing, including but not limited to Air Emissions Tester.

  • Grievability Denial of a petition for reinstatement is grievable. The grievance may not be based on information other than that shared with the Employer at the time of the petition for reinstatement.

  • STATEWIDE ACHIEVEMENT TESTING When CONTRACTOR is an NPS, per implementation of Senate Bill 484, CONTRACTOR shall administer all Statewide assessments within the California Assessment of Student Performance and Progress (“CAASP”), Desired Results Developmental Profile (“DRDP”), California Alternative Assessment (“CAA”), achievement and abilities tests (using LEA-authorized assessment instruments), the Fitness Gram with the exception of the English Language Proficiency Assessments for California (“ELPAC”) to be completed by the LEA, and as appropriate to the student, and mandated by XXX xxxxxxxx to LEA and state and federal guidelines. CONTRACTOR is subject to the alternative accountability system developed pursuant to Education Code section 52052, in the same manner as public schools. Each LEA student placed with CONTRACTOR by the LEA shall be tested by qualified staff of CONTRACTOR in accordance with that accountability program. XXX shall provide test administration training to CONTRACTOR’S qualified staff. CONTRACTOR shall attend LEA test training and comply with completion of all coding requirements as required by XXX.

  • Geometric visibility The visibility of the illuminating surface, including its visibility in areas which do not appear to be illuminated in the direction of observation considered, shall be ensured within a divergent space defined by generating lines based on the perimeter of the illuminating surface and forming an angle of not less than 5° with the axis of reference of the headlamp. The origin of the angles of geometric visibility is the perimeter of the projection of the illuminating surface on a transverse plane tangent to the foremost part of the lens of the headlamp.

Time is Money Join Law Insider Premium to draft better contracts faster.