1-3 | What the scheme is, who may certify under it, and the terms it uses | 0 |
10.2-10.4 | Report indicators of effectiveness at the defined levels, from approved testing and audit, on a valid statistical basis, and publish summaries | 0 |
10.5-10.8 | Report indicators per component and system, disclose demographic coverage and error parity, add local indicators, and use the standard table | 0 |
11 | Produce a Stage Two audit report to the mandatory template and assemble a complete, version-controlled audit package | 0 |
12.2-12.3 | Obtain an independent evaluation review and a documented certification decision by independent certification officers | 0 |
12.4-12.6 | Receive a certificate and schedule that separate what is and is not certified, appear in the public registry, use the mark within scope, and optionally pursue IEEE 2089.1 certifica | 0 |
13.2-13.3 | Undergo annual surveillance audits that confirm the practice statement, scope, indicators, change control and obligations are maintained | 0 |
13.4-13.5 | Run continuous monitoring of accuracy, parity, attack resilience, incidents and performance, review it, and notify major changes and material incidents | 0 |
13.6 | Complete a recertification audit before expiry, with fresh test evidence and current requirements | 0 |
14 | Scheme revision: alignment with ISO/IEC 27566 and controlled updates | 0 |
4.1-4.4 | Define and record the certification scope by client role: provider, relying party or intermediary | 0 |
4.10 | Declare the assumptions the item depends on and the exclusions from its certification | 0 |
4.5 | Declare known and anticipated attack vectors | 0 |
4.6 | Define repeatable scope boundaries with architecture, identification and an inclusions and exclusions statement | 0 |
4.7 | Define the contexts of use: sectors, channels, use type and jurisdictions | 0 |
4.8 | Keep certification current: three-year cycle, annual surveillance, continuous monitoring, change notification and the minor versus major change test | 0 |
4.9 | Declare every data source, its authority, governing terms and third-party dependencies | 0 |
5.1-5.2 | Publish a practice statement in the ISO/IEC 27566-1 Clause 10 structure with the scheme's additional content | 0 |
5.3-5.6 | Assess the practice statement against the five core characteristics, keep it current and submit updates | 0 |
5.7 | Declare ISO 10007-based configuration management and constrain relying party configuration options that could weaken conformity | 0 |
5.8 | Control, version and retain the practice statement, and submit major-change updates within 14 days | 0 |
5.9-5.10 | Declare external certifications and evidence, accept the scheme's weighting, and notify lapses within 14 days | 0 |
6 | Pass a Stage One audit of the practice statement, governance, legal standing, impartiality, privacy baseline, risk, management systems and monitoring readiness | 0 |
7.11-7.14 | Where reduced-sample designs are used, pre-register the statistics, respect stratified floors, apply the acceptance rules and protect data integrity | 0 |
7.2-7.3 | Use competent, independent test analysts and build test plans that map every practice statement claim to a test with acceptance criteria | 0 |
7.4-7.6 | Cover functionality, accuracy, performance, attack resistance and the declared characteristics, with samples sized to the claimed level and demographically varied | 0 |
7.7-7.8 | Apply national and jurisdictional test requirements and document plans, results and testing limitations | 0 |
7.9-7.10 | Weigh external test results by accreditation and keep responsibility for outsourced testing with the conformity assessment body | 0 |
8.2-8.3 | Execute testing to the approved plan, record deviations, keep it reproducible and analyse results against the declared indicators | 0 |
8.4-8.6 | Report tests to international formats, at component and system level, submit them in full and publish summaries | 0 |
9.2-9.3 | Submit to the mandatory Stage Two activities and make the required evidence available | 0 |
9.4-9.6 | Demonstrate conformity on functionality, performance, privacy, security and acceptability, per component and at system level, and for each declared jurisdiction and sector | 0 |
9.7 | Receive a Stage Two report that maps every practice statement claim to evidence and categorises nonconformities | 0 |
A-H | Annexes: transition from PAS 1296 and legacy ACCS standards, audit effort calculation, templates, model certificate and normative mapping | 0 |