+Input Data Validation

Input Data Validation

Description

Mechanisms exist to check the validity of information inputs.

Possible Solutions & Considerations

Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2

Small Business (10-49 staff) / BLS Firm Size Classes 3-4

Medium Business (50-249 staff) / BLS Firm Size Classes 5-6

Large Business (250-999 staff) / BLS Firm Size Classes 7-8

Enterprise (> 1,000 staff) / BLS Firm Size Class 9

∙ Enterprise formal methods or model-based design for highest-assurance systems

SCR-CMM

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

Technology Development & Acquisition (TDA) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with TDA domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Technology development & acquisition-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ Secure development practices loosely conform to industry-recognized standards for secure engineering (e.g., OWASP, NIST SP 800-218, NIST SP 800-160, etc.).

Level 2 Planned Tracked

Technology Development & Acquisition (TDA) 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 TDA domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with TDA 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 TDA domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Technology development and acquisition-related controls are primarily administrative and preventative in nature (e.g., policies, standards, procedures & guidelines).
▪ Technology development and acquisition management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ Secure development practices mostly conform to industry-recognized standards for secure engineering of Technology Assets, Applications and/or Services (TAAS) (e.g., OWASP, NIST SP 800-218, NIST SP 800-160, etc.).
▪ An application development team, or similar function, uses a structured process to design, build and maintain secure configurations for test, development, staging and production environments.

Level 3 Well Defined

Technology Development & Acquisition (TDA) 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 TDA 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 TDA domain capabilities are well-documented and kept current by process owners.
▪ A software development team, or similar function, is appropriately staffed and supported to implement and maintain TDA domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of technology development and acquisition management (e.g., project management software, software escrow solution, software testing tools, etc.).
▪ 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 TDA 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 check the validity of information inputs.

Level 4 Quantitatively Controlled

Technology Development & Acquisition (TDA) 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

Technology Development & Acquisition (TDA) 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.
▪ Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes.
▪ Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions.

1. Übersicht

Bezeichnung Standard

1.1 Referenzen

1.2 Identifizierte Anforderungen

1.3 Related Regulations

2. Identifizierte Anforderungen

Anforderungen
Source Anforderung

3. Related Regulations

Regulations
Source Regulierung

Linked Issues

Issuelinks
Linktyp Issue
is related to Annual
is related to relative Control Weighting = 09
is related to Technology
is related to Protect
is related to SCRM Focus Tier 1 STRATEGIC
is related to SCRM Focus Tier 2 OPERATIONAL
is related to SCRM Focus Tier 3 TACTICAL
blocks Privilege escalation
blocks Unauthorized access
blocks Loss of integrity through unauthorized changes
blocks Emergent properties and/or unintended consequences
blocks Business interruption
blocks Data loss / corruption
blocks Information loss / corruption or system compromise due to technical attack
blocks Loss of revenue
blocks Cancelled contract
blocks Diminished competitive advantage
blocks Diminished reputation
blocks Fines and judgements
blocks Unmitigated vulnerabilities
blocks System compromise
blocks Inability to support business processes
blocks Incorrect controls scoping
blocks Inadequate internal practices
blocks Inadequate third-party practices
blocks Lack of oversight of internal controls
blocks Lack of oversight of third-party controls
blocks Expense associated with managing a loss event
blocks Inability to maintain situational awareness
blocks Third-party cybersecurity exposure
blocks Third-party physical security exposure
blocks Third-party supply chain relationships, visibility and controls
blocks Third-party compliance / legal exposure
blocks Use of product / service
blocks Reliance on the third-party
blocks SMB/Windows Admin Shares
blocks VNC
blocks Command Obfuscation
blocks Masquerading
blocks Match Legitimate Resource Name or Location
blocks Masquerade File Type
blocks Exfiltration Over Alternative Protocol
blocks Exfiltration Over Symmetric Encrypted Non-C2 Protocol
blocks Exfiltration Over Asymmetric Encrypted Non-C2 Protocol
blocks Exfiltration Over Unencrypted Non-C2 Protocol
blocks Command and Scripting Interpreter
blocks PowerShell
blocks AppleScript
blocks Windows Command Shell
blocks Unix Shell
blocks Visual Basic
blocks Python
blocks JavaScript
blocks Network Device CLI
blocks DNS
blocks Taint Shared Content
blocks Proxy
blocks Multi-hop Proxy
blocks Non-Application Layer Protocol
blocks Trusted Developer Utilities Proxy Execution
blocks ClickOnce
blocks Shared Modules
blocks Software Extensions
blocks Forced Authentication
blocks Exploit Public-Facing Application
blocks BITS Jobs
blocks User Execution
blocks Malicious File
blocks System Script Proxy Execution
blocks PubPrn
blocks System Binary Proxy Execution
blocks Compiled HTML File
blocks Control Panel
blocks CMSTP
blocks InstallUtil
blocks Mshta
blocks Odbcconf
blocks Regsvcs/Regasm
blocks Regsvr32
blocks Rundll32
blocks Verclsid
blocks Mavinject
blocks MMC
blocks Electron Applications
blocks Remote Access Tools
blocks XSL Script Processing
blocks Template Injection
blocks Network Denial of Service
blocks Direct Network Flood
blocks Reflection Amplification
blocks Endpoint Denial of Service
blocks OS Exhaustion Flood
blocks Service Exhaustion Flood
blocks Application Exhaustion Flood
blocks Application or System Exploitation
blocks Data from Cloud Storage
blocks Transfer Data to Cloud Account
blocks Screensaver
blocks LC_LOAD_DYLIB Addition
blocks Accessibility Features
blocks AppCert DLLs
blocks AppInit DLLs
blocks Winlogon Helper DLL
blocks Kernel Modules and Extensions
blocks TCC Manipulation
blocks Unsecured Credentials
blocks Cloud Instance Metadata API
blocks Subvert Trust Controls
blocks Gatekeeper Bypass
blocks SIP and Trust Provider Hijacking
blocks Mark-of-the-Web Bypass
blocks Adversary-in-the-Middle
blocks Name Resolution Poisoning and SMB Relay
blocks ARP Cache Poisoning
blocks DHCP Spoofing
blocks Hidden Window
blocks Run Virtual Instance
blocks Resource Forking
blocks Lateral Tool Transfer
blocks Protocol Tunneling
blocks Hijack Execution Flow
blocks DLL
blocks Dynamic Linker Hijacking
blocks Path Interception by PATH Environment Variable
blocks Path Interception by Search Order Hijacking
blocks Path Interception by Unquoted Path
blocks COR_PROFILER
blocks KernelCallbackTable
blocks AppDomainManager
blocks Network Boundary Bridging
blocks Network Address Translation Traversal
blocks Data from Configuration Repository
blocks SNMP (MIB Dump)
blocks Network Device Configuration Dump
blocks Container Administration Command
blocks Debugger Evasion
  • Secure Controls Framework -

    The Secure Controls Framework® (SCF)

    "The SCF is the Common Controls Framework™ (CCF), the world's most comprehensive cybersecurity and data privacy metaframework - it is also free to use. The entire concept is building secure, compliant and resilient capabilities in the most efficient and cost-effective manner possible.

    The SCF is more than just a unified control catalog, since its included content creates a playbook for Governance, Risk & Compliance (GRC) capabilities. Used globally by organizations of every size, the SCF is a robust and scalable solution for security, compliance and resilience controls. As a comprehensive security framework, the SCF maps 1,400+ controls across 200+ laws, regulations, and industry frameworks so you can implement once and comply everywhere.

    Like it or not, cybersecurity is a protracted war on an asymmetric battlefield, where the threats are everywhere and as defenders we have to make the effort to work together to help improve cybersecurity and data privacy practices, since we all suffer when massive data breaches occur or when cyber attacks have physical impacts. Hackers share information on attack methods with other hackers, so why shouldn’t the good guys share information on how to best protect an organization? We decided to take action and make a difference, since we feel it is too important to wait for someone else to fix the problems that exist.

    The SCF is made up of volunteers, mainly specialists within the cybersecurity profession, who focus on GRC and the cybersecurity side of data privacy. These are auditors, engineers, architects, incident responders, consultants and other specialists who live and breathe these topics on a daily basis. The end product is "expert-derived content" that makes up the SCF." https://securecontrolsframework.com/ 

    Terms & Conditions

    The SCF End User License Agreement (EULA) governs the use of the Secure Controls Framework® (SCF) under the Creative Commons Attribution-No Derivatives 4.0 International Public License.

Impressum Deutsch Englisch