# AI Usage, Spend & Value (VAL) Requirements — 9 Workforce AI Security Controls > Measure adoption, spend and business value so AI investment decisions are evidence-led. 9 vendor evaluation requirements with acceptance criteria, verification tests and framework mappings. Source: Harmonic Security, updated October 2026. 9 requirements. Disclaimer: Mappings indicate relevant contributions, not complete compliance, certification, assurance, a conformity assessment or legal advice. Read each explanation and its scope conditions. Legal applicability depends on jurisdiction, role, use and effective dates. Reference summaries are selective; consult current official sources and full licensed standards before relying on them. ## SPM-008: Distinguish personal, free and guest accounts from sanctioned enterprise tenants - Area: AI Security Posture Management - Verification: Live test - OWASP adoption tier: AT0, AT1 - Formerly: DIS-006 - URL: /r/SPM-008 **Acceptance criteria:** Report a reliable account-type split at the point of use and allow policy to vary depending on account plan. **Why it matters:** Contractual protections attach to the enterprise tenant, not the domain. A personal account reaches the same URL with none of them. **How to verify:** Enterprise, personal and unauthenticated use of the same tool are each identified and handled per policy. **OWASP adoption context:** Personal-account and vendor-assistant contexts make account ownership and plan distinctions important; tier alone does not establish contractual safeguards. **Mappings:** - NIST AI RMF: MAP 4.1 — The account-plan distinction helps identify the third-party service context and supplier terms needing risk review. A plan label alone does not establish the applicable relationship or complete its assessment. - SOC 2: CC6.7, CC9.2; ISO 27001: A.8.3, A.5.23 — Reliable account-tier context can inform permitted data destinations, access restrictions and enterprise-cloud or supplier rules. The policy linkage must work in practice; classification alone does not enforce those rules. ISO/IEC 27001: Account identification does not manage the identity lifecycle. - NIST CSF 2.0: DE.CM-03 — The observed personal, free, guest or enterprise account context supports monitoring employee technology use. An account-plan label does not manage identities or credentials or enforce access. ## IDR-003: Identify use cases leading to elevated risk behavior. - Area: AI Detection & Response - Verification: Proof of value - OWASP adoption tier: AT0–AT4 - Formerly: VAL-005 - URL: /r/IDR-003 **Acceptance criteria:** Surface the use cases and teams that require additional training on safe usage principles. **Why it matters:** Repeat exposure and under-use point to where risk reduction or enablement will pay off. **How to verify:** High-risk use cases and the associated users are identified in a pilot. **OWASP adoption context:** Risky use and repeat exposure patterns can appear across the listed employee AI settings; low use is not itself proof of risk or failure. **Mappings:** - NIST CSF 2.0: DE.CM-03; NIST AI RMF: MEASURE 3.1; SOC 2: CC7.2; ISO 27001: Cl. 9.1, A.8.16 — Team-level risky-use and recurring-exposure patterns provide findings for usage monitoring, AI-risk tracking and evaluation against responsible-use/security objectives. Under-use alone is an enablement signal rather than a security anomaly; assessment and intervention remain necessary beyond surfacing patterns. ISO/IEC 27001: Confirm the need for monitoring and choose the interventions to apply. - ISO 42001: A.6.2.6 — Observed risky-use and recurring-exposure patterns provide ongoing operational-monitoring findings for in-scope AI systems or controls. Under-use alone is an enablement signal; surfacing patterns does not establish responsible-use objectives or complete assessment and intervention. ## VAL-001: Measure AI usage and adoption by tool, team, function and workflow - Area: AI Usage, Spend & Value - Verification: Proof of value - OWASP adoption tier: AT0–AT4 - URL: /r/VAL-001 **Acceptance criteria:** Report volumes, active users, trends and the sanctioned/unsanctioned split at privacy-appropriate aggregation. **Why it matters:** Usage is the denominator for every cost, risk and value figure. **How to verify:** Usage by tool, team and function from pilot data, at privacy-appropriate aggregation. **OWASP adoption context:** Adoption reporting spans the listed employee AI contexts so sanctioned usage does not hide shadow or agent-assisted activity; privacy limits still govern the telemetry. **Mappings:** - NIST CSF 2.0: DE.CM-03; SOC 2: CC7.2; ISO 27001: Cl. 9.1, A.5.36 — Workforce usage and the sanctioned/unsanctioned split provide technology-monitoring context and inputs to security-performance and acceptable-use review. Adoption volumes and active-user counts alone are business analytics; security conclusions need relevant analysis and follow-up. - ISO 42001: Cl. 9.1 — The sanctioned and unsanctioned usage split provides policy-performance evidence when included in AI-management-system evaluation. Define the relevant objectives and evaluation method; pure activity volumes do not establish responsible-use objectives or effectiveness. ## VAL-002: Classify AI activity into business-relevant use cases - Area: AI Usage, Spend & Value - Verification: Proof of value - OWASP adoption tier: Tier-independent - URL: /r/VAL-002 **Acceptance criteria:** Turn raw telemetry into recognizable tasks, workflows and functions. **Why it matters:** Tool-level data cannot tell a team drafting contracts from one summarizing public research. **How to verify:** Top use cases by function from pilot data, with personal conversations excluded. **OWASP adoption context:** Business-use classification can describe activity from any adoption tier; a deployment pattern alone does not identify the business purpose. **Mappings:** - NIST AI RMF: MAP 1.1; ISO 42001: A.9.4 — Recognizable tasks and workflows provide context for documenting intended purposes and beneficial uses, and allow actual activity to be compared with intended use. Observed activity does not itself determine that purpose or demonstrate conformity with it. ## VAL-003: Measure spend, waste and portfolio decisions - Area: AI Usage, Spend & Value - Verification: Proof of value + Walkthrough - OWASP adoption tier: Tier-independent - URL: /r/VAL-003 **Acceptance criteria:** Report licenses, tokens, provider cost, model efficiency, redundant tools and cost per task or outcome, and produce the evidence behind a decision to scale, pause, optimize or retire a tool. **Why it matters:** License waste and duplicate tools are often the fastest way to fund the control. **How to verify:** Licensed versus active use for one enterprise AI tool, and the cost method explained. **OWASP adoption context:** Portfolio cost, overlap and retirement decisions can compare AI services across adoption tiers rather than treating a tier as a measure of value. **Mappings:** - NIST AI RMF: GOVERN 1.7 — Cost and outcome evidence can inform a decision to retire an AI tool. The relationship is an input to decommissioning decisions; financial optimization does not establish safe retirement or treatment of residual risks. - ISO 42001: A.4.5 — Token use and model efficiency provide resource-consumption information for identified in-scope AI services. Cost or ROI alone is insufficient, and these metrics establish neither capacity adequacy nor responsible-AI supplier alignment. ## VAL-004: Measure productivity and business-value signals - Area: AI Usage, Spend & Value - Verification: Proof of value - OWASP adoption tier: Tier-independent - URL: /r/VAL-004 **Acceptance criteria:** Identify time saved, throughput, completion and quality indicators with stated assumptions. **Why it matters:** Risk without value is a brake. Value without risk is a blind spot. **How to verify:** Value indicators for pilot functions, shown with their assumptions. **OWASP adoption context:** Productivity and value evidence can be assessed across adoption tiers; the workflow, baseline and assumptions determine meaningful comparisons. **Mappings:** - NIST AI RMF: MAP 3.1, MEASURE 4.3 — Time saved, throughput and quality indicators with stated assumptions inform benefit assessment and context-relevant AI performance evaluation against chosen responsible-use objectives. Their meaning and validity need evaluation; reporting business-value metrics alone establishes neither realized benefit nor security effectiveness. ## VAL-005: Generate targeted training and enablement recommendations - Area: AI Usage, Spend & Value - Verification: Proof of value - URL: /r/VAL-005 **Acceptance criteria:** Turn observed usage and detection telemetry into prioritized interventions, templates, coaching and sanctioned-tool adoption, aimed at the teams and behaviors that actually generate risk, and measure whether behavior changes. **Why it matters:** Training aimed at the teams and behaviors that actually create risk works better than blanket training. **How to verify:** Prioritized enablement recommendations from pilot data, and a measure of whether behavior changed. **OWASP adoption context:** Training recommendations should reflect observed needs across the listed employee AI contexts instead of assuming that adoption tier determines competence. **Mappings:** - NIST CSF 2.0: PR.AT-01, PR.AT-02; NIST AI RMF: GOVERN 2.2; ISO 42001: Cl. 7.2, Cl. 7.3; SOC 2: CC1.4, CC2.2, CC4.1 — Usage and detection telemetry can target AI/security training and coaching at relevant teams and roles, while behavior changes provide evaluation evidence. Recommendations do not establish delivered training or required competence; effectiveness measures must relate to the awareness or risk-control objective being evaluated. - ISO 27001: Cl. 9.1, Cl. 7.3, A.6.3 — Measured changes in risky behavior provide security-effectiveness evidence; targeted coaching can support awareness when it reaches employees. Define the relevant objective, baseline, responsibility, measurement cadence and evaluation. Recommendations alone are not delivered training and do not determine or assess required competence. ## VAL-006: Measure employee self-remediation - Area: AI Usage, Spend & Value - Verification: Proof of value - OWASP adoption tier: AT0–AT4 - URL: /r/VAL-006 **Acceptance criteria:** Record whether a warned user cancels, edits, redirects or proceeds, and calculate a remediation rate where privacy allows. **Why it matters:** Self-remediation shows whether coaching changes behavior or just records it. **How to verify:** Share of coached pilot interventions where the employee edits or cancels, and the trend over the pilot. **OWASP adoption context:** Shadow, embedded-assistant and integrated-platform interactions are primary contexts for observing whether employees cancel, edit or proceed after a warning. **Mappings:** - NIST CSF 2.0: ID.IM-01, PR.AT-01; ISO 42001: Cl. 7.3, Cl. 9.1 — Post-warning cancel, edit, redirect and proceed behavior provides evidence for evaluating AI/security awareness interventions and identifying improvements. A remediation rate does not prove competence, safe final content or an effective overall program; meaningful denominators and privacy-appropriate collection are needed. - NIST AI RMF: MEASURE 4.1 — Cancel, edit, redirect and proceed telemetry can inform context-sensitive evaluation of measurements. It complements rather than replaces consultation with end users and domain experts. - SOC 2: CC4.1 — Responses to a security warning and the remediation rate provide evidence for evaluating that intervention. Define the denominator and sampling window and use privacy-appropriate collection; a click or edit does not prove safe final content or an effective overall program. - ISO 27001: Cl. 9.1, A.6.3 — Responses to a security warning and a defined remediation rate evaluate a specific security intervention. The training link applies when the metric evaluates a delivered awareness intervention. Define the objective, denominator, sampling window, responsibility, cadence and evaluation; a click or edit does not prove safe content, competence or understanding of ISMS duties. ## VAL-007: Provide role-based dashboards and reporting, up to board level - Area: AI Usage, Spend & Value - Verification: Walkthrough - OWASP adoption tier: AT0–AT2 - Formerly: GOV-009 - URL: /r/VAL-007 **Acceptance criteria:** Tailor views for Security, IT, GRC, Legal, executives and business units, filter by unit, tool, environment, owner and risk, and summarize adoption, risk, policy, incidents and recommendations with trends and supporting evidence. **Why it matters:** Each audience, from SOC to board, needs its own view of the same data. **How to verify:** The same pilot data shown through executive, function and security views. **OWASP adoption context:** Role-based governance reporting can combine workforce AI evidence from any adoption tier while limiting the detail each audience receives. **Mappings:** - ISO 42001: Cl. 9.1, Cl. 9.3; SOC 2: CC2.1, CC2.2, CC4.1; ISO 27001: Cl. 9.1, Cl. 9.3.2 — Evidence-backed risk, policy and incident trends provide information for performance evaluation, oversight and management review. Responsible people must receive, review and act on it; a dashboard is not a completed review, and adoption metrics alone are not security-effectiveness evidence. - NIST AI RMF: GOVERN 2.1 — Role-tailored reporting helps communicate AI-risk information to people with governance responsibilities across teams. Providing views does not itself assign those responsibilities or establish accountability. - NIST CSF 2.0: GV.OV-03 — Evidence-backed risk, policy and incident trends provide inputs to cybersecurity performance oversight. Responsible people must review and use the reporting; a dashboard is not a completed review, and adoption alone is not security-effectiveness evidence.