Recent from talks
Nothing was collected or created yet.
BS 7799
View on WikipediaThis article needs additional citations for verification. (November 2010) |
BS 7799 was a British standard "Code of Practice for Information Security Management", first published as such by the British Standards Institution (BSI) in February 1995. Read about the origins of BS 7799 here.
Subsequently, two further parts to BS 7799 were also published (the first becoming BS 7799 Part 1), by which time BSI had become BSI Group.
The original BS 7799 outlined a structured approach to the management of information security but was primarily a description of some 127 information security controls in 10 sections or categories. Each control was designed to address a specified control objective.
Some of the controls considered particularly important at the time were identified as 'key controls' indicated with a key icon in the margin.[1] Following pushback from the user and academic communities, however, the 'key control' concept was dropped when BS 7799 was revised in 1998. Users were encouraged to determine their own risks and objectives in order to select whichever controls were appropriate to their needs - a more fundamental and flexible approach applicable to organisations of all types, sizes and industries.
After a lengthy discussion by standards bodies through ISO/IEC, BS 7799-1 was eventually fast-tracked and adopted as ISO/IEC 17799, "Information Technology - Code of practice for information security management." in 2000. ISO/IEC 17799 was revised in June 2005, and renumbered ISO/IEC 27002 in July 2007 when it was incorporated into the growing ISO/IEC 27000 family of standards.
BS 7799 Part 2 "Information Security Management Systems - Specification with guidance for use." was first published by BSI Group in 1999 as a formal specification supporting conformity assessment and certification. BS 7799-2 explained how to design and implement an information security management system (ISMS) - a systematic approach to the governance and management of information security within an organisation. The 2002 version of BS 7799-2 introduced the Plan-Do-Check-Act (PDCA) (Deming cycle), aligning it with quality standards such as ISO 9000. BS 7799 Part 2 was adopted by ISO/IEC as ISO/IEC 27001 in November 2005.
BS 7799 Part 3 "Information security management systems - Guidelines for information security risk management" was first published by BSI Group in 2005. BS 7799-3 focuses on the identification, analysis, treatment and monitoring of information risks. It was adapted and adopted by ISO/IEC as ISO/IEC 27005 in 2008. Meanwhile, BS 7799-3 continues to evolve in parallel. It was revised in 2017 and a project was proposed in 2023 to simplify the guidance specifically for smaller organisations.[2]
See also
[edit]References
[edit]- ^ List, William. "BS 7799 The Code of Practice for information security management". academic.oup.com. Retrieved 30 November 2023.
- ^ BSI. "British Standards Institution - Project". standardsdevelopment.bsigroup.com. Retrieved 30 November 2023.
External links
[edit]- British Standards Institution -> BSI Shop
- Certificate register Archived 2008-05-09 at the Wayback Machine
- BS 7799 Part 2 PDCA Methodology
BS 7799
View on GrokipediaHistory and Development
Origins and Initial Publication
The development of BS 7799 began in the early 1990s, derived from a security standard donated by Shell to a UK government initiative, and was formalized by the British Standards Institution (BSI) in collaboration with the UK's Department of Trade and Industry (DTI) in 1995, responding to the increasing demand from industry, government, and businesses for a standardized framework to manage information security risks.[3][4] This effort was driven by the early 1990s surge in cyber threats, such as unauthorized access and data breaches, alongside heightened data protection concerns under evolving UK regulations like the Data Protection Act 1984, which underscored the need for systematic security practices in an increasingly digital business environment.[3] The first part of the standard, BS 7799-1, was published on February 15, 1995, as a code of practice for information security management systems (ISMS).[5] Titled "Information security management - Code of practice for information security management systems," it provided non-certifiable guidance on best practices, emphasizing a proactive approach to protecting information assets without mandating formal audits or compliance verification.[5] The initial scope encompassed 10 key security management domains, including security policy, organizational structure for security, asset classification and control, personnel security, physical and environmental security, communications and operations management, access control, systems acquisition development and maintenance, business continuity management, and compliance.[6] Building on this foundation, BS 7799-2 was introduced on February 15, 1998, as the certifiable specification for implementing an ISMS.[7] Titled "Information security management - Specification for information security management systems," it enabled organizations to demonstrate conformance through third-party certification, marking a shift toward auditable implementation of the code of practice outlined in Part 1.[7] This dual-structure approach established BS 7799 as a pioneering standard for integrating security into organizational processes.[8]Revisions and Evolution
Following its initial publication in 1995, BS 7799 underwent iterative revisions to enhance its applicability and robustness in information security management. In 1998, the standard was divided into two distinct parts: BS 7799-1, serving as a code of practice, and BS 7799-2, providing a specification for information security management systems (ISMS). The subsequent 1999 revision of BS 7799-1 expanded the framework to encompass 11 control areas—covering aspects such as security policy, asset management, access control, and compliance—while introducing more detailed guidelines on risk assessment and management to support systematic identification and mitigation of security threats.[9] The 2000 revision of BS 7799-1 further refined these elements by incorporating feedback from early adopters, which led to increased emphasis on legal compliance requirements and business continuity planning as integral components of the control framework.[6] Meanwhile, BS 7799-2 was revised in 2002 to integrate the Plan-Do-Check-Act (PDCA) cycle, a process model that facilitates continual improvement of the ISMS by structuring activities into planning, implementation, monitoring, and review phases. This period of evolution was marked by growing international interest in BS 7799 during the late 1990s, prompting the British Standards Institution (BSI) to collaborate with the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) on harmonizing the standard for broader global relevance.Structure of the Standard
BS 7799-1: Code of Practice
BS 7799-1 serves as a foundational code of practice for information security management, offering detailed guidelines to help organizations implement effective controls for protecting information assets against a wide range of threats. Originally published by the British Standards Institution (BSI) in 1995 and revised in 1999 and 2000, it emphasizes best practices that promote the confidentiality, integrity, and availability of information without imposing mandatory requirements or certification processes.[9][10] This non-certifiable framework acts as a reference for self-assessment and the development of tailored security policies, enabling organizations to build confidence in their inter-organizational dealings and comply with relevant laws and regulations.[11] The standard structures its recommendations around 10 management domains, which collectively outline 127 security controls designed to address specific objectives. These domains cover essential areas such as:- Security policy
- Organizational security
- Asset classification and control
- Personnel security
- Physical and environmental security
- Communications and operations management
- Access control
- Systems development and maintenance
- Business continuity management
- Compliance
BS 7799-2: Specification for ISMS
BS 7799-2, titled "Information security management systems - Specification with guidance for use," provides the certifiable requirements for establishing, implementing, maintaining, and improving an Information Security Management System (ISMS). First published in February 1998 by the British Standards Institution (BSI), it was revised in May 1999 and again in 2002 to enhance its structure. The 2002 edition, effective from September 5, introduced a process-oriented approach aligned with quality management standards such as BS EN ISO 9001:2000, facilitating integration with other management systems like those for environmental management under BS EN ISO 14001:1996.[13][14] The core requirements of BS 7799-2 center on a systematic framework using the Plan-Do-Check-Act (PDCA) model to ensure continual improvement of the ISMS. In the Plan phase, organizations must define the ISMS scope based on business context, locations, assets, and technologies involved; develop an information security policy; conduct risk assessments to identify assets, threats, vulnerabilities, and potential impacts; and select appropriate security controls to address identified risks, drawing from the guidelines in BS 7799-1. The Do phase involves implementing and operating the ISMS, including applying the selected controls and allocating necessary resources. During the Check phase, organizations monitor, measure, and review the ISMS's performance through internal audits, management reviews, and analysis of security incidents. Finally, the Act phase focuses on taking corrective and preventive actions to maintain suitability, adequacy, and effectiveness, thereby driving continual improvement.[14] A key process in BS 7799-2 is the preparation of the Statement of Applicability (SoA), which documents the security controls selected from BS 7799-1, justifies their implementation based on risk assessment results, and explains any exclusions with evidence that such omissions do not compromise the organization's information security. The SoA serves as a critical artifact for demonstrating how risks are managed and must be approved by top management.[14] BS 7799-2 emphasizes auditable conformance to enable third-party certification, requiring demonstrable management commitment through policy approval, resource provision, and regular reviews of residual risks. Internal audits are mandatory to evaluate ISMS effectiveness, identify nonconformities, and ensure compliance with the standard's requirements, with results feeding into management reviews for ongoing enhancements. Certification audits assess adherence to these elements, confirming that the ISMS scope covers relevant organizational parts without unjustified exclusions that could affect security objectives.[14][13]Key Components and Principles
Information Security Management System (ISMS)
The Information Security Management System (ISMS) forms the core framework of BS 7799, providing a structured methodology for organizations to manage sensitive information securely across all assets. It encompasses people, processes, and IT systems to establish, implement, maintain, and continually improve information security practices. This systematic approach ensures that security is addressed proactively rather than reactively, adapting to evolving threats and organizational needs.[15] The primary objectives of the ISMS under BS 7799 are to preserve the confidentiality, integrity, and availability of information—collectively referred to as the CIA triad—applied consistently at an organization-wide level. Confidentiality protects information from unauthorized access, integrity safeguards its accuracy and completeness, and availability ensures timely access for authorized users. These objectives guide the development of security policies that support business operations while mitigating risks to critical data.[12][16] Integration of the ISMS into business processes requires alignment with the organization's overall strategy, emphasizing top management involvement to demonstrate leadership commitment. This includes defining clear roles, allocating necessary resources such as personnel and budget, and embedding security considerations into decision-making. By doing so, the ISMS becomes a seamless part of corporate governance, enhancing resilience without hindering operational efficiency.[17][18] A key element of the ISMS is the creation of risk treatment plans derived from comprehensive risk assessments, which identify potential threats and vulnerabilities to information assets. These plans specify security measures that are proportionate to the level of risk, balancing protection needs with practical feasibility. The process supports ongoing monitoring and adjustment to maintain effective security. The ISMS implementation in BS 7799-2 utilizes the Plan-Do-Check-Act (PDCA) cycle to facilitate this cyclical improvement.[17][6]Security Controls Framework
The Security Controls Framework in BS 7799-1:2000 provides a comprehensive set of best practices for implementing information security measures, organized into 10 domains that address various aspects of organizational security. These domains encompass 36 control objectives and 127 specific controls, designed to mitigate risks to information assets through structured guidelines.[19][6] The domains are as follows:- Security Policy: Establishes management's commitment and direction for information security.
- Organizational Security: Defines roles, responsibilities, and coordination for security governance.
- Asset Classification and Control: Identifies and protects assets based on their sensitivity and value.
- Personnel Security: Addresses security risks from staff recruitment, training, and termination.
- Physical and Environmental Security: Secures facilities, equipment, and environments against unauthorized access and hazards.
- Communications and Operations Management: Ensures secure operations, including incident response and media handling.
- Access Control: Manages user access to systems and data to prevent unauthorized use.
- Systems Development and Maintenance: Incorporates security into software development and maintenance processes.
- Business Continuity Management: Plans for maintaining critical operations during disruptions.
- Compliance: Ensures adherence to legal, regulatory, and internal security requirements.[19]
