Updated 2022-10-17 19:09
https://par-tec.github.io/security-ontologies/onto/iso#27001/2013/control-New
27001/2013/control-New
Show more
Outsourced development
27002/2022/control-8.30
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization should direct, monitor and review the activities related to outsourced system development
Show more
Access control
27002/2022/control-5.15
https://par-tec.github.io/security-ontologies/onto/iso#Control
Rules to control physical and logical access to information and other associated assets should be established and implemented based on business and information security requirements
Show more
Access rights
27002/2022/control-5.18
https://par-tec.github.io/security-ontologies/onto/iso#Control
Access rights to information and other associated assets should be provisioned, reviewed, modified and removed in accordance with the organization’s topic-specific policy and rules on access control
Show more
Access to source code
27002/2022/control-8.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
Read and write access to source code, development tools and software libraries should be appropriately managed
Show more
Application security requirements
27002/2022/control-8.26
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security requirements should be identified, specified and approved when developing or acquiring applications
Show more
Authentication information
27002/2022/control-5.17
https://par-tec.github.io/security-ontologies/onto/iso#Control
Allocation and management of authentication information should be controlled by a management process, including advising personnel of appropriate handling of authentication information
Show more
Cabling security
27002/2022/control-7.12
https://par-tec.github.io/security-ontologies/onto/iso#Control
Cables carrying power, data or supporting information services should be protected from interception, interference or damage
Show more
Capacity management
27002/2022/control-8.6
https://par-tec.github.io/security-ontologies/onto/iso#Control
The use of resources should be monitored and adjusted in line with current and expected capacity requirements
Show more
Change management
27002/2022/control-8.32
https://par-tec.github.io/security-ontologies/onto/iso#Control
Changes to information processing facilities and information systems should be subject to change management procedures
Show more
Classification of information
27002/2022/control-5.12
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information should be classified according to the information security needs of the organization based on confidentiality, integrity, availability and relevant interested party requirements
Show more
Clock synchronization
27002/2022/control-8.17
https://par-tec.github.io/security-ontologies/onto/iso#Control
The clocks of information processing systems used by the organization should be synchronized to approved time sources
Show more
Collection of evidence
27002/2022/control-5.28
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization should establish and implement procedures for the identification, collection, acquisition and preservation of information from information security incidents
Show more
Confidentiality or non-disclosure agreements
27002/2022/control-6.6
https://par-tec.github.io/security-ontologies/onto/iso#Control
Confidentiality or non-disclosure agreements reflecting the organization’s needs for the protection of information should be identified, documented, regularly reviewed and signed by personnel and other relevant interested parties
Show more
Configuration management
27002/2022/control-8.9
https://par-tec.github.io/security-ontologies/onto/iso#Control
Configurations, including security configurations, of hardware, software, services and networks should be established, documented, implemented, monitored and reviewed
About |
Configuration management
|
dcterms:description |
Configurations, including security configurations, of hardware, software, services and networks should be established, documented, implemented, monitored and reviewed
|
dcterms:identifier |
27002/2022/control-8.9
|
dcterms:title |
Configuration management
|
rdf:type |
Control
|
iso:controlCategory |
Technological
|
iso:correspondsTo |
https://par-tec.github.io/security-ontologies/onto/iso#27001/2013/control-New
|
hasControlType |
Preventive
|
https://par-tec.github.io/security-ontologies/onto/iso#hasCybersecurityConcept |
Protect
|
hasInformationSecurityProperty |
Availability
Confidentiality
Integrity
|
hasOperationalCapability |
Secure Configuration
|
iso:hasRelatedControls |
Change management
Intellectual property rights
|
hasInformationSecurityProperty |
Protection and Risk
|
iso:purpose |
To ensure hardware, software, services and networks function correctly with required security settings, and configuration is not altered by unauthorized or incorrect changes
|
Show more
Contact with authorities
27002/2022/control-5.5
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization should establish and maintain contact with relevant authorities
Show more
Data masking
27002/2022/control-8.11
https://par-tec.github.io/security-ontologies/onto/iso#Control
Data masking should be used in accordance with the organization’s topic-specific policy on access control and business requirement, taking legal requirements into consideration
Show more
Disciplinary process
27002/2022/control-6.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
A disciplinary process should be formalized and communicated to take actions against personnel and other relevant interested parties who have committed an information security policy violation
Show more
Documented operating procedures
27002/2022/control-5.37
https://par-tec.github.io/security-ontologies/onto/iso#Control
Operating procedures for information processing facilities should be documented and made available to personnel who need them
Show more
Equipment maintenance
27002/2022/control-7.13
https://par-tec.github.io/security-ontologies/onto/iso#Control
Equipment should be maintained correctly
Show more
Identity management
27002/2022/control-5.16
https://par-tec.github.io/security-ontologies/onto/iso#Control
The full lifecycle of identities should be managed
Show more
Information security event reporting
27002/2022/control-6.8
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization should provide a mechanism for personnel to report observed or suspected information security events through appropriate channels in a timely manner
Show more
Information transfer
27002/2022/control-5.14
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information transfer rules, procedures, or agreements, both within the organization and between the organization and other parties, should be in place for all types of transfer facilities
Show more
Labelling of information
27002/2022/control-5.13
https://par-tec.github.io/security-ontologies/onto/iso#Control
An appropriate set of procedures for information labelling should be developed and implemented in accordance with the information classification scheme adopted by the organization
Show more
Logging
27002/2022/control-8.15
https://par-tec.github.io/security-ontologies/onto/iso#Control
Logs that record activities, exceptions, faults and other relevant events should be produced, protected, stored and analysed
Show more
Management of technical vulnerabilities
27002/2022/control-8.8
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information about technical vulnerabilities of information systems in use should be obtained, the organization’s exposure to such vulnerabilities should be evaluated and appropriate measures should be taken
Show more
Monitoring activities
27002/2022/control-8.16
https://par-tec.github.io/security-ontologies/onto/iso#Control
Networks, systems and applications should be monitored for anomalous behaviour and appropriate actions taken to evaluate potential information security incidents
Show more
Network controls
27002/2022/control-8.20
https://par-tec.github.io/security-ontologies/onto/iso#Control
Networks should be managed and controlled to protect information in systems and applications
Show more
Physical entry controls
27002/2022/control-7.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Secure areas should be protected by appropriate entry controls and access points
Show more
Physical security perimeter
27002/2022/control-7.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Security perimeters should be defined and used to protect areas that contain either sensitive or critical information and other associated assets
Show more
Privacy and protection of PII
27002/2022/control-5.34
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization should identify and meet the requirements regarding preservation of privacy and protection of PII according to applicable laws and regulations and contractual requirements
Show more
Privileged access rights
27002/2022/control-8.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
The allocation and use of privileged access rights should be restricted and managed
Show more
Protection of records
27002/2022/control-5.33
https://par-tec.github.io/security-ontologies/onto/iso#Control
Records should be protected from loss, destruction, falsification, unauthorized access and unauthorized release, in accordance with legal, statutory, regulatory, contractual and business requirements
Show more
Remote working
27002/2022/control-6.7
https://par-tec.github.io/security-ontologies/onto/iso#Control
Security measures should be implemented when personnel are working remotely to protect information accessed, processed or stored outside the organization's premises
Show more
Return of assets
27002/2022/control-5.11
https://par-tec.github.io/security-ontologies/onto/iso#Control
Personnel and other interested parties as appropriate should return all the organization's assets in their possession upon change or termination of their employment, contract or agreement
Show more
Screening
27002/2022/control-6.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Background verification checks on all candidates to become personnel should be carried out prior to joining the organization and on an ongoing basis in accordance with applicable laws, regulations and ethics, and be proportional to the business requirements, the classification of the information to be accessed and the perceived risks
Show more
Secure authentication
27002/2022/control-8.5
https://par-tec.github.io/security-ontologies/onto/iso#Control
Secure authentication technologies and procedures should be implemented based on information access restrictions and the topic-specific policy on access control
Show more
Secure coding
27002/2022/control-8.28
https://par-tec.github.io/security-ontologies/onto/iso#Control
Secure coding principles should be applied to software development
Show more
Secure development lifecycle
27002/2022/control-8.25
https://par-tec.github.io/security-ontologies/onto/iso#Control
Rules for the secure development of software and systems should be established and applied
Show more
Secure system architecture and engineering principles
27002/2022/control-8.27
https://par-tec.github.io/security-ontologies/onto/iso#Control
Principles for engineering secure systems should be established, documented, maintained and applied to any information system development activities
Show more
Security testing in development and acceptance
27002/2022/control-8.29
https://par-tec.github.io/security-ontologies/onto/iso#Control
Security testing processes should be defined and implemented in the development lifecycle
Show more
Segregation in networks
27002/2022/control-8.23
https://par-tec.github.io/security-ontologies/onto/iso#Control
Groups of information services, users, and information systems should be segregated in the organization’s networks
Show more
Storage media
27002/2022/control-7.10
https://par-tec.github.io/security-ontologies/onto/iso#Control
Storage media should be managed through its lifecycle of acquisition, use, transportation and disposal in accordance with the organization’s classification scheme and handling requirements
Show more
Use of privileged utility programs
27002/2022/control-8.18
https://par-tec.github.io/security-ontologies/onto/iso#Control
The use of utility programs that might be capable of overriding system and application controls should be restricted and tightly controlled
Show more
User endpoint devices
27002/2022/control-8.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information stored on, processed by or accessible via user endpoint devices should be protected
Show more
Web filtering
27002/2022/control-8.22
https://par-tec.github.io/security-ontologies/onto/iso#Control
Access to external websites should be managed to reduce exposure to malicious content
Show more
Working in secure areas
27002/2022/control-7.6
https://par-tec.github.io/security-ontologies/onto/iso#Control
Procedures for working in secure areas should be designed and implemented
Show more
Acceptable use of assets
27001/2013/control-8.1.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Rules for the acceptable use of information and of assets associated with information and information processing facilities shall be identified, documented and implemented.
Show more
Acceptable use of information and associated assets
27002/2022/control-5.10
https://par-tec.github.io/security-ontologies/onto/iso#Control
Rules for the acceptable use and procedures for the handling of information and other associated assets should be identified, documented and implemented
Show more
Access control policy
27001/2013/control-9.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
An access control policy shall be established, documented and reviewed based on business and information security requirements.
Show more
Access control to program source code
27001/2013/control-9.4.5
https://par-tec.github.io/security-ontologies/onto/iso#Control
Access to program source code shall be restricted.
Show more
Access to networks and network services
27001/2013/control-9.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Users shall only be provided with access to the network and network services that they have been specifically authorized to use.
Show more
Addressing information security within supplier agreements
27002/2022/control-5.20
https://par-tec.github.io/security-ontologies/onto/iso#Control
Relevant information security requirements should be established and agreed with each supplier based on the type of supplier relationship
Show more
Addressing security within supplier agreements
27001/2013/control-15.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
All relevant information security requirements shall be established and agreed with each supplier that may access, process, store, communicate, or provide IT infrastructure components for, the organization’s information.
Show more
Administrator and operator logs
27001/2013/control-12.4.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
System administrator and system operator activities shall be logged and the logs protected and regularly reviewed.
Show more
Agreements on information transfer
27001/2013/control-13.2.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Agreements shall address the secure transfer of business information between the organization and external parties.
Show more
Assessment and decision on information security events
27002/2022/control-5.25
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization should assess information security events and decide if they are to be categorized as information security incidents
Show more
Assessment of and decision on information security events
27001/2013/control-16.1.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security events shall be assessed and it shall be decided if they are to be classified as information security incidents.
Show more
Availability of information processing facilities
27001/2013/control-17.2.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information processing facilities shall be implemented with redundancy sufficient to meet availability requirements.
Show more
Cabling security
27001/2013/control-11.2.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Power and telecommunications cabling carrying data or supporting information services shall be protected from interception, interference or damage.
Show more
Capacity management
27001/2013/control-12.1.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
The use of resources shall be monitored, tuned and projections made of future capacity requirements to ensure the required system performance.
Show more
Change management
27001/2013/control-12.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Changes to the organization, business processes, information processing facilities and systems that affect information security shall be controlled.
Show more
Classification of information
27001/2013/control-8.2.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information shall be classified in terms of legal requirements, value, criticality and sensitivity to unauthorized disclosure or modification.
Show more
Clear desk and clear screen
27002/2022/control-7.7
https://par-tec.github.io/security-ontologies/onto/iso#Control
Clear desk rules for papers and removable storage media and clear screen rules for information processing facilities should be defined and enforced
Show more
Clear desk and clear screen policy
27001/2013/control-11.2.9
https://par-tec.github.io/security-ontologies/onto/iso#Control
A clear desk policy for papers and removable storage media and a clear screen policy for information processing facilities shall be adopted.
Show more
Clock synchronization
27001/2013/control-12.4.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
The clocks of all relevant information processing systems within an organization or security domain shall be synchronized to a single reference time source.
Show more
Collection of evidence
27001/2013/control-16.1.7
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization shall define and apply procedures for the identification, collection, acquisition and preservation of information, which can serve as evidence.
Show more
Compliance with policies and standards for information security
27002/2022/control-5.36
https://par-tec.github.io/security-ontologies/onto/iso#Control
Compliance with the organization’s information security policy, topic-specific policies and standards should be regularly reviewed
Show more
Compliance with security policies and standards
27001/2013/control-18.2.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Managers shall regularly review the compliance of information processing and procedures within their area of responsibility with the appropriate security policies, standards and any other security requirements.
Show more
Confidentiality or nondisclosure agreements
27001/2013/control-13.2.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
Requirements for confidentiality or non-disclosure agreements reflecting the organization’s needs for the protection of information shall be identified, regularly reviewed and documented.
Show more
Contact with authorities
27001/2013/control-6.1.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Appropriate contacts with relevant authorities shall be maintained.
Show more
Contact with special interest groups
27002/2022/control-5.6
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization should establish and maintain contact with special interest groups or other specialist
security forums and professional associations
Show more
Contact with special interest groups
27001/2013/control-6.1.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
Appropriate contacts with special interest groups or other specialist security forums and professional associations shall be maintained.
Show more
Controls against malware
27001/2013/control-12.2.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Detection, prevention and recovery controls to protect against malware shall be implemented, combined with appropriate user awareness.
Show more
Data leakage prevention
27002/2022/control-8.12
https://par-tec.github.io/security-ontologies/onto/iso#Control
Data leakage prevention measures should be applied to systems, networks and endpoint devices that process, store or transmit sensitive information
Show more
Delivery and loading areas
27001/2013/control-11.1.6
https://par-tec.github.io/security-ontologies/onto/iso#Control
Access points such as delivery and loading areas and other points where unauthorized persons could enter the premises shall be controlled and, if possible, isolated from information processing facilities to avoid unauthorized access.
Show more
Disciplinary process
27001/2013/control-7.2.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
There shall be a formal and communicated disciplinary process in place to take action against employees who have committed an information security breach.
Show more
Disposal of media
27001/2013/control-8.3.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Media shall be disposed of securely when no longer required, using formal procedures.
Show more
Documented operating procedures
27001/2013/control-12.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Operating procedures shall be documented and made available to all users who need them.
Show more
Electronic messaging
27001/2013/control-13.2.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information involved in electronic messaging shall be appropriately protected.
Show more
Equipment maintenance
27001/2013/control-11.2.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
Equipment shall be correctly maintained to ensure its continued availability and integrity.
Show more
Equipment siting and protection
27002/2022/control-7.8
https://par-tec.github.io/security-ontologies/onto/iso#Control
Equipment should be sited securely and protected
Show more
Equipment siting and protection
27001/2013/control-11.2.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Equipment shall be sited and protected to reduce the risks from environmental threats and hazards, and opportunities for unauthorized access.
Show more
Event logging
27001/2013/control-12.4.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Event logs recording user activities, exceptions, faults and information security events shall be produced, kept and regularly reviewed.
Show more
Handling of assets
27001/2013/control-8.2.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Procedures for handling assets shall be developed and implemented in accordance with the information classification scheme adopted by the organization.
Show more
ICT readiness for business continuity
27002/2022/control-5.30
https://par-tec.github.io/security-ontologies/onto/iso#Control
ICT readiness should be planned, implemented, maintained and tested based on business continuity objectives and ICT continuity requirements
Show more
Identification of applicable legislation and contractual requirements
27001/2013/control-18.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
All relevant legislative statutory, regulatory, contractual requirements and the organization’s approach to meet these requirements shall be explicitly identified, documented and kept up to date for each information system and the organization.
Show more
Identification of legal, statutory, regulatory and contractual requirements
27002/2022/control-5.31
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security relevant legal, statutory, regulatory and contractual requirements and the organization’s approach to meet these requirements should be identified, documented and kept up to date
Show more
Implementing information security continuity
27001/2013/control-17.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization shall establish, document, implement and maintain processes, procedures and controls to ensure the required level of continuity for information security during an adverse situation.
Show more
Independent review of information security
27001/2013/control-18.2.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization’s approach to managing information security and its implementation (i.e. control objectives, controls, policies, processes and procedures for information security) shall be reviewed independently at planned intervals or when significant changes occur.
Show more
Independent review of information security
27002/2022/control-5.35
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization’s approach to managing information security and its implementation including people process and technology should be reviewed independently at planned intervals, or when significant changes occur
Show more
Information access restriction
27002/2022/control-8.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Access to information and other associated assets should be restricted in accordance with the established topic-specific policy on access control
Show more
Information access restriction
27001/2013/control-9.4.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Access to information and application system functions shall be restricted in accordance with the access control policy.
Show more
Information and communication technology supply chain
27001/2013/control-15.1.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Agreements with suppliers shall include requirements to address the information security risks associated with information and communications technology services and product supply chain.
Show more
Information backup
27001/2013/control-12.3.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Backup copies of information, software and system images shall be taken and tested regularly in accordance with an agreed backup policy.
Show more
Information backup
27002/2022/control-8.13
https://par-tec.github.io/security-ontologies/onto/iso#Control
Backup copies of information, software and systems should be maintained and regularly tested in accordance with the agreed topic-specific policy on backup
Show more
Information deletion
27002/2022/control-8.10
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information stored in information systems and devices should be deleted when no longer required
Show more
Information security
requirements analysis
and specification
27001/2013/control-14.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
The information security related requirements shall be included in the requirements for new information systems or enhancements to existing information systems.
Show more
Information security awareness, education and training
27002/2022/control-6.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Personnel of the organization and relevant interested parties should receive appropriate information security awareness, education and training and regular updates of organizational policies and procedures, as relevant for their job function
Show more
Information security awareness, education and training
27001/2013/control-7.2.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
All employees of the organization and, where relevant, contractors shall receive appropriate awareness education and training and regular updates in organizational policies and procedures, as relevant for their job function.
Show more
Information security during disruption
27002/2022/control-5.29
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization should plan how to maintain information security at an appropriate level during disruption
Show more
Information security for use of cloud services
27002/2022/control-5.23
https://par-tec.github.io/security-ontologies/onto/iso#Control
Processes for acquisition, use, management and exit from cloud services should be established in accordance with the organization’s information security requirements
Show more
Information security in project management
27002/2022/control-5.8
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security should be integrated into the organization's project management activities
Show more
Information security in project management
27001/2013/control-6.1.5
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security shall be addressed in project management, regardless of the type of the project.
Show more
Information security in supplier relationships
27002/2022/control-5.19
https://par-tec.github.io/security-ontologies/onto/iso#Control
Processes and procedures should be identified and implemented to manage the information security risks associated with the use of supplier's products or services
Show more
Information security incident management responsibilities and preparation
27002/2022/control-5.24
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization should plan and prepare for managing information security incidents by defining, establishing and communicating information security incident management processes, roles and responsibilities
Show more
Information security policy for supplier relationships
27001/2013/control-15.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security requirements for mitigating the risks associated with supplier’s access to the organization’s assets shall be agreed with the supplier and documented.
Show more
Information security roles and responsibilities
27002/2022/control-5.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security roles and responsibilities should be defined and allocated according to the
organization needs
Show more
Information security roles and responsibilities
27001/2013/control-6.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
All information security responsibilities shall be defined and allocated.
Show more
Information systems audit controls
27001/2013/control-12.7.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Audit requirements and activities involving verification of operational systems shall be carefully planned and agreed to minimize disruptions to business processes.
Show more
Information transfer policies and procedures
27001/2013/control-13.2.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Formal transfer policies, procedures and controls shall be in place to protect the transfer of information through the use of all types of communication facilities.
Show more
Installation of software on operational systems
27002/2022/control-8.19
https://par-tec.github.io/security-ontologies/onto/iso#Control
Procedures and measures should be implemented to securely manage software installation on operational systems
Show more
Installation of software on operational systems
27001/2013/control-12.5.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Procedures shall be implemented to control the installation of software on operational systems.
Show more
Intellectual property rights
27002/2022/control-5.32
https://par-tec.github.io/security-ontologies/onto/iso#Control
Organizations should implement appropriate procedures should be implemented to protect intellectual property rights
Show more
Intellectual property rights
27001/2013/control-18.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Appropriate procedures shall be implemented to ensure compliance with legislative, regulatory and contractual requirements related to intellectual property rights and use of proprietary software products.
Show more
Inventory of assets
27001/2013/control-8.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Assets associated with information and information processing facilities shall be identified and an inventory of these assets shall be drawn up and maintained.
Show more
Inventory of information and other associated assets
27002/2022/control-5.9
https://par-tec.github.io/security-ontologies/onto/iso#Control
An inventory of information and other associated assets, including owners, should be developed and
maintained
Show more
Key management
27001/2013/control-10.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
A policy on the use, protection and lifetime of cryptographic keys shall be developed and implemented through their whole lifecycle.
Show more
Labeling of information
27001/2013/control-8.2.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
An appropriate set of procedures for information labeling shall be developed and implemented in accordance with the information classification scheme adopted by the organization.
Show more
Learning from information security incidents
27001/2013/control-16.1.6
https://par-tec.github.io/security-ontologies/onto/iso#Control
Knowledge gained from analyzing and resolving information security incidents shall be used to reduce the likelihood or impact of future incidents.
Show more
Learning from information security incidents
27002/2022/control-5.27
https://par-tec.github.io/security-ontologies/onto/iso#Control
Knowledge gained from information security incidents should be used to strengthen and improve the control environment
Show more
Management of privileged access rights
27001/2013/control-9.2.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
The allocation and use of privileged access rights shall be restricted and controlled.
Show more
Management of removable media
27001/2013/control-8.3.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Procedures shall be implemented for the management of removable media in accordance with the classification scheme adopted by the organization.
Show more
Management of secret authentication information of users
27001/2013/control-9.2.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
The allocation of secret authentication information shall be controlled through a formal management process.
Show more
Management of technical vulnerabilities
27001/2013/control-12.6.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information about technical vulnerabilities of information systems being used shall be obtained in a timely fashion, the organization’s exposure to such vulnerabilities evaluated and appropriate measures taken to address the associated risk.
Show more
Management responsibilities
27002/2022/control-5.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
Management should be a role model for information security and require all personnel to apply
information security in accordance with the established information security policy, topic-specific
policies and procedures of the organization
Show more
Management responsibilities
27001/2013/control-7.2.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Management shall require all employees and contractors to apply information security in accordance with the established policies and procedures of the organization.
Show more
Managing changes to supplier services
27001/2013/control-15.2.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Changes to the provision of services by suppliers, including maintaining and improving existing information security policies, procedures and controls, shall be managed, taking account of the criticality of business information, systems and processes involved and re-assessment of risks.
Show more
Managing information security in the ICT supply chain
27002/2022/control-5.21
https://par-tec.github.io/security-ontologies/onto/iso#Control
Processes and procedures should be defined and implemented to address information security risks associated with ICT services and product supply chain
Show more
Mobile device policy
27001/2013/control-6.2.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
A policy and supporting security measures shall be adopted to manage the risks introduced by using mobile devices.
Show more
Monitoring and review of supplier services
27001/2013/control-15.2.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Organizations shall regularly monitor, review and audit supplier service delivery.
Show more
Monitoring, review and change management of supplier services
27002/2022/control-5.22
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization should regularly monitor, review, evaluate and manage change in supplier information security practices and service delivery
Show more
Network controls
27001/2013/control-13.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Networks shall be managed and controlled to protect information in systems and applications.
Show more
Outsourced development
27001/2013/control-14.2.7
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization shall supervise and monitor the activity of outsourced system development.
Show more
Ownership of assets
27001/2013/control-8.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Assets maintained in the inventory shall be owned.
Show more
Password management system
27001/2013/control-9.4.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Password management systems shall be interactive and shall ensure quality passwords.
Show more
Physical entry controls
27001/2013/control-11.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Secure areas shall be protected by appropriate entry controls to ensure that only authorized personnel are allowed access.
Show more
Physical media transfer
27001/2013/control-8.3.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Media containing information shall be protected against unauthorized access, misuse or corruption during transportation.
Show more
Physical security monitoring
27002/2022/control-7.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
Premises should be continuously monitored for unauthorized physical access
Show more
Physical security perimeter
27001/2013/control-11.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Security perimeters shall be defined and used to protect areas that contain either sensitive or critical information and information processing facilities.
Show more
Planning information security continuity
27001/2013/control-17.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization shall determine its requirements for information security and the continuity of information security management in adverse situations, e.g. during a crisis or disaster.
Show more
Policies for information security
27001/2013/control-5.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
A set of policies for information security shall be defined, approved by management, published and communicated to employees and relevant external parties.
Show more
Policies for information security
27002/2022/control-5.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security policy and topic-specific policies should be defined, approved by management,
published, communicated to and acknowledged by relevant personnel and relevant interested parties,
and reviewed at planned intervals and if significant changes occur.
Show more
Policy on the use of cryptographic controls
27001/2013/control-10.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
A policy on the use of cryptographic controls for protection of information shall be developed and implemented.
Show more
Privacy and protection of personally identifiable information
27001/2013/control-18.1.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
Privacy and protection of personally identifiable information shall be ensured as required in relevant legislation and regulation where applicable.
Show more
Protecting against external and environmental threats
27001/2013/control-11.1.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
Physical protection against natural disasters, malicious attack or accidents shall be designed and applied.
Show more
Protecting against physical and environmental threats
27002/2022/control-7.5
https://par-tec.github.io/security-ontologies/onto/iso#Control
Protection against physical and environmental threats, such as natural disasters and other intentional or unintentional physical threats to infrastructure should be designed and implemented
Show more
Protecting application
services transactions
27001/2013/control-14.1.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information involved in application service transactions shall be protected to prevent incomplete transmission, mis-routing, unauthorized message alteration, unauthorized disclosure, unauthorized message duplication or replay
Show more
Protection against malware
27002/2022/control-8.7
https://par-tec.github.io/security-ontologies/onto/iso#Control
Protection against malware should be implemented, supported by appropriate user awareness
Show more
Protection of information systems during audit and testing
27002/2022/control-8.34
https://par-tec.github.io/security-ontologies/onto/iso#Control
Audit tests and other assurance activities involving assessment of operational systems should be planned and agreed between the tester and appropriate management
Show more
Protection of log information
27001/2013/control-12.4.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Logging facilities and log information shall be protected against tampering and unauthorized access.
Show more
Protection of records
27001/2013/control-18.1.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Records shall be protected from loss, destruction, falsification, unauthorized access and unauthorized release, in accordance with legislative, regulatory, contractual and business requirements.
Show more
Protection of test data
27001/2013/control-14.3.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Test data shall be selected carefully, protected and controlled.
Show more
Redundancy of information processing facilities
27002/2022/control-8.14
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information processing facilities should be implemented with redundancy sufficient to meet availability requirements
Show more
Regulation of cryptographic controls
27001/2013/control-18.1.5
https://par-tec.github.io/security-ontologies/onto/iso#Control
Cryptographic controls shall be used in compliance with all relevant agreements, legislation and regulations.
Show more
Removal of assets
27001/2013/control-11.2.5
https://par-tec.github.io/security-ontologies/onto/iso#Control
Equipment, information or software shall not be taken off-site without prior authorization.
Show more
Removal or adjustment of access rights
27001/2013/control-9.2.6
https://par-tec.github.io/security-ontologies/onto/iso#Control
The access rights of all employees and external party users to information and information processing facilities shall be removed upon termination of their employment, contract or agreement, or adjusted upon change.
Show more
Reporting information security events
27001/2013/control-16.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security events shall be reported through appropriate management channels as quickly as possible.
Show more
Reporting information security weaknesses
27001/2013/control-16.1.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Employees and contractors using the organization’s information systems and services shall be required to note and report any observed or suspected information security weaknesses in systems or services.
Show more
Response to information security incidents
27002/2022/control-5.26
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security incidents should be responded to in accordance with the documented procedures
Show more
Response to information security incidents
27001/2013/control-16.1.5
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security incidents shall be responded to in accordance with the documented procedures.
Show more
Responsibilities after termination or change of employment
27002/2022/control-6.5
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security responsibilities and duties that remain valid after termination or change of employment should be defined, enforced and communicated to relevant personnel and other interested parties
Show more
Responsibilities and procedures
27001/2013/control-16.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Management responsibilities and procedures shall be established to ensure a quick, effective and orderly response to information security incidents.
Show more
Restrictions on changes to software packages
27001/2013/control-14.2.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
Modifications to software packages shall be discouraged, limited to necessary changes and all changes shall be strictly controlled.
Show more
Restrictions on software installation
27001/2013/control-12.6.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Rules governing the installation of software by users shall be established and implemented.
Show more
Return of assets
27001/2013/control-8.1.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
All employees and external party users shall return all of the organizational assets in their possession upon termination of their employment, contract or agreement.
Show more
Review of the policies for information security
27001/2013/control-5.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
The policies for information security shall be reviewed at planned intervals or if significant changes occur to ensure their continuing suitability, adequacy and effectiveness.
Show more
Review of user access rights
27001/2013/control-9.2.5
https://par-tec.github.io/security-ontologies/onto/iso#Control
Asset owners shall review users’ access rights at regular intervals.
Show more
Screening
27001/2013/control-7.1.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Background verification checks on all candidates for employment shall be carried out in accordance with relevant laws, regulations and ethics and shall be proportional to the business requirements, the classification of the information to be accessed and the perceived risks.
Show more
Secure development environment
27001/2013/control-14.2.6
https://par-tec.github.io/security-ontologies/onto/iso#Control
Organizations shall establish and appropriately protect secure development environments for system development and integration efforts that cover the entire system development lifecycle.
Show more
Secure development policy
27001/2013/control-14.2.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Rules for the development of software and systems shall be established and applied to developments within the organization.
Show more
Secure disposal or re-use of equipment
27002/2022/control-7.14
https://par-tec.github.io/security-ontologies/onto/iso#Control
Items of equipment containing storage media should be verified to ensure that any sensitive data and licensed software has been removed or securely overwritten prior to disposal or re-use
Show more
Secure disposal or reuse of equipment
27001/2013/control-11.2.7
https://par-tec.github.io/security-ontologies/onto/iso#Control
All items of equipment containing storage media shall be verified to ensure that any sensitive data and licensed software has been removed or securely overwritten prior to disposal or re-use.
Show more
Secure log-on procedures
27001/2013/control-9.4.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Where required by the access control policy, access to systems and applications shall be controlled by a secure log-on procedure.
Show more
Secure system engineering principles
27001/2013/control-14.2.5
https://par-tec.github.io/security-ontologies/onto/iso#Control
Principles for engineering secure systems shall be established, documented, maintained and applied to any information system implementation efforts.
Show more
Securing application
services on public
networks
27001/2013/control-14.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information involved in application services passing over public networks shall be protected from fraudulent activity, contract dispute and unauthorized disclosure and modification.
Show more
Securing offices, rooms and facilities
27002/2022/control-7.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Physical security for offices, rooms, and facilities should be designed and implemented
Show more
Securing offices, rooms and facilities
27001/2013/control-11.1.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Physical security for offices, rooms and facilities shall be designed and applied.
Show more
Security of assets off-premises
27002/2022/control-7.9
https://par-tec.github.io/security-ontologies/onto/iso#Control
Off-site assets should be protected taking into account the different risks
Show more
Security of equipment and assets off-premises
27001/2013/control-11.2.6
https://par-tec.github.io/security-ontologies/onto/iso#Control
Security shall be applied to off-site assets taking into account the different risks of working outside the organization’s premises.
Show more
Security of network
services
27001/2013/control-13.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Security mechanisms, service levels and management requirements of all network services shall be identified and included in network services agreements, whether these services are provided in-house or outsourced.
Show more
Security of network services
27002/2022/control-8.21
https://par-tec.github.io/security-ontologies/onto/iso#Control
Security mechanisms, service levels, and service requirements of network services should be identified, implemented and monitored
Show more
Segregation in networks
27001/2013/control-13.1.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Groups of information services, users and information systems shall be segregated on networks.
Show more
Segregation of duties
27002/2022/control-5.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Conflicting duties and areas of responsibility should be segregated
Show more
Segregation of duties
27001/2013/control-6.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Conflicting duties and areas of responsibility shall be segregated to reduce opportunities for unauthorized or unintentional modification or misuse of the organization’s assets.
Show more
Separation of development, test and production environments
27002/2022/control-8.31
https://par-tec.github.io/security-ontologies/onto/iso#Control
Development, testing, and production environments should be separated and secured
Show more
Separation of development, testing and operational environments
27001/2013/control-12.1.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
Development, testing, and operational environments shall be separated to reduce the risks of unauthorized access or changes to the operational environment.
Show more
Supporting utilities
27002/2022/control-7.11
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information processing facilities should be protected from power failures and other disruptions caused by failures in supporting utilities
Show more
Supporting utilities
27001/2013/control-11.2.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Equipment shall be protected from power failures and other disruptions caused by failures in supporting utilities.
Show more
System acceptance testing
27001/2013/control-14.2.9
https://par-tec.github.io/security-ontologies/onto/iso#Control
Acceptance testing programs and related criteria shall be established for new information systems, upgrades and new versions.
Show more
System change control procedures
27001/2013/control-14.2.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
Changes to systems within the development lifecycle shall be controlled by the use of formal change control procedures.
Show more
System security testing
27001/2013/control-14.2.8
https://par-tec.github.io/security-ontologies/onto/iso#Control
Testing of security functionality shall be carried out during development.
Show more
Technical compliance review
27001/2013/control-18.2.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information systems shall be regularly reviewed for compliance with the organization’s information security policies and standards.
Show more
Technical review of applications after operating platform changes
27001/2013/control-14.2.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
When operating platforms are changed, business critical applications shall be reviewed and tested to ensure there is no adverse impact on organizational operations or security.
Show more
Teleworking
27001/2013/control-6.2.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
A policy and supporting security measures shall be implemented to protect information accessed, processed or stored at teleworking sites.
Show more
Termination or change of employment responsibilities
27001/2013/control-7.3.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information security responsibilities and duties that remain valid after termination or change of employment shall be defined, communicated to the employee or contractor and enforced.
Show more
Terms and conditions of employment
27002/2022/control-6.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
The employment contractual agreements should state the personnel’s and the organization’s responsibilities for information security
Show more
Terms and conditions of employment
27001/2013/control-7.1.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
The contractual agreements with employees and contractors shall state their and the organization’s responsibilities for information security.
Show more
Test information
27002/2022/control-8.33
https://par-tec.github.io/security-ontologies/onto/iso#Control
Test information should be appropriately selected, protected and managed
Show more
Threat intelligence
27002/2022/control-5.7
https://par-tec.github.io/security-ontologies/onto/iso#Control
Information relating to information security threats should be collected and analysed to produce threat
intelligence
Show more
Unattended user equipment
27001/2013/control-11.2.8
https://par-tec.github.io/security-ontologies/onto/iso#Control
Users shall ensure that unattended equipment has appropriate protection.
Show more
Use of cryptography
27002/2022/control-8.24
https://par-tec.github.io/security-ontologies/onto/iso#Control
Rules for the effective use of cryptography, including cryptographic key management, should be defined and implemented
Show more
Use of privileged utility programs
27001/2013/control-9.4.4
https://par-tec.github.io/security-ontologies/onto/iso#Control
The use of utility programs that might be capable of overriding system and application controls shall be restricted and tightly controlled.
Show more
Use of secret authentication information
27001/2013/control-9.3.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
Users shall be required to follow the organization’s practices in the use of secret authentication information.
Show more
User access provisioning
27001/2013/control-9.2.2
https://par-tec.github.io/security-ontologies/onto/iso#Control
A formal user access provisioning process shall be implemented to assign or revoke access rights for all user types to all systems and services.
Show more
User registration and de-registration
27001/2013/control-9.2.1
https://par-tec.github.io/security-ontologies/onto/iso#Control
A formal user registration and de-registration process shall be implemented to enable assignment of access rights.
Show more
Verify, review and evaluate information security continuity
27001/2013/control-17.1.3
https://par-tec.github.io/security-ontologies/onto/iso#Control
The organization shall verify the established and implemented information security continuity controls at regular intervals in order to ensure that they are valid and effective during adverse situations.
Show more
Working in secure areas
27001/2013/control-11.1.5
https://par-tec.github.io/security-ontologies/onto/iso#Control
Procedures for working in secure areas shall be designed and applied.
Show more
Access control
27001/2013/category-9
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Asset management
27001/2013/category-8
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Communications security
27001/2013/category-13
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Compliance
27001/2013/category-18
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Cryptography
27001/2013/category-10
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Human resources security
27001/2013/category-7
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Information security aspects of business continuity management
27001/2013/category-17
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Information security incident management
27001/2013/category-16
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Information security policies
27001/2013/category-5
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Operations security
27001/2013/category-12
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Organization of information security
27001/2013/category-6
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Organizational
category-5
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
People
category-6
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Physical
category-7
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Physical and environmental security
27001/2013/category-11
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Supplier relationships
27001/2013/category-15
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
System acquisition, development and maintenance
27001/2013/category-14
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Technological
category-8
https://par-tec.github.io/security-ontologies/onto/iso#ControlCategory
Show more
Corrective
Corrective
https://par-tec.github.io/security-ontologies/onto/iso#ControlType
Show more
Detective
Detective
https://par-tec.github.io/security-ontologies/onto/iso#ControlType
Show more
Preventive
Preventive
https://par-tec.github.io/security-ontologies/onto/iso#ControlType
Show more
Detect
Detect
https://par-tec.github.io/security-ontologies/onto/iso#CybersecurityConcept
Show more
Identify
Identify
https://par-tec.github.io/security-ontologies/onto/iso#CybersecurityConcept
About |
Identify
|
rdf:type |
Cybersecurity Concepts
|
rdfs:comment |
The Identify Function assists in developing an organizational understanding to managing cybersecurity risk
to systems, people, assets, data, and capabilities.
Understanding the business context, the resources that support critical functions,
and the related cybersecurity risks enables an organization to focus and prioritize its efforts,
consistent with its risk management strategy and business needs
|
rdfs:label |
Identify
|
Show more
Protect
Protect
https://par-tec.github.io/security-ontologies/onto/iso#CybersecurityConcept
Show more
Recover
Recover
https://par-tec.github.io/security-ontologies/onto/iso#CybersecurityConcept
Show more
Respond
Respond
https://par-tec.github.io/security-ontologies/onto/iso#CybersecurityConcept
Show more
Ecosystem Cybersecurity Management
EcosystemCybersecurityManagement
https://par-tec.github.io/security-ontologies/onto/iso#GovernanceEcosystem
Show more
Availability
Availability
https://par-tec.github.io/security-ontologies/onto/iso#InformationSecurityProperty
Show more
Confidentiality
Confidentiality
https://par-tec.github.io/security-ontologies/onto/iso#InformationSecurityProperty
Show more
Integrity
Integrity
https://par-tec.github.io/security-ontologies/onto/iso#InformationSecurityProperty
Show more
Application Security
ApplicationSecurity
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
Asset Management
AssetManagement
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
Continuity
Continuity
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
Governance
Governance
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
Human Resources Security
HRSecurity
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
Identity and Access Management
IAM
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
Information Security Event Management
EventManangement
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
Information security Assurance
Assurance
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
Legal andCompliance
Compliance
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
Physical Security
PhysicalSecurity
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
Secure Configuration
SecureConfiguration
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
Supplier and Relationship Security
SupplierSecurity
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
System Network Security
SystemNetworkSecurity
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
Threat and Vulnerability Management
ThreatManagement
https://par-tec.github.io/security-ontologies/onto/iso#OperationalCapability
Show more
IT Security Administration
ITSecurityAdministration
https://par-tec.github.io/security-ontologies/onto/iso#Protection
Show more
IT Security Architecture
ITSecurityArchitecture
https://par-tec.github.io/security-ontologies/onto/iso#Protection
Show more
Backup
27001/2013/section-12.3
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Business requirements of access control
27001/2013/section-9.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Compliance with legal and contractual requirements
27001/2013/section-18.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Control of operational software
27001/2013/section-12.5
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Cryptographic controls
27001/2013/section-10.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
During employment
27001/2013/section-7.2
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Equipment
27001/2013/section-11.2
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Information classification
27001/2013/section-8.2
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Information security continuity
27001/2013/section-17.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Information security in supplier relationships
27001/2013/section-15.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Information security reviews
27001/2013/section-18.2
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Information systems audit considerations
27001/2013/section-12.7
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Information transfer
27001/2013/section-13.2
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Internal organization
27001/2013/section-6.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Logging and monitoring
27001/2013/section-12.4
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Management direction for information security
27001/2013/section-5.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Management of information security incidents and improvements
27001/2013/section-16.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Media Handling
27001/2013/section-8.3
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Mobile devices and teleworking
27001/2013/section-6.2
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Network security management
27001/2013/section-13.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Operational procedures and responsibilities
27001/2013/section-12.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Prior to employment
27001/2013/section-7.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Protection from malware
27001/2013/section-12.2
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Redundancies
27001/2013/section-17.2
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Responsibility for assets
27001/2013/section-8.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Secure areas
27001/2013/section-11.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Security in development and support processes
27001/2013/section-14.2
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Security requirements of information systems
27001/2013/section-14.1
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Supplier service delivery management
27001/2013/section-15.2
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
System and application access control
27001/2013/section-9.4
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Technical vulnerability management
27001/2013/section-12.6
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Termination and change of employment
27001/2013/section-7.3
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Test data
27001/2013/section-14.3
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
User access management
27001/2013/section-9.2
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
User responsibilities
27001/2013/section-9.3
https://par-tec.github.io/security-ontologies/onto/iso#Section
Show more
Defence and Security
Defence
https://par-tec.github.io/security-ontologies/onto/iso#SecurityDomain
Show more
Governance and Ecosystem
GovernanceEcosystem
https://par-tec.github.io/security-ontologies/onto/iso#SecurityDomain
Show more
Protection and Risk
Protection
https://par-tec.github.io/security-ontologies/onto/iso#SecurityDomain
Show more
Resilience and Recovery
Resilience
https://par-tec.github.io/security-ontologies/onto/iso#SecurityDomain
Show more
Control
Control
http://www.w3.org/2002/07/owl#Class
Show more
Control Category
ControlCategory
http://www.w3.org/2002/07/owl#Class
Show more
Cybersecurity Concepts
CybersecurityConcept
http://www.w3.org/2002/07/owl#Class
Show more
Operational Capabilities
OperationalCapability
http://www.w3.org/2002/07/owl#Class
Show more
Security Domains
SecurityDomain
http://www.w3.org/2002/07/owl#Class
Show more
hasControlCategory
hasControlCategory
http://www.w3.org/2002/07/owl#ObjectProperty
Show more
hasControlType
hasControlType
http://www.w3.org/2002/07/owl#ObjectProperty
Show more
hasInformationSecurityProperty
hasSecurityDomain
http://www.w3.org/2002/07/owl#ObjectProperty
Show more
hasOperationalCapability
hasOperationalCapability
http://www.w3.org/2002/07/owl#ObjectProperty
Show more
https://par-tec.github.io/security-ontologies/onto/iso#hasCybersecurityConcept
hasCybersecurityConcept
http://www.w3.org/2002/07/owl#ObjectProperty
Show more
https://par-tec.github.io/security-ontologies/onto/iso#
http://www.w3.org/2002/07/owl#Ontology
ISO27001 Controls Ontology
Show more
n88b4ce733c314ae997b89adc30714a33b1
n88b4ce733c314ae997b89adc30714a33b1
http://www.w3.org/2002/07/owl#Restriction
Show more
Control Type
ControlType
http://www.w3.org/2004/02/skos/core#Concept
Show more