Advanced Cybersecurity Experts, LLC (ACE)
Link10/23/2026
AI comparisonLike Devis, uses sign-in metrics and an alternate access path to distinguish configured authentication from observed coverage.
A KSI is met when three things are true. The measure fits the KSI. The measure works. Someone outside the provider has checked both. Our reviewers test each link.
- Security assertion: what the provider says is true.
- Security measure: the thing they do or track that makes it true.
- Evidence of implementation: proof the measure exists. Example: a config export.
- Evidence of effectiveness: proof it works over time. Example: logs or metrics.
- Verification: is this the right measure, and is it enough to show the KSI? Is the automation right?
- Validation: is the measure in place and working?
- Independent verification and validation (IV&V): a party outside the provider does both checks. The provider then answers its comments.
For each KSI we ask five things. Does the SDR entry cover each SDR-CSX-KSI item? Does the measure fit the boundary? Is the proof current for the stated cycle? Do the JSON and text agree? Did IV&V find the same thing?
Example: KSI-IAM-APM (Adopting Passwordless Methods).
- Assertion: "All users sign in with phishing-resistant MFA."
- Measure: a sign-in rule that requires FIDO2 or PIV. Plus a daily count of accounts that lack one.
- Proof it exists: the rule export. It applies to all user groups.
- Proof it works: 30 days of sign-in logs. Every login used FIDO2 or PIV.
- Verification: does the rule cover admin consoles, break-glass accounts, and every tenant? Does the daily count pull from the real user list?
- Validation: the count matches a sample we pull from the logs. A test login with a password gets blocked.
- IV&V: the 3PAO ran the same checks. Its comments are closed.
Now say the rule is right, but 3% of logins still use passwords through an old app. The measure exists, but it does not fully work. We raise a question. We log it in the review sheet and tie it to the log data.
11/2/2026
AI comparisonLike FITS, uses an access-control example; focuses on just-in-time privilege, expiry logs, and policy queries.
We treat a KSI as demonstrated only when the chain from claim to independent check is complete. Our reviewers organize around the following terms:
• Assertion: the provider's claim of a security outcome.
• Measure: the objective, repeatable metric or method used to evaluate that outcome.
• Evidence of implementation: artifacts showing the capability exists as described (configurations, policies, IaC).
• Evidence of effectiveness: data showing the KSI operates as intended over time, not at a single point.
• Verification: confirming the implementation matches the documented design (built right).
• Validation: confirming the implementation achieves the intended outcome in operations.
• IV&V: verification and validation by a FedRAMP Recognized assessor independent of the provider, reviewed at a technical level rather than from documentation or screenshots alone.
A KSI is adequate when the assertion is specific to the boundary, the measure is defined, implementation and effectiveness evidence are current and traceable, and automated validation results agree with the evidence. A KSI passing automated validation alone is not proof. We seek to document where automation stops and engineering judgment begins.
An example of our approach using just-in-time privileged access (KSI-IAM-JIT):
• Assertion: no human holds standing admin access to production.
• Measure: count of identities with persistent admin rights; target zero, checked daily.
• Implementation: IdP group mappings, cloud IAM policies, and JIT elevation configuration.
• Effectiveness: daily metric history and elevation logs showing time-bound grants that expired, with zero persistent assignments.
• Verification: automated policy query confirms deployed roles match the design stated in the SDR.
• Validation: a test elevation confirms access is granted, scoped, logged, and revoked on expiry.
• IV&V: the assessor re-runs the query and samples log records against the daily measure; our reviewers confirm the SDR reflects that work and spot-check it with Government-approved tools.
If a provider submits only the policy export, we record implementation without effectiveness and issue a question, not an acceptance.
We apply this model today, dual-tagging a SaaS provider's Rev. 5 evidence to KSIs, and are scoping KSI evidence plans for a 20x Class B candidate.
10/29/2026
AI comparisonLike IBSS, describes passwordless methods with a fallback; includes historical logs and attempted authentication downgrades.
Our reviewers treat a KSI as demonstrated only when validated evidence of effectiveness shows the intended outcome in production and, where the Class requires it, an independent assessor has confirmed it.
- Security assertion: the provider's claim that the KSI is met.
- Security measure: the repeatable mechanism, with a defined cycle, that produces data on whether the KSI is met.
- Evidence of implementation: proof the mechanism is in place. It is the result of verification.
- Evidence of effectiveness: proof the mechanism produces the intended outcome in operation. It is the result of validation.
- Verification: confirming implemented measures match the documented measures (configured to block).
- Validation: confirming the measures achieve the intended outcome (actually blocked).
- Independent verification and validation: a FedRAMP Recognized assessor re-performs both through technical review of configurations, code, and data, not screenshots, at least annually for Class B and above.
Example, KSI-IAM-APM (Adopting Passwordless Methods):
- Assertion: users authenticate with passwordless FIDO2/PIV; where infeasible, strong passwords plus phishing-resistant MFA are required.
- Measure: a daily automated query of identity provider policy and authentication logs.
- Implementation evidence (verification): the IdP policy export shows FIDO2/PIV enforced where feasible, phishing-resistant MFA required on remaining accounts, and legacy protocols disabled. The reviewer confirms scope includes service and break-glass accounts.
- Effectiveness evidence (validation): 30 days of logs, or a documented representative sample, for standard, privileged, and break-glass users show passwordless sign-in where feasible and phishing-resistant MFA on every fallback. A one-time-code-only test login was denied and logged.
- IV&V: the independent assessor samples accounts, re-runs the query, and attempts the downgrade independently.
We would find a KSI not demonstrated in any of five cases. The measure does not map to the KSI's outcome. Implementation evidence exists without effectiveness evidence. Samples, where used, are not documented. Data is stale relative to the measure's cycle. The independent assessment restates provider results instead of re-performing them. Each conclusion records the KSI, the evidence examined, and the gap, so the Government can trace it and decide.
Cloud9 Security Services, Inc.
Link10/29/2026
AI comparisonLike RADIX, includes a deliberately noncompliant sign-in test; uses a privileged-account query and a password-only test account.
A KSI is adequately demonstrated only when the provider's measures, run on their stated cycle, show the security outcome is achieved across the full boundary, and, where the certification class requires it, an independent assessor has confirmed it. Reviewers apply these terms from the Security Decision Record:
• Security assertion: the provider's claim that an outcome is achieved. It is a starting point, not proof.
• Security measure: the specific, repeatable mechanism the provider uses to show the outcome, with its objective, scope and cycle.
• Evidence of implementation: proof the measure and underlying configuration are in place as documented.
• Evidence of effectiveness: output over time showing the measure works and the outcome holds, including detected exceptions and their handling.
• Verification: confirming that what is implemented matches what is documented.
• Validation: confirming the implemented measure actually achieves the intended outcome.
• Independent verification and validation (IVV): the same two checks performed by an independent FedRAMP Recognized assessor.
• Reviewers check that the measure covers every in-scope account, component and environment; that evidence is current, consistent with the boundary and traceable; that automation output is machine-readable and schema-valid; and that IVV results appear unmodified. Gaps become questions or findings tied to the specific evidence.
• Example, KSI-IAM-APM (Adopting Passwordless Methods):
• Assertion: "All privileged users authenticate with phishing-resistant FIDO2 passkeys; no passwords."
• Measure: a daily automated query of the identity provider listing privileged accounts without a FIDO2-only policy, with alerts on any exception.
• Evidence of implementation: the exported IdP authentication policy and the query code, matching the SDR description.
• Evidence of effectiveness: 90 days of query results showing zero or quickly remediated exceptions and their tickets.
• Verification: the reviewer confirms the exported policy and query match the documented measure and cover all privileged groups, including break-glass accounts.
• Validation: a seeded test account with password-only login is flagged within one cycle and blocked.
• IVV: the provider's Recognized assessor performs the verification and validation independently and reports results in the package.
11/2/2026
AI comparisonLike CVP, includes configuration, logs, and a second reviewer; also describes Government checks and six months of log history.
[personal name removed] (30+ years, CISSP, PMP, RegScale Certified Admin), our proposed FedRAMP Lead who currently owns FedRAMP High authorization and leads Security Decision Record review for a multi-cloud SaaS platform, evaluates KSI demonstration by separating distinct evidence layers rather than accepting a single claim at face value, and records a recommendation for the Government.
A security assertion is the provider's stated claim that a control exists (for example "all production access requires multi-factor authentication"). A security measure is the specific control actually implemented to satisfy that claim, such as a named policy or configuration. Evidence of implementation is documentation or configuration exports proving the measure was genuinely deployed, not merely planned. Evidence of effectiveness uses operational data such as authentication logs, scan results, or monitoring metrics to show the measure functions as intended over a sustained period, not just at a single point in time.
Verification is the reviewer's check that documented evidence is internally consistent with the assertion and measure, confirming the paperwork lines up. Validation confirms, through the Government's automated checks on the machine-readable KSI data and review of operational output, that the control produces the required outcome in the live environment and that the narrative matches the machine-readable data. Independent verification and validation (IV&V) adds a layer: a reviewer with no role in the first review repeats these steps and the 3PAO's independent assessment is compared against both results, removing bias before the Government relies on the result.
Example: a provider asserts under KSI-IAM that all production access requires MFA. The measure is a Microsoft Entra ID Conditional Access policy enforcing MFA on production accounts. A configuration export confirming organization-wide application is evidence of implementation. Six months of authentication logs showing zero successful non-MFA logins is evidence of effectiveness. [personal name removed] first verifies the configuration matches the assertion, then validates by running the Government's automated check on the KSI data and reviewing the logs. A second reviewer, uninvolved so far, re-performs the evidence check and confirms the 3PAO reached the same result, completing IV&V for a defensible KSI recommendation.
Customer Value Partners, LLC
Link11/2/2026
AI comparisonLike the later CyberStorm submission, uses encryption; describes configuration, logs, and a second internal reviewer.
CVP's personnel would evaluate KSI demonstration by progressing through a structured evidence hierarchy, drawing on our USDA FSIS experience conducting approximately 4,000 security control tests annually across 11 system boundaries in a FedRAMP Azure Government environment.
A security assertion is an unsubstantiated provider claim that a control or capability exists, such as stating that multi-factor authentication is enabled. A security measure is the specific technical or procedural mechanism implemented to satisfy a security requirement, such as an MFA policy or configuration standard. Evidence of implementation is documentation or artifact demonstrating the measure has been deployed, such as a screenshot, configuration export, or system security plan control implementation summary. Evidence of effectiveness demonstrates the measure is operating as intended and producing the desired security outcome, such as authentication logs confirming MFA challenges are consistently enforced. Verification confirms that the evidence of implementation is accurate, complete, and consistent with stated configurations. Validation confirms that the implemented measure actually satisfies the intent of the KSI requirement. Independent verification and validation applies all prior steps through a reviewer with no involvement in the package development, ensuring objectivity and freedom from bias.
CVP's FSIS experience directly informs this hierarchy. Our teams routinely distinguished between what system owners claimed in SSPs versus what control testing and artifact review confirmed, reducing disputed findings from 23 per month to one per month over three years.
Example: A CSP asserts encryption at rest is enabled (assertion). AES-256 encryption is configured on all storage volumes (measure). A configuration report export shows encryption enabled on all volumes (implementation evidence). Audit logs confirm no unencrypted data writes occurred over 90 days (effectiveness evidence). CVP verifies the configuration report matches the deployed environment (verification). CVP confirms AES-256 satisfies the KSI encryption requirement (validation). A separate CVP reviewer with no prior package involvement repeats verification and validation independently (IV&V).
Cyber Management International Corporation
Link11/2/2026
AI comparisonLike Vertekal, uses remediation work rather than authentication; includes vulnerability coverage, tickets, exceptions, and retests.
We would begin by identifying the specific KSI, its intended security outcome, applicable measurement criteria, scope, and any Government-provided validation rules.
A security assertion is the provider's claim about its security posture or outcome.
A security measure is the defined method, metric, or observable used to assess that claim.
Evidence of implementation shows that the capability or process exists and is configured.
Evidence of effectiveness shows that it operates as intended and achieves the required outcome over the relevant period.
Verification determines whether the measure and supporting evidence conform to stated requirements and criteria.
Validation considers whether the demonstrated capability is effective for the intended security outcome in the provider's actual environment.
Independent verification and validation (IV&V) adds review by a party sufficiently independent of the provider's implementation and operation to provide objective confirmation.
Reviewers should not treat a provider assertion, a configuration screenshot, or a successful automated check as proof of effectiveness by itself. For example, a provider may assert that it continuously identifies and remediates vulnerable assets. Measures could include asset coverage, time to detect, remediation time by severity, and overdue vulnerabilities. Implementation evidence could include the deployed scanning and asset-inventory configuration, defined workflows, and assigned response responsibilities. Effectiveness evidence could include time-series scan results, asset coverage reports, sampled findings, remediation tickets, exception records, and retest results showing that fixes were completed.
We would verify that the reported measures are calculated as defined, cover the stated environment, and reconcile to source records; then validate whether the results demonstrate the intended risk-reduction outcome. IV&V would require an appropriately independent party to perform or confirm that work. CMIC's Wiz experience informs our understanding of operational visibility and vulnerability workflows, but is not represented as independent KSI validation.
10/26/2026 · S03
AI comparisonThis cell describes SDR review gates, whereas ACE and other answers use examples of individual security measures.
This text is in the original column. The apparent answer to this question is elsewhere in this submission.
1. Completeness: every required element is present: scope and boundary, decision and rationale, the KSIs or rules affected, compensating measures, residual risk, owner and date. We confirm referenced artifacts exist and open.
2. Technical sufficiency: the rationale holds up against the architecture, threat and data flows. Evidence expected: configuration exports, machine-readable validation output, logs or test results, and assessor results where required.
3. Consistency: the SDR agrees with the SSP or package narrative, machine-readable data, inventory, POA&M and prior SDRs. Identifiers, versions and dates match across artifacts.
4. Traceability: each claim links to a specific evidence item, each evidence item to a KSI or rule, and each change to a dated version.
Outcomes:
• Question: a clarification or missing reference the provider can likely resolve quickly.
• Finding: evidence is missing, stale, contradictory or does not support the claim; logged with requirement, condition and needed action.
• Escalation to the Government Task Lead: a material risk, a disputed interpretation, a repeat deficiency, a schedule-critical issue or a possible integrity problem with evidence.
• "Not ready to proceed": a core boundary or KSI cannot be evaluated; machine-readable data fails validation in ways that block review; required assessor evidence is absent; or unresolved high-severity findings remain after the response cycle.
11/2/2026 · S26
AI comparisonLike CVP, uses encryption; includes infrastructure-as-code, runtime logs, and direct probes.
CyberStorm Defense personnel evaluate Key Security Indicators (KSIs) by translating high-level security claims into immutable technical artifacts and empirical test outputs.
Definitions & Distinctions:
Security Assertion: A provider's qualitative claim that a security control requirement is satisfied (e.g., "All stored data is encrypted at rest").
Security Measure: The specific technical or operational mechanism deployed to fulfill the assertion (e.g., configuring AWS Key Management Service with customer-managed AES-256 keys).
Evidence of Implementation: Static or structural artifacts proving the security measure exists and is configured correctly (e.g., Terraform configuration files, architecture boundary diagrams).
Evidence of Effectiveness: Dynamic, empirical test data proving the security measure functions successfully under operational conditions (e.g., automated scan results, runtime logs, cryptographic validation tests).
Verification: Internal evaluation confirming that a security measure meets specified design, configuration, and engineering specifications.
Validation: Objective confirmation that the implemented security measure fulfills its intended operational purpose within the defined system authorization boundary.
Independent Verification and Validation (IV&V): Unbiased, third-party technical assessment conducted by an independent engineering team (such as CSD) that independently re-tests, inspects, and certifies both verification and validation without conflict of interest.
Concise Application Example (Encryption at Rest):
A CSP makes a security assertion that databases are secure. They deploy AWS KMS AES-256 as their security measure. CSD inspects Terraform scripts and configuration exports as evidence of implementation, then reviews automated runtime execution logs and active key-rotation telemetry as evidence of effectiveness. Internal engineering teams perform verification of the configuration, vulnerability scans provide validation against NIST SP 800-53 controls, and CSD's independent assessment team conducts IV&V by executing direct API probes and storage volume inspections to certify the control's integrity
Dekalb Solutions LLC (DBA CybertLabs)
Link11/2/2026
AI comparisonLike TES, examines more than one authentication path; includes two identity providers and cloud-local access.
Our reviewers determine whether a KSI is adequately demonstrated by following the provider's claim through to independent confirmation. We report findings and recommendations to the Government, which decides whether the KSI is accepted.
Take a cloud service hosted on one cloud service provider (CSP) with two identity providers: a workforce identity provider federated to the CSP for the provider's own administrators, and a customer identity provider for tenant administrators. The provider makes the security assertion that all privileged access through either identity provider requires phishing-resistant MFA, and that no local CSP accounts bypass it. The security measures are conditional access policies in both identity providers requiring hardware security keys for administrator roles, a CSP IAM policy denying console and API access without MFA, and a daily metric counting privileged sessions without MFA across all three. To verify these measures, the provider's engineers compare the policies exported from its infrastructure-as-code repository against the documented design and the privileged role inventory. Matching exports covering every privileged role, with no local accounts beyond documented break-glass access, are the evidence of implementation. The provider then validates in production: engineers review 30 days of authentication logs from both identity providers and the CSP audit log showing no privileged sessions without MFA, confirm that a legacy-protocol login and a direct role assumption that skips the identity provider are both denied, and check that the daily metric agrees with the logs. Those logs, test results, and metric history are the evidence of effectiveness.
Independent verification and validation (IV&V) follows, performed by a FedRAMP-recognized assessor who repeats both steps at a technical level instead of relying on documents or screenshots. The assessor inspects each policy directly, reruns the denied-access tests, tests the metric pipeline, and reports any findings and disputes. Our reviewers confirm that each element is present, current, within the authorization boundary, and traceable to the KSI objective. If a package offers only the assertion and screenshots, we request the missing evidence before reaching a conclusion.
Deloitte Consulting LLP
Link11/2/2026
AI comparisonLike CVP, uses encryption-related evidence; labels its scenario as illustrative and includes independent sampling.
We assess a KSI by tracing the requirement to the provider’s assertion, measure, and supporting evidence, then evaluating whether the evidence demonstrates implementation and effectiveness against applicable FedRAMP 20x criteria. We use Government- or solicitation-defined terms where they differ.
A security assertion is the provider’s claim about a security outcome. A security measure is the metric or test used to assess that claim. Implementation evidence shows the indicator is deployed as described; effectiveness evidence shows it operates as intended over time. Verification checks that the implementation and evidence match the stated requirements. Validation assesses whether the implemented control or process achieves its intended security outcome. Independent verification and validation (IV&V) is a separate review or testing activity by an appropriately independent party, within a defined scope.
Illustrative example, not an official KSI: “No unresolved critical or high encryption-related vulnerabilities in production.” The assertion is that no such vulnerabilities remain. The measure is the count of open findings in scope. Implementation evidence could include system configurations and documentation showing applicable validated cryptographic modules are in use. Effectiveness evidence could include recent scan or test results and remediation records.
Reviewers verify by checking that the configurations, asset scope, and scan results support the reported count. They validate by assessing whether the evidence reasonably demonstrates the intended outcome across in-scope production systems and over the relevant period. If required, an independent reviewer could examine the test method and independently sample or repeat checks. Gaps in scope, unsupported claims, or contradictory evidence would prompt clarification or further review before concluding the KSI is demonstrated. This can be accelerated with Deloitte’s deep experience with OSCAL innovations for standardized, machine-readable content that enables automated data sharing, having developed OSCAL translation accelerators for GRC tools.
Development InfoStructure, LLC (Devis)
Link11/2/2026
AI comparisonLike ACE, uses an authentication counterexample alongside reported metrics; its example concerns SMS fallback.
Under the Consolidated Rules for 2026, a KSI is demonstrated when the Security Decision Record shows measures that address it, verification and validation of those measures, and independent verification and validation, all traceable to evidence (SDR-CSX-KSI, SDR-CSO-FRR, IVV-CSX-AIA).
- Security assertion: the provider's statement of how the KSI is met. A claim, not proof.
- Security measure: a repeatable check, with a stated objective and cycle, that produces data on whether the KSI is met.
- Evidence of implementation: the result of verification (IVV-CSO-SEI), showing the measure is deployed as documented, best drawn from the source of truth, not screenshots.
- Evidence of effectiveness: the result of validation (IVV-CSO-SEE), showing the measure produces the intended outcome over time, such as daily metric data and logs.
- Verification: objective evidence that the FedRAMP Practice is fulfilled (FRD-VRF). Was it built as the KSI requires?
- Validation: objective evidence that the capability and its certification data suit their intended use and support the expected outcome (FRD-VLN). Does it work, and does the measure tell the truth?
- IV&V: verification and validation by a FedRAMP Recognized independent assessment service, or rarely FedRAMP (FRD-FIN), not the provider or its advisors.
Example, KSI-IAM-APM (passwordless methods, or strong passwords with phishing-resistant MFA):
- Assertion: "All user authentication uses passkeys or phishing-resistant MFA."
- Measure: daily percentage of user accounts whose sign-in policy enforces a phishing-resistant method.
- Implementation: identity provider policy export showing enforced methods and scope.
- Effectiveness: 30 days of daily metrics and sign-in logs showing no user sign-in by a weaker method.
- Verification: reconcile the user inventory against policy scope; every user is covered.
- Validation: test what the measure could miss, such as legacy protocols or an SMS fallback. With SMS fallback enabled, the measure reads 100 percent and the KSI is still not met. Non-user accounts fall under KSI-IAM-SNU.
- IV&V: confirm the assessor's results are in the record and the provider answered its comments.
Any missing link is a finding.
11/2/2026
AI comparisonLike Softthink, uses account lifecycle and authoritative records; connects evidence review to its proposed service tiers.
EY would find a KSI demonstrated only when current, traceable evidence in the Security Decision Record (SDR) links the KSI outcome to the provider's assertion, measure, implementation, effectiveness, and independent verification and validation; otherwise, EY would report it as partially or not demonstrated. Tier 1 would use automation and pull machine-readable evidence from the providers Trust Center and flag exceptions; Tier 2 reviewers would judge sufficiency; Tier 3 independent QA would review complex or consequential conclusions.
A security assertion is the provider's claim that a KSI is met within a defined scope. A security measure is the metric tracking the KSI outcome, with defined source data, population, logic, cadence, and thresholds. Implementation evidence is artifacts and live data showing capability deployed across that scope. Effectiveness of evidence is historical operating results showing the measure meets its threshold, and exceptions are resolved.
- Verification is a test of design: is the implementation appropriate for the KSI?
- Validation is a test of effectiveness: is it in place and working as intended?
Independent verification and validation repeat both through FedRAMP Recognized independent assessment service using its own sampling and tests; EY would evaluate that work, not replace it.
Ex. (KSI-IAM-AAM, Automating Account Management): The provider asserts automation manages the lifecycle and privileges of all accounts, roles, and groups. The measure reports the share of accounts provisioned and removed through the workflow and time to remove access against a threshold.
- Implementation evidence: IAM configurations, role definitions, and identity-provider records covering human, service, and administrative accounts.
- Effectiveness evidence: metrics over time and exceptions, such as orphaned accounts or overdue removals, and how each was resolved.
- Verification: reviewers confirm that the workflow design and account population fit the KSI and assertion.
- Validation: reviewers trace results to authoritative records showing access to stay within the workflow and is removed on time.
- IVV: the independent assessor tests the same population; EY checks its scope, samples, and conclusions. Reviewers would document conclusions, evidence, limitations, and gaps for GSA's decision.
11/2/2026
AI comparisonLike Cloud9, uses recurring checks and test results; also compares deployed settings with infrastructure-as-code.
A KSI is adequately demonstrated only when each element below is present, current, traceable, and consistent with the SDR:
- Security assertion: the provider's claim that an outcome is met.
- Security measure: the safeguard or repeatable activity that produces the outcome.
- Evidence of implementation: proof the measure is deployed as documented; the result of verification (IVV-CSO-SEI).
- Evidence of effectiveness: proof the measure achieves its outcome over time; the result of validation (IVV-CSO-SEE).
- Verification: confirmation that FedRAMP practices are fulfilled as documented.
- Validation: confirmation that capabilities and certification data work for their intended use.
- Independent verification and validation: a FedRAMP Recognized assessor examining and re-performing both.
Reviewers apply NIST SP 800-53A to judge evidence sufficiency and appropriateness, use documented sampling, compare infrastructure-as-code baselines with deployed state to detect drift, and engage cloud-platform SMEs on technical questions. They confirm automation is accurate and runs at the required cycle (SDR-CSX-KSI). Our assessors applied this method to KSI evidence as the IAS for a FedRAMP 20x Low pilot system. For DHA, we also performed formal independent verification and validation.
Example, phishing-resistant MFA (KSI-IAM):
- Assertion: all users authenticate with phishing-resistant MFA.
- Measure: an identity provider policy requiring FIDO2/PIV for every human account, checked by a daily automated scan.
- Evidence of implementation: the exported policy and its infrastructure-as-code definition, applied to all user groups with no exclusions.
- Evidence of effectiveness: 30 days of sign-in metrics showing only FIDO2/PIV authentications and blocked password-only attempts.
- Verification: the policy covers all in-scope tenants and admin roles, with no drift from the code baseline.
- Validation: the daily scan flags a deliberately non-compliant test account.
- IVV: the assessor samples break-glass and service accounts and attempts a weaker factor directly.
If break-glass accounts are excluded without explanation, the KSI is not demonstrated. Missing or contradictory evidence becomes a traceable issue for Government decision.
First Information Technology Services
Link11/2/2026
AI comparisonLike Stondoh, uses least privilege; includes role configurations, access reviews, measurement logic, and independent testing.
FITS evaluates whether the CSP’s security measures, supported by objective evidence, demonstrate the applicable KSI across the relevant assessment scope. FITS examines both the security capability and the processes used to measure and report its performance.
• Security assertion: CSP’s claim about a security outcome or capability.
• Security measure: practice, mechanism, or activity used to achieve or demonstrate that outcome.
• Evidence of implementation: Configurations, code, or other artifacts that show the measure is in place.
• Evidence of effectiveness: Test results, logs, or historical data that show the measure operates and supports the intended outcome.
• Verification: Confirmation through objective evidence that specified FedRAMP practices have been fulfilled.
• Validation: Confirmation through objective evidence that implemented capabilities and related certification data are suitable for their intended use and support the expected security outcome.
• Independent verification and validation: An independent assessor evaluates the CSP’s measures and evidence, performs or observes testing, and documents its own conclusions.
For automated measures, FITS analysis code, data sources, logic, scope, and results to assess whether the measure operates as described and produces reliable evidence. FITS also examines appropriate manual artifacts and activities where automation is not available or applicable. FITS documents the evidence reviewed, testing performed, assessment limitations, and any deficiencies.
Least privilege (example): A CSP asserts that users have access only to the resources needed for their roles. Its measures include role-based access and periodic access reviews. Role configurations show implementation; completed reviews, access-change records, and exception trends provide evidence of effectiveness. Verification confirms that the specified practices are fulfilled. Validation evaluates whether those practices and their results support the intended least privilege outcome. FITS independently examines the evidence and tests selected access and exceptions prior to documenting our conclusion.
Once Measures have been verified, the KSI/rule is assessed to ensure that all requirements have been met and that all relevant parts of the system are included. Our writeups reflect our process and will notate any deficiency we find during our assessment.
Graham Technologies, LLC
Link11/2/2026
AI comparisonLike Longevity, reconciles sign-in evidence with inventories and bypass paths; adds independently sampled results.
Start with the applicable FedRAMP 20x KSI, rule, boundary and Government acceptance criteria; build a traceable chain from claim to measure, implementation, operation and independent test. A security assertion is the provider's claim of an achieved outcome. A security measure is an observable metric/test of that claim. Implementation evidence proves a mechanism exists and is configured. Effectiveness evidence proves it works over the relevant period and in-scope population. Verification checks the accuracy of configurations, data, calculations and references against specified criteria. Validation assesses whether the evidence actually establishes the intended KSI outcome. Independent verification and validation (IV&V) means an adequately separate assessor challenges or reproduces the tests and conclusions. Example: for privileged MFA, the assertion is that privileged access requires MFA; the measure is the share of in-scope privileged sign-ins subject to MFA. Implementation evidence includes conditional-access policies and privileged-account inventories. Effectiveness evidence includes timestamped sign-in logs, enforcement events and exceptions. Verification reconciles account/sign-in populations to log exports and policy versions. Validation examines bypass paths, break-glass exceptions and scope gaps. IV&V independently samples privileged accounts and reruns permitted queries/tests. Missing logs or unexplained exemptions trigger findings or questions, not automatic acceptance. On USCIS G-CACS III, CCI maps data to 70 automated NIST controls and reduced manual review by approximately 40 hours per assessment. For GSA, subject to approval, deploy/adapt CCI or reproduce its checks on premises in Government-approved systems to flag missing, stale or conflicting evidence. Reviewers adjudicate sufficiency; GSA decides certification and risk acceptance.
11/2/2026
AI comparisonLike Longevity, examines population coverage and authentication bypasses; also discusses architecture and documented testing limitations.
Guidehouse would evaluate each applicable KSI against the offering's architecture, boundary, class, and Government-approved criteria. We would examine whether measures address the intended outcome, cover the relevant population, use reliable data, and operate at an appropriate cadence. Reviewers would inspect evidence and assessor results, evaluate automation limitations, and seek clarification or authorized retesting. A policy statement or passing schema check alone would not demonstrate a security outcome.
Security assertion: the provider's claim about a security capability or outcome.
Security measure: the implemented safeguard or activity intended to produce that outcome, together with the measurement used to demonstrate it.
Evidence of implementation: objective artifacts showing the safeguard is deployed and configured within the claimed scope.
Evidence of effectiveness: operational results showing it works as intended over the relevant period, including failures and exceptions.
Verification: objective confirmation that specified FedRAMP practices have been fulfilled, including whether the selected measures appropriately address the KSI.
Validation: objective confirmation that implemented capabilities and certification data are suitable for their intended use and support expected security outcomes.
Independent verification and validation: those determinations performed by an independent assessor, with methods, evidence, limitations, and conclusions documented; provider self-attestation is not independent assurance.
Illustrative example: For an applicable authentication KSI, the assertion is that privileged access requires phishing-resistant MFA. The measure is enforced MFA, monitored through privileged-account coverage and authentication results. Implementation evidence includes identity-provider configuration, account inventories, and access policies. Effectiveness evidence includes successful protected logins, blocked bypass attempts, exception records, and coverage trends. Verification checks the requirement, account population, and configuration alignment. Validation examines whether actual privileged access is protected, including alternate access paths. Independent assessors examine the evidence and perform or witness authorized tests, documenting gaps and conclusions. The Government retains certification and risk decisions.
International Business Sales And Services Corp (IBSS Corp)
Link11/2/2026
AI comparisonLike Assurit, describes passwordless authentication and a phishing-resistant fallback; includes exceptions and alternate access paths.
IBSS reviewers evaluate each KSI against the applicable FedRAMP 20x rule, acceptance criteria, and evidence requirements. They trace the provider's claim to measurable results and current, relevant evidence; assess completeness, integrity, consistency, and exceptions; and document conclusions and unresolved risks. A KSI is adequately demonstrated when every link from assertion to independent confirmation holds.
Security assertion: the provider's claim that a security outcome is achieved.
Security measure: a defined metric or test used to assess that outcome.
Evidence of implementation: artifacts showing a safeguard is deployed and configured.
Evidence of effectiveness: results showing the safeguard operates and achieves the intended outcome over a relevant period.
Verification: checking that evidence, calculations, and configurations meet specified criteria.
Validation: determining whether the implemented safeguard achieves the intended security outcome in its actual operating context.
Independent verification and validation (IV&V): those checks performed by qualified reviewers sufficiently independent of the work or claim being evaluated.
Example, KSI-IAM-APM (Adopting Passwordless Methods). Assertion: secure passwordless authentication is used where feasible; otherwise, strong passwords and phishing-resistant MFA protect applicable user access. Measure: percentage of in-scope user accounts covered by compliant authentication policies, with documented exceptions. Implementation evidence: dated identity-provider policy exports and authenticator inventories. Effectiveness evidence: authentication logs and test results showing enforcement during the review period, including rejection of prohibited fallback methods. Verification: reconcile accounts, policies, exceptions, logs, and machine-readable KSI data against source evidence and criteria. Validation: test whether the mechanisms provide the intended phishing resistance and whether alternate access paths permit bypass. IV&V: an independent assessor corroborates the evidence through documented sampling, configuration examination, and testing.
Reviewers separate formatting failures from substantive deficiencies and document gaps as traceable questions or findings. The Government retains final KSI disposition and certification authority.
Kapoor IT Consulting LLC (KITC)
Link10/29/2026
AI comparisonLike LDR, combines MFA policy and log evidence with bypass testing; its example includes stolen credentials.
KITC determines whether a provider has demonstrated a Key Security Indicator (KSI) by evaluating whether current, traceable technical evidence substantiates the claimed security outcome across the system boundary. Reviewers examine configurations, telemetry, and test results against applicable FedRAMP 20x criteria to assess implementation and operational effectiveness.
Key Distinctions:
•Security Assertion: Provider's claim that a security outcome is achieved.
•Security Measure: Control, mechanism, or policy intended to achieve that outcome.
•Evidence of Implementation: Artifacts showing the measure is deployed and configured.
•Evidence of Effectiveness: Operational records demonstrating the measure works over time.
•Verification: Confirms the measure meets defined technical specifications ("built correctly").
•Validation: Confirms the measure achieves its intended security outcome ("built the right thing").
•Independent Verification and Validation (IV&V): Objective verification and validation by assessors independent of the measure's implementation and operation.
Example: Phishing-Resistant MFA for Privileged Access
•Assertion: Provider claims phishing-resistant MFA protects all privileged access.
•Measure: Identity provider policies enforce FIDO2/WebAuthn authentication for privileged roles.
•Implementation Evidence: Policy exports and infrastructure-as-code configurations demonstrate enforcement.
•Effectiveness Evidence: Authentication logs show consistent MFA enforcement, with exceptions investigated.
•Verification: Reviewers inspect policies, role assignments, and test results against technical requirements.
•Validation: Security testing confirms stolen credentials alone cannot bypass privileged authentication.
•IV&V: Independent assessors corroborate configurations, logs, and test results to evaluate the claimed outcome.
LDR Security Solutions, LLC
Link11/2/2026
AI comparisonLike KITC, uses MFA policies, SIEM records, and assessor bypass tests; also includes policy benchmarking.
LDR determines whether a provider has adequately demonstrated a Key Security Indicator (KSI) by evaluating objective evidence against FedRAMP Consolidated Rules 2026 (CR26) and NIST SP 800-53 standards, ensuring safeguards operate as specified and produce verifiable telemetry. To evaluate a KSI, LDR establishes clear distinctions between provider claims, technical configurations, and continuous operational proof.
The evaluation begins with a Security Assertion, a formal claim that a control requirement is met. The provider then enacts a Security Measure, representing the deployed technical mechanism. LDR validates this through two proof tiers: Evidence of Implementation (static configuration artifacts proving deployment) and Evidence of Effectiveness (dynamic telemetry demonstrating correct operation under production workloads).
Assessment proceeds through technical phases. The provider conducts internal Verification via automated testing to confirm configurations match engineering specs. Reviewers perform Validation, analyzing implementation against compliance standards to ensure risk mitigation. Finally, Independent Verification and Validation (IV&V) is conducted by an unbiased third party to corroborate structural implementation and operational defense.
For example, in an IAM Federation scenario with Enforced Multi-Factor Authentication (MFA), a provider asserts that administrative access enforces phishing-resistant MFA via SAML. The security measure is an identity provider integrated with FIDO2 WebAuthn authenticators. Evidence of Implementation includes JSON policies proving WebAuthn enforcement across admin roles, while Evidence of Effectiveness includes SIEM logs proving 100 percent of administrative sessions completed FIDO2 challenges. The provider performs Verification via CI/CD tests confirming unauthorized attempts fail. Reviewers perform Validation by benchmarking policies against NIST SP 800-63B AAL3 guidelines, and IV&V is finalized when an accredited 3PAO executes token bypass and penetration testing.
This approach reflects LDR delivery on federal contracts, including automated telemetry ingestion into Xacta 360 at the Department of the Interior (DOI) and automated artifact validation models supporting the National Cancer Institute (NCI) Fast Authority to Operate (FAST ATO) initiative.
Life Cycle Engineering, Inc.
Link10/26/2026
AI comparisonLike KITC, discusses MFA and examination, interviews, and testing; organizes its response around definitions rather than one extended scenario.
Our personnel use an evidence-based assessment process to determine whether a provider has adequately demonstrated a Key Security Indicator (KSI). A KSI is not satisfied by a provider’s statement alone; it must be supported by objective evidence showing the control is implemented and operating effectively.
• Security Assertion: A provider’s claim that a security capability exists (e.g., MFA is enabled) that complies with the FedRAMP requirements.
• Security Measure: The policy, process, technology, or control implemented to satisfy the requirement.
• Evidence of Implementation: Artifacts proving the measure is deployed, such as policies, configurations, architecture diagrams, screenshots, or system settings.
• Evidence of Effectiveness: Artifacts proving the measure works as intended, including logs, monitoring data, test results, vulnerability scans, incident records, or performance metrics.
• Verification: Confirmation that the required control exists and that supporting evidence is authentic, complete, and aligned with the KSI.
• Validation: Determination that the implemented control achieves the intended security outcome and reduces risk within the operational environment.
• IV&V: Verification and validation performed by individuals independent of the provider and implementation team to ensure an objective assessment.
To satisfy a KSI, the provider must demonstrate a clear chain from assertion to measure, implementation evidence, effectiveness evidence, verification, and validation. Our reviewers would evaluate documentation, interview personnel, examine technical evidence, observe system operations, and perform sampling or testing as needed. A KSI would only be considered adequately demonstrated when objective evidence confirms the control is implemented, operating effectively, and achieving its intended security purpose. Assertions without supporting evidence would not be considered sufficient.
11/2/2026
AI comparisonLike Guidehouse, examines privileged-account coverage and alternate access paths; distinguishes schema checks from evidence of security outcomes.
Longevity will evaluate each Key Security Indicator (KSI) against the applicable FedRAMP 20x rule, system boundary, and Security Decision Record (SDR). Reviewers will trace the provider's claim through its measure, source data, tests, historical results, and exceptions. A schema-valid submission does not establish that a security outcome has been achieved.
Security assertion: The CSP's claim that an outcome is met.
Security measure: The defined configuration, process, test, or metric used to demonstrate that outcome, including scope and frequency.
Implementation evidence: Proof that the measure is deployed in the actual environment, such as configuration exports and system inventories.
Effectiveness evidence: Operational results showing the measure works, such as logs, tests, and exception trends over time.
Verification: Determining whether the selected measure and automation are suitable and sufficient to demonstrate the KSI.
Validation: Checking that the measure and underlying data are accurate and operate as described.
Independent verification and validation (IV&V): Separately conducted assessment of the design, evidence, and results, including reproduction or direct testing where appropriate.
Example—privileged multifactor authentication (MFA): A CSP asserts that privileged access requires MFA; defines a measure covering privileged identities and access paths; provides identity-provider settings and inventories as implementation evidence; and supplies sign-in logs and exception trends as effectiveness evidence. Reviewers verify that the measure covers administrators, alternate access paths, and relevant accounts; validate settings against sampled events; and examine independent 3PAO testing. An omitted bypass path, unaccounted privileged identity, or inconsistent log produces a documented question or finding, not an assumed pass.
Senior reviewers resolve conflicting evidence and record the KSI conclusion, cited artifacts, limitations, and escalation; GSA makes the final disposition.
11/2/2026
AI comparisonLike CybertLabs, uses privileged sign-in metrics, policy exports, and log sampling; includes API/service keys in its example’s scope.
We would judge a KSI against the provider's Security Decision Record entry for it (SDR-CSX-KSI): the measures and their objectives, the cycle for persistent measures, verification, automation accuracy, and validation. A KSI is demonstrated only when each of those is present, current and supported by evidence within the stated boundary.
The distinctions:
Security assertion: the provider's claim about a capability.
Security measure: the defined criterion, measurable where possible, that shows the claim is true.
Evidence of implementation: artifacts showing the capability is configured and in place.
Evidence of effectiveness: data showing it operates as intended over time, including exceptions.
Verification: confirming the implementation and measures fit the rule or KSI as claimed.
Validation: confirming the measures are accurately produced and the capability works as intended in this system, with full coverage.
Independent verification and validation: the same checks performed by a party independent of the provider, with its own sampling or testing.
Example, phishing-resistant MFA for privileged access:
Assertion: "All privileged access requires phishing-resistant MFA."
Measure: percentage of privileged sign-ins over 30 days using FIDO2 or PIV, target 100 percent.
Implementation evidence: identity provider policy export requiring those authenticators for privileged roles.
Effectiveness evidence: authentication logs for the period showing compliant sign-ins and how exceptions were handled.
Verification: the policy and logs match the assertion and the measure's definition.
Validation: the measure covers every privileged path, including break-glass accounts, API keys and console access; if service keys bypass MFA, the measure is incomplete even if the logs show 100 percent.
IV&V: an independent reviewer pulls its own log sample and tests a privileged path directly.
Our reviewers would document each step in the evidence traceability record, distinguish missing evidence from failed evidence, and leave acceptance of the KSI to the Government.
11/2/2026
AI comparisonUses GitLab activity and dashboard testing for an investment-review example, while WITS uses inventory and logging coverage.
Reviewers follow this process for KSI review:
1. Examine the Security Decision Record (SDR)
a. Review Implementation Status and Statement
b. If N/A*, go to step 2
c. Review Validation Statements, Tests and Evidence
d. Review Assessment Statements
2. Identify questions or concerns. Gather Provider responses
3. Identify agency-specific security risk impacts and recommendations
*1c and 1d do not apply if KSI status is Not Implemented & not relevant to the Provider’s environment
In our example, Provider (P) is pursuing a Class B certification.
If P states the Implementation Status is Implemented, we ensure P translates the security outcome represented in the KSI to their environment. I.e., KSI-PIY-RIS states "The effectiveness of the provider's investments in achieving security goals is persistently reviewed." P describes a critical security investment is in their people (a security measure) and several related indicators. We will focus on one indicator: the ISSM's sustained engagement on their work management system indicates that security investments are achieving P’s security goals. If the ISSM is absent from GitLab for more than three days, it signals a potential gap.
To monitor this gap, P describes an automated verification & validation they perform: A daily script analyzes the ISSM’s GitLab login data. If the three-day inactivity threshold is exceeded, the script adds a trust center record. The dashboard displays a year of data.
P’s description is just a security assertion without evidence & independent verification & validation (IV&V). The Reviewer locates evidence of implementation: the automated script’s code and the link to the dashboard included in the SDR. However, for evidence of effectiveness, these are not sufficient. The Reviewer looks for this in the FedRAMP recognized Independent Assessor’s (IA) IV&V report included in the SDR. The IA outlines their validation steps & results. The IA verifies that the script & dashboard are operating as expected through code review and testing. The IA’s tests include triggering various error conditions that could yield false positives/negatives. The IA’s test results indicate that P’s automated validation is operating as intended and producing accurate results. The IA states that the dashboard displays no exceeded thresholds. The Reviewer confirms this with the IA-provided dashboard link.
11/2/2026
AI comparisonLike CybertLabs, examines federated and local identities; compares account repositories, telemetry queries, and assessor results.
KSIs measure the current state of core security principles as they operate in a CSP’s environment. The KSI assertion is based on the CSP’s description of its implementation. To understand the security measure, reviewers must examine the specific telemetry being queried and compare it to FedRAMP’s KSI description. This also requires an understanding of the technical implementation and a review of the architecture, minimum assessment scope, and related KSIs. After determining whether the telemetry is correct, reviewers should examine the deterministic information to see how effectively the CSP is managing the specific KSIs. This should identify the expected condition, the observed condition, and all deltas. Examination of the original code, script, or configuration source will show how the KSI is validated. The two verifications presented by CSPs should show how the data is being pulled and what is measured, including sources and outcomes. These verifications should match the architecture, design of the KSI, sources, and the condition, configuration item, and log data identified in previous steps. Finally, the 3PAO’s IV&V should include this review and an analysis of each KSI, along with an opinion on its “pass/fail” status.
As a simple example, a review of account-based KSIs would include identifying each source account repository through the SDR, architecture documentation, and any external or internal services that could have accounts. The CSP’s implementation description should identify and enumerate all sources, federated identity systems, and local accounts. The verification methods should be examined, including all queries to the federated identity management solutions, to ensure that all accounts and settings applicable to the KSI are included. All external and internal identity sources should also be present in the verification, showing integration with the federated identity provider. For repositories that are not integrated, the individual accounts and their associated configurations should be present in the verification request. Finally, the 3PAO report for the account-based KSI should be examined to confirm that the information in the JSON/trust center is accurate and that the implementation operates as described in the SDR and KSI descriptions.
Paragon Technology Group, Inc.
Link11/2/2026
AI comparisonLike Guidehouse, uses privileged MFA and alternate paths; describes additional senior testing when evidence conflicts.
To determine whether a cloud service provider has satisfied a Key Security Indicator (KSI), Paragon's reviewers examine what the provider claims, how it protects the system, and whether the technical evidence supports that claim. Documentation alone does not establish compliance. Reviewers check configurations, test results, logs, and other evidence against the KSI's required security outcome.
Consider a provider that asserts all privileged accounts require multifactor authentication (MFA). The assertion describes the claimed protection, while the security measure is the identity management policy that enforces MFA. Configuration records provide evidence of implementation by showing that the provider enabled the policy and applied it to administrator accounts. Authentication logs and test results provide evidence of effectiveness by showing whether the policy actually blocks access without the additional factor.
Verification confirms that the MFA policy meets its technical requirements, including account coverage, enforcement settings, and exceptions. Validation goes further by determining whether those settings achieve the intended security outcome. For example, reviewers examine alternate authentication paths to determine whether an administrator can bypass MFA.
Independent verification and validation (IV&V) requires reviewers who did not design or implement the security measure to examine the evidence, independently test the provider's conclusions, and document discrepancies. When evidence conflicts or exceptions introduce security risks, senior cloud security engineers assess the findings and determine whether additional testing is necessary.
Paragon documents the evidence reviewed, unresolved questions, and technical findings for Government consideration. The Government retains responsibility for final security and authorization decisions.
Prudent Technology LLC
Link11/2/2026
AI comparisonLike Assurit, uses phishing-resistant authentication, historical logs, samples, and independent testing.
Our reviewers treat a KSI as adequately demonstrated only when each indicator, applied across the full minimum assessment scope, has a Security Decision Record entry with an implementation statement, accurately produced measures, current objective evidence such as deterministic telemetry, a repeatable validation method automated where feasible, and independent assessment results with provider responses. JSON and human-readable entries must agree, and Class B and C packages must show metrics over time. A Package Reviewer drafts each determination and a Senior Engineer confirms it, the same discipline we apply in our DCSA independent test and evaluation work and federal courts IV&V testing. We separate seven terms, aligned to FedRAMP’s 2026 definitions. A security assertion is the provider’s claim about what it does. A security measure is the specific, measurable condition it tracks to support that claim. Evidence of implementation shows the capability is configured and in place now. Evidence of effectiveness shows it achieves the intended outcome over time. Verification is confirmation through objective evidence that the specified FedRAMP Practices are fulfilled. Validation is confirmation through objective evidence that the capability and its certification data are suitable for their intended use and support the expected security outcome. Independent verification and validation is both, performed by a FedRAMP Recognized independent assessment service or FedRAMP, at least annually for Class B and above. Take phishing-resistant MFA. The assertion: all users, including administrators, sign in with phishing-resistant MFA. The measure: the percentage of in-scope accounts and sign-ins using FIDO2 or PIV. Implementation evidence: an identity provider policy export requiring those factors for every in-scope application, with no SMS or OTP fallback. Effectiveness evidence: 90 days of sign-in logs showing 100% phishing-resistant authentication and blocked legacy attempts. Verification: the record and configuration show the KSI’s requirements are met for every account. Validation: metrics over time show the outcome holds, including for break-glass accounts. IV&V: the assessor tests a documented representative sample and attempts a legacy-factor sign-in. Unexplained break-glass exclusions raise a question; logs that contradict the claim produce a finding.
11/2/2026
AI comparisonLike TES, examines authentication coverage and assessor work; discusses how successful-login percentages relate to the account population.
We evaluate each KSI against its scope and evidence requirements. SDR-CSX-KSI requires summaries of measures/objectives, persistent cycles where applicable, verification of KSI coverage, verification of automation accuracy/sufficiency or why it is unnecessary, and validation of accurate production and operation. Missing measures require an explanation of the reason and customer risk.
Distinctions:
- Assertion: the provider's claim, not proof.
- Measure: a repeatable method with a defined objective, scope, and cycle.
- Implementation evidence (IVV-CSO-SEI): proof the documented measure is deployed/configured.
- Effectiveness evidence (IVV-CSO-SEE): proof the measure achieves its intended outcome.
- Verification (FRD-VRF): objective evidence that specified FedRAMP Practices are fulfilled.
- Validation (FRD-VLN): objective evidence that capabilities and certification data suit their intended FedRAMP use and support expected security outcomes.
- Independent V&V (IVV-IAS-VIM/VEF): independent examination of actual measures and effectiveness, where required; PMO reviewers evaluate that work and seek further testing through Government direction.
Example, KSI-IAM-APM: secure passwordless authentication/authorization where feasible, otherwise strong passwords with phishing-resistant MFA.
- Assertion: all applicable users follow that approach.
- Measure: an illustrative daily reconciliation of identities, policies, and authentication methods, including privileged/emergency accounts, federation, and recovery paths.
- Implementation: deployed identity policies, configurations, and enrollment records.
- Effectiveness: operating results, exceptions, collection failures, and metric history under SDR-CSX-KMT.
- Verification: inspect deployed settings and measure logic for complete coverage.
- Validation: review provider test results, including blocked disallowed sign-ins, and reproduce reported metrics.
- Independent V&V: review assessor methods, samples, evidence, and results.
Successful sign-in percentages alone do not establish coverage. SMS fallback contradicts an all-phishing-resistant claim; record scope and risk for disposition. Unexplained gaps do not pass.
We propose approved NISTcompliance.ai support to organize evidence and flag contradictions. Reviewers confirm findings; automated scores do not establish KSI sufficiency.
RADIX International Consulting LLC
Link11/2/2026
AI comparisonLike Cloud9, uses deliberately noncompliant sign-in tests; also reconciles identity inventories with historical logs.
A KSI is adequately demonstrated only when a defined measure, current evidence covering the full boundary, and verified and validated results all support the provider's claim. Our reviewers separate seven elements:
- Security assertion: the provider's claim that an outcome is achieved.
- Security measure: the defined, observable test or metric showing whether the outcome holds (what, how, how often, target).
- Evidence of implementation: artifacts proving the capability is configured and deployed as described.
- Evidence of effectiveness: data over time showing it works as intended in operation.
- Verification: reviewer confirms the evidence matches the stated requirement and measure (built as specified).
- Validation: reviewer confirms the outcome is actually achieved in the operating context, with no gaps or bypasses (right result).
- Independent verification and validation: the above performed or re-performed by a party independent of the provider and its implementers (e.g., the independent assessor), with results the Government can rely on.
Example (phishing-resistant MFA):
- Assertion: all users authenticate with phishing-resistant MFA.
- Measure: 100% of interactive sign-ins (users, admins, break-glass) use FIDO2/PIV, checked continuously.
- Implementation: machine-readable IdP policy export requiring FIDO2/PIV, legacy factors and protocols disabled, no exempt groups.
- Effectiveness: 90 days of authentication logs showing 100% compliant successful sign-ins and blocked SMS/OTP attempts.
- Verification: policy settings match the measure and apply to every user population in the identity inventory.
- Validation: sample admin and break-glass accounts; reconcile log population to the inventory; confirm no legacy-protocol or service-account bypass.
- IV&V: the assessor re-performs a non-compliant sign-in test in the production boundary and attests the result.
If any link is missing, stale or does not cover the boundary, we raise a question or finding rather than accept the assertion.
10/27/2026
AI comparisonLike TES, describes accounts outside the main sign-in path; its example focuses on break-glass accounts omitted from SSO measurements.
A KSI is adequately demonstrated when a specific assertion is backed by measures that cover the full assessment scope, implementation and effectiveness evidence support those measures, the provider has verified and validated them, and an independent assessor has repeated both against evidence it obtained itself. Missing any link produces a question or finding.
Distinctions:
- Security assertion: the provider's claim that an outcome is achieved. It is a starting point, not evidence.
- Security measure: a defined, repeatable measurement with an objective and a cycle (e.g., daily) that shows whether the outcome holds.
- Evidence of implementation: shows the capability exists and is configured as described.
- Evidence of effectiveness: shows the capability produces the intended outcome over time.
- Verification: confirmation that the measure is the right one, i.e., that it actually demonstrates the KSI, covers the scope, and that its automation is accurate.
- Validation: confirmation that the capability is in place and working as intended, and that measure results are produced accurately.
- Independent verification and validation: both performed by a party independent of the provider, using evidence it gathers or tests directly rather than the provider's dashboards alone.
Example (phishing-resistant MFA, KSI-IAM):
- Assertion: all human access uses phishing-resistant MFA.
- Measure: daily percentage of in-scope human identities whose policy requires FIDO2/PIV; target 100%, exceptions tracked.
- Implementation: exported identity-provider policy showing FIDO2 required and OTP/SMS disabled.
- Effectiveness: 90 days of authentication logs showing every successful human login used FIDO2, with OTP attempts denied.
- Verification: the reviewer finds the measure counts only SSO users and omits cloud-console break-glass accounts, so it does not fully demonstrate the KSI. Question issued.
- Validation: identity inventory reconciled to the measure's denominator; a test login with OTP is rejected.
- IV&V: the assessor pulls the inventory and logs directly and repeats the reconciliation and test.
The reviewer records each element, its evidence link, and the gap, so the Government sees why the KSI is or is not demonstrated.
Softthink Solutions Inc
Link10/29/2026
AI comparisonLike EY, uses account-lifecycle records and access removal, including human, service, and privileged accounts.
STSI evaluates each KSI against the applicable rule, boundary, and claimed outcome. A security assertion states what the provider claims. A security measure is the mechanism or process used to achieve and demonstrate that outcome. Implementation evidence shows the measure exists; effectiveness evidence shows it produces intended results over time. Verification checks whether the measure demonstrates the KSI and its automation is accurate and sufficient. Validation tests whether the measure is accurately produced and works as intended. Independent verification and validation add an independent assessor's evaluation and testing.
Example: A provider asserts that automation securely manages account lifecycles. Its measure reconciles personnel events with cloud accounts. Workflow settings show implementation; dated logs, termination samples, and exception closures show effectiveness. We verify coverage of human, service, and privileged accounts and measurement accuracy, then validate event processing and access removal using authorized tests or test evidence. We examine the independent assessor's scope and results. Missing coverage or failed tests trigger findings for GSA disposition.
Stondoh Secure Digital Solutions
Link11/2/2026
AI comparisonLike FITS, uses least privilege; examines inherited permissions and denied privilege-escalation attempts.
Stondoh recommends an evidence-driven, risk-based approach to evaluating FedRAMP 20x Key Security Indicators (KSIs). Our personnel would assess whether a provider's security claims are supported by objective, current, and independently verifiable operational evidence, rather than relying solely on documentation or self-attestation.
We distinguish seven levels of assurance:
1. Security Assertion: A provider's claim that a security requirement is satisfied.
2. Security Measure: The safeguard or mechanism intended to achieve the security outcome.
3. Evidence of Implementation: Configuration records, policies, or system artifacts demonstrating that the safeguard is deployed.
4. Evidence of Effectiveness: Operational results demonstrating that the safeguard achieves its intended outcome.
5. Verification: Objective confirmation that implementation and results satisfy defined KSI criteria.
6. Validation: Assessment of whether the implemented safeguard achieves the intended security outcome in its operational context.
7. Independent Verification and Validation (IV&V): Evaluation by qualified personnel independent of the implementation team, using corroborating evidence and repeatable testing.
Example: Least Privilege (IAM)
Assertion: "Administrative access is restricted."
Measure: Role-based access controls and least privilege policies.
Implementation: IAM policies, role assignments, and configuration exports.
Effectiveness: Access logs and test results demonstrating unauthorized privilege escalation attempts are denied.
Verification: Engineers compare configurations and test results against defined KSI acceptance criteria.
Validation: Engineers assess whether effective permissions, inherited privileges, and operational workflows prevent unauthorized administrative access.
IV&V: Independent reviewers reproduce access tests, examine cloud-native logs, and corroborate results without relying solely on provider assertions.
Stondoh would document evidence sources, review results, deficiencies, and residual risks. A KSI is adequately demonstrated when sufficient, relevant, and reproducible evidence supports the required security outcome within the defined system boundary.
The Enterprise Security Consultants, LLC (dba TES Consultants)
Link10/30/2026
AI comparisonLike Secured IT Solutions, examines access outside the main identity provider; uses Okta and direct AWS accounts.
Reviewers recommend a Key Security Indicator (KSI) as demonstrated only when every element below is supported:
Security assertion: the provider's claim that an outcome is achieved; a starting point, not evidence.
Security measure: the specific mechanism or process the provider uses to achieve the outcome, with its objective and run cycle.
Evidence of implementation: proof the measure is in place as documented (configuration, policy, code).
Evidence of effectiveness: proof the implemented measure produces the intended outcome over time (metrics, logs, test results).
Verification: the activity that produces evidence of implementation - confirming the measure exists and is configured as stated.
Validation: the activity that produces evidence of effectiveness - confirming the measure works as intended and its output is accurately produced.
Independent verification and validation (IVV): verification and validation by a FedRAMP Recognized independent assessor or FedRAMP, included in the package without inappropriate modification.
Reviewers do not re-perform IVV. They check that measures and assessor testing cover the full Minimum Assessment Scope for the KSI, that automation is accurate and sufficient, that evidence is current for its cycle, and that provider and IVV results agree.
Example, KSI-IAM-APM: the scope includes Okta SSO into AWS plus direct AWS IAM users:
Assertion: "All users use phishing-resistant MFA."
Measures: daily Okta check that sign-on policy requires FIDO2/PIV; daily AWS check that IAM users have MFA.
Implementation evidence: Okta policy export; IAM credential report.
Effectiveness evidence: 30 days of Okta and CloudTrail sign-ins by method.
Verification (provider): both configurations match the documented measures.
Validation (provider): logs show enforcement and match check output; a non-phishing-resistant test sign-in was denied.
IVV (assessor): samples users and repeats the denial test.
Both checks pass, yet the KSI is not demonstrated: the AWS check accepts TOTP, which is not phishing-resistant; IAM users sit outside Okta deprovisioning (KSI-IAM-AAM); workload keys are non-user credentials (KSI-IAM-SNU). Two passing validations are not coverage. Reviewers map every in-scope information resource to a KSI validation or justified exception, and attribute each gap to provider, assessor, or both.
10/31/2026
AI comparisonUses a patching pipeline, while CMIC uses vulnerability remediation; both compare implementation records with operational results.
A KSI is adequately demonstrated when evidence supports the claimed security outcome across the applicable boundary and review period. We examine the current rule, measure, collection method, coverage, results, and exceptions before recommending a disposition.
A security assertion states the claimed outcome. A security measure is the safeguard used to achieve it. Implementation evidence shows that the measure is deployed. Effectiveness evidence shows whether it achieves the intended security result.
Verification uses objective evidence to confirm that specified practices are fulfilled. Validation establishes that the capability and data suit their intended use and support expected security outcomes. Independent verification and validation require a recognized assessor, separate from implementation, to examine the methods, evidence, and conclusions.
Vertekal's delivered security automation on a large Intelligence Community program illustrates these distinctions. We deployed GitLab orchestration and Ansible playbooks across more than 1,000 RHEL hosts. The assertion was consistent security patching; the measure was centralized, repeatable patching and remediation. The deployed pipeline, remediation playbooks, and automated host-data collection established implementation.
Our delivery process verified changes in the target environment, checked applicable security requirements and adjacent functionality, and updated configuration records. Validation confirmed acceptance criteria with the customer before closure. An operational dashboard correlated security findings with remediation actions and tracked completion and trends. The automation reduced risk-to-resolution cycles from days to hours and manual patching labor by over 80 percent. Labor savings establish efficiency; findings and remediation records support security-effectiveness judgments.
These are delivered RMF engineering activities. Customer acceptance and peer review are distinct from independent verification and validation. For a KSI determination, independent assessment results must substantiate the required independent work. Unresolved coverage gaps, contradictory results, or insufficient effectiveness evidence become questions or findings for Government disposition.
11/2/2026
AI comparisonLike TES, describes a reported passing result alongside a coverage gap; compares 400 inventoried assets with 360 log sources.
Reviewers would start with the current KSI text and class rules, then the Security Decision Record (SDR) entry, machine-readable metrics, and independent assessment results. They would confirm scope, test whether the measures actually demonstrate the outcome, inspect evidence and cycle history, check that automation is accurate, and tie each question or finding to the rule and the evidence. A passing validation status alone never settles adequacy, and the Government makes the final determination.
Security assertion: the provider's claim that an outcome is met. It proves nothing by itself.
Security measure: the specific mechanism or activity, with an objective and cycle, that demonstrates the KSI.
Evidence of implementation: objective artifacts showing the documented measure exists as described.
Evidence of effectiveness: objective results showing the measure produces the intended outcome over time.
Verification: the provider's confirmation through objective evidence that FedRAMP practices are fulfilled and documented measures are implemented.
Validation: the provider's confirmation through objective evidence that implemented capabilities and related data are suitable and work as intended.
Independent verification and validation: the same confirmations performed by a FedRAMP Recognized assessment service, with results carried into the Certification Package without inappropriate modification.
Example, KSI-MLA-OSM (centralized, tamper-resistant logging):
Assertion: "All in-scope events reach our SIEM and cannot be altered."
Measure: a daily automated job compares the asset inventory with active log sources and checks immutable storage settings.
Implementation evidence: SIEM configuration, storage policy, and a log source list.
Effectiveness evidence: job history, a seeded event that reached the SIEM, a blocked deletion attempt, and review tickets.
Verification: the provider confirms that the configuration matches the SDR.
Validation: the provider confirms that a new host begins logging and that deletion fails.
IV&V: a Recognized assessor samples assets and repeats the deletion test.
Reviewer result: if the inventory lists 400 assets and logs cover 360, our reviewer raises a finding even when the job status shows green.