Security controls

Security controls are safeguards or countermeasures to avoid, detect, counteract, or minimize security risks to physical property, information, computer systems, or other assets. In the field of information security, such controls protect the confidentiality, integrity and availability of information.

Systems of controls can be referred to as frameworks or standards. Frameworks can enable an organization to manage security controls across different types of assets with consistency.

Types of security controlsEdit

Security controls can be classified by several criteria. For example, according to the time that they act, relative to a security incident:

  • Before the event, preventive controls are intended to prevent an incident from occurring e.g. by locking out unauthorized intruders;
  • During the event, detective controls are intended to identify and characterize an incident in progress e.g. by sounding the intruder alarm and alerting the security guards or police;
  • After the event, corrective controls are intended to limit the extent of any damage caused by the incident e.g. by recovering the organization to normal working status as efficiently as possible.

They can also be classified according to their nature, for example:

  • Physical controls e.g. fences, doors, locks and fire extinguishers;
  • Procedural controls e.g. incident response processes, management oversight, security awareness and training;
  • Technical controls e.g. user authentication (login) and logical access controls, antivirus software, firewalls;
  • Legal and regulatory or compliance controls e.g. privacy laws, policies and clauses.

Information security standards and control frameworksEdit

Numerous information security standards promote good security practices and define frameworks or systems to structure the analysis and design for managing information security controls. Some of the most well known are outlined below.

International Standards OrganizationEdit

ISO/IEC 27001 specifies 114 controls in 14 groups:

  • A.5: Information security policies
  • A.6: How information security is organised
  • A.7: Human resources security - controls that are applied before, during, or after employment.
  • A.8: Asset management
  • A.9: Access controls and managing user access
  • A.10: Cryptographic technology
  • A.11: Physical security of the organisation's sites and equipment
  • A.12: Operational security
  • A.13: Secure communications and data transfer
  • A.14: Secure acquisition, development, and support of information systems
  • A.15: Security for suppliers and third parties
  • A.16: Incident management
  • A.17: Business continuity/disaster recovery (to the extent that it affects information security)
  • A.18: Compliance - with internal requirements, such as policies, and with external requirements, such as laws.

U.S. Federal Government information security standardsEdit

The Federal Information Processing Standards (FIPS) apply to all US government agencies. However, certain national security systems under the purview of the Committee on National Security Systems are managed outside these standards.

Federal information Processing Standard 200 (FIPS 200), "Minimum Security Requirements for Federal Information and Information Systems", specifies the minimum security controls for federal information systems and the processes by which risk-based selection of security controls occurs. The catalog of minimum security controls is found in NIST Special Publication SP 800-53.

FIPS 200 identifies 17 broad control families:

  1. AC Access Control.
  2. AT Awareness and Training.
  3. AU Audit and Accountability.
  4. CA Security Assessment and Authorization. (historical abbreviation)
  5. CM Configuration Management.
  6. CP Contingency Planning.
  7. IA Identification and Authentication.
  8. IR Incident Response.
  9. MA Maintenance.
  10. MP Media Protection.
  11. PE Physical and Environmental Protection.
  12. PL Planning.
  13. PS Personnel Security.
  14. RA Risk Assessment.
  15. SA System and Services Acquisition.
  16. SC System and Communications Protection.
  17. SI System and Information Integrity.

National Institute of Standards and Technology

NIST Cybersecurity FrameworkEdit

A maturity based framework divided into five functional areas and approximately 100 individual controls in its "core."

NIST SP-800-53Edit

A database of nearly one thousand technical controls grouped into families and cross references.

  • Starting with Revision 3 of 800-53, Program Management controls were identified. These controls are independent of the system controls, but are necessary for an effective security program.
  • Starting with Revision 4 of 800-53, eight families of privacy controls were identified to align the security controls with the privacy expectations of federal law.
  • Starting with Revision 5 of 800-53, the controls also address data privacy as defined by the NIST Data Privacy Framework.

Commercial Control SetsEdit

COBIT5Edit

A proprietary control set published by ISACA. [1]

  • Governance of Enterprise IT
    • Evaluate, Direct and Monitor (EDM) – 5 processes
  • Management of Enterprise IT
    • Align, Plan and Organise (APO) – 13 processes
    • Build, Acquire and Implement (BAI) – 10 processes
    • Deliver, Service and Support (DSS) – 6 processes
    • Monitor, Evaluate and Assess (MEA) - 3 processes

CIS Top-20Edit

A commercially licensable control set published by the Center for Internet Security.[2]

  • 20 controls developed by a network of volunteers and made available for commercial use through a license agreement.

ts mitigationEdit

An open (Creative Commons) and commercially licensable control set from Threat Sketch.[3]

  • Open: 50 business language mitigations mapped to one hundred NIST Cybersecurity Framework controls.
  • Open: 50 business language mitigations mapped to nearly one thousand NIST SP-800-53 controls.

TelecommunicationsEdit

In telecommunications, security controls are defined as security services as part of the OSI Reference model

  • ITU-T X.800 Recommendation.
  • ISO ISO 7498-2

These are technically aligned.[4][5] This model is widely recognized.[6][7]

Data Liability (legal, regulatory, compliance)Edit

The intersection of security risk and laws that set standards of care is where data liability are defined. A handful of databases are emerging to help risk managers research laws that define liability at the country, province/state, and local levels. In these control sets, compliance with relevant laws are the actual risk mitigators.

  • Perkins Coie Security Breach Notification Chart: A set of articles (one per state) that define data breach notification requirements among US states. [8]
  • NCSL Security Breach Notification Laws: A list of US state statutes that define data breach notification requirements.[9]
  • ts jurisdiction: A commercial cybersecurity research platform with coverage of 380+ US State & Federal laws that impact cybersecurity before and after a breach. ts jurisdiction also maps to the NIST Cybersecurity Framework.[10]

Business control frameworksEdit

There are a wide range of frameworks and standards looking at internal business, and inter-business controls, including:

See alsoEdit

ReferencesEdit

  1. ^ "COBIT Framework | Risk & Governance | Enterprise IT Management - ISACA". cobitonline.isaca.org. Retrieved 2020-03-18.
  2. ^ "The 20 CIS Controls & Resources". CIS. Retrieved 2020-03-18.
  3. ^ "ts mitigation". Threat Sketch. Retrieved 2020-03-18.
  4. ^ X.800 : Security architecture for Open Systems Interconnection for CCITT applications
  5. ^ ISO 7498-2 (Information processing systems – Open systems interconnection – Basic Reference Model – Part 2: Security architecture)
  6. ^ William Stallings Crittografia e sicurezza delle reti Seconda edizione ISBN 88-386-6377-7 Traduzione Italiana a cura di Luca Salgarelli di Cryptography and Network security 4 edition Pearson 2006
  7. ^ Securing information and communications systems: principles, technologies, and applications Steven Furnell, Sokratis Katsikas, Javier Lopez, Artech House, 2008 - 362 pages
  8. ^ "Security Breach Notification Chart". Perkins Coie. Retrieved 2020-03-18.
  9. ^ "Security Breach Notification Laws". www.ncsl.org. Retrieved 2020-03-18.
  10. ^ "ts jurisdiction". Threat Sketch. Retrieved 2020-03-18.