Advanced Cybersecurity Experts, LLC (ACE)
LinkAI comparisonLike Assurit, uses four review passes; lists schema failures among not-ready conditions, while KITC ties that category to failures preventing review.
We read the Security Decision Record (SDR) four times. Each pass asks one question. Each maps to the SDR rules.
1. Is it all there? Each rule needs all seven SDR-CSO-FRR items. Each KSI needs its SDR-CSX-KSI summaries. We need both the JSON and the human-readable SDR. The SDR-CSO-MTD data must show version, last update, and source. Metrics must meet SDR-CSX-KMT for the package Class. 2. Is it enough? The measures must fit the real system. That means its boundary, data flows, and inherited services. The automation must be shown to be accurate. A rule not followed needs a stated risk to customers and sign-off by a senior official. 3. Does it agree? IDs, counts, and dates must match in the JSON, the SDR text, the test output, and the independent results. 4. Can we trace it? Each claim must link to proof, a test result, an independent result, and the provider's reply.
Proof we expect: config exports, logs, metric history, inventories, boundary and data flow maps, test output, and the assessor's results and comment log.
What each problem triggers: - Question: a detail is unclear or missing, but likely exists. Example: no cycle is stated for a persistent measure. - Finding: the proof does not back the claim. Or it is stale, or it conflicts. Example: metrics show a gap the SDR does not name. - Escalation: a large risk. A repeat issue across packages. A doubt about the assessor's independence. A big risk the provider chose to accept. A blocker that threatens the schedule. - Not ready to proceed: the JSON fails the schema check. The JSON or the text SDR is missing. Independent verification or validation is missing. The boundary is not defined. Required metrics are missing, with no agreed fix.
We recommend. The Government decides.