Authentication Tokens Sample Clauses

Authentication Tokens. 2. Contractor may be asked to submit a Cloud Security Alliance Consensus Assessments Initiative Questionnaire (CAIQ) dated 1/1/2015 or later. 3. Contractor may be asked to submit its most recent ISO 9001. 4. Contractor may be asked to share their breach notification and response plan. 5. Contractor may be asked to submit its most recent ISO 27001. 6. Contractor may be asked to submit its most recent SSAE 16 Standard Report. 7. Contractor may be asked to submit overview of business continuity/disaster recovery executive briefing. PAYMENT AND DELIVERABLES Payments to Contractor for completing the Individual Implementation Plan will be based on the Deliverables as described in the Individual Implementation Plan. These Deliverables are not based on the Contractor’s effort, but rather are based on the percent the Authorized User is willing to pay per Deliverable of the Contractor’s total anticipated price of the Individual Implementation Plan for the Authorized User. The percentages will be paid based on actual costs at a time as agreed upon in the Individual Implementation Plan. Deliverable 1: Agreed upon Individual Implementation Plan (10%). Deliverable 2: Configured, tested and acceptance of 50% of Authorized User scripts as described in Implementation Plan (30%). Deliverable 3: Security plan that encompasses all the details outlined in the NYS Secure Systems Development Life Cycle Standard (NYS-S13-001) (10%) Deliverable 4: Go Live Production Environment (30%).

Authentication Tokens. If included in an RFQ, OPWDD Agreement may require authentication tokens for all systems in accordance with NIST 800-63B Authentication and Lifecycle Management, or its successor.