Skip to main content

AST-13: Software Licensing Restrictions

AST 8 — High Identify

Mechanisms exist to protect Intellectual Property (IP) rights with software licensing restrictions.

Renumbered: Formerly AST-02.7 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, AST-13 was Use of Third-Party Devices. That control is now AST-26.

Control Question: Does the organization protect Intellectual Property (IP) rights with software licensing restrictions?

General (15)
US (1)
Framework Mapping Values
USA Federal IRS 1075 2021 SC-18(CE-2)
EMEA (1)
Framework Mapping Values
EMEA UK Cyber Essentials 3.3 3-BP1
APAC (2)
Framework Mapping Values
APAC Japan ISMAP 14.2.7.1 18.1.2 18.1.2.1 18.1.2.2 18.1.2.3 18.1.2.4 18.1.2.5 18.1.2.6 18.1.2.7 18.1.2.8 18.1.2.9 18.1.2.10 18.1.2.11 18.1.2.12
APAC New Zealand HISF Microsmall 2023 HMS14

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

Asset Management (AST) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with AST domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Asset management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Asset management is informally assigned as an additional duty to existing IT/cybersecurity personnel. ▪ Software licensing restrictions for users, as part of acceptable and unacceptable behaviors.

Level 2 — Planned & Tracked

Asset Management (AST) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with AST domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with AST domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with AST domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Asset management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Asset management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ The IT department establishes, maintains and updates an inventory that contains a listing of all organizational-owned TAASD, at a minimum covering common devices (e.g., laptops, workstations and servers). ▪ Software licensing is tracked as part of IT asset inventories. ▪ Software licensing restrictions for users, as part of acceptable and unacceptable behaviors are primarily administrative and preventative in nature.

Level 3 — Well Defined

Asset Management (AST) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with AST domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with AST domain capabilities are well-documented and kept current by process owners. ▪ An IT Asset Management (ITAM) team, or similar function, is appropriately staffed and supported to implement and maintain AST domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of ITAM operations (e.g., ITAM platform, (e.g., Configuration Management Database (CMBD) Asset Management solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with AST domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to protect Intellectual Property (IP) rights with software licensing restrictions.

Level 4 — Quantitatively Controlled

Asset Management (AST) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. AST-13_A01 administrative practices identify software licensing restrictions needed for compliance with End User Licensing Agreements (EULAs).
  2. AST-13_A02 software inventories are reviewed, through automated or manual means, for software licensing compliance per an organization-defined frequency.

Evidence Requirements

E-AST-28 Software Licenses

Documented evidence of software license inventories.

Asset Management

Technology Recommendations

Micro/Small

  • IT Asset Management (ITAM) program

Small

  • IT Asset Management (ITAM) program

Medium

  • IT Asset Management (ITAM) program

Large

  • IT Asset Management (ITAM) program

Enterprise

  • IT Asset Management (ITAM) program

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.