-
PDF
- Split View
-
Views
-
Cite
Cite
Heemeng Ho, Ryan Ko, Lorraine Mazerolle, John Gilmour, Cheng Miao, Using Situational Crime Prevention (SCP)-C3 cycle and common inventory of cybersecurity controls from ISO/IEC 27002:2022 to prevent cybercrimes, Journal of Cybersecurity, Volume 10, Issue 1, 2024, tyae020, https://doi.org/10.1093/cybsec/tyae020
- Share Icon Share
Abstract
Situational Crime Prevention (SCP) is a well-documented crime prevention approach that reduces criminal opportunities for a range of different crimes. However, SCP adoption in combating cybercrimes is currently limited. Current cybersecurity controls are not mapped to crime prevention techniques, and consequently, it is hard to gauge if existing controls are actually effective in reducing crime opportunities. The dynamic environments and complex nature of cybercrimes—spanning from human-centric cyber-enabled crimes to highly technical cyber-focused crimes—exacerbate the inability to apply or measure cybersecurity controls for crime prevention effectiveness. Using best practices from the globally adopted ISO/IEC 27002:2022 standard, our paper aligns industry best-practice cybersecurity controls with the five SCP strategies and 25 techniques. We conduct a comprehensive review of 1788 peer-reviewed academic articles across computer science, criminal justice, and criminology literature using the PRISMA method. We elucidate how our common inventory of SCP-based cybersecurity controls is developed and the rationale behind the mapping of ISO/IEC controls to SCP classification. We propose our SCP-C3 (Concentrate, Comprehend, and Consider) cycle as an instrument to facilitate multi-disciplinary research in cybercrime prevention and illustrate conceptually how our SCP-C3 cycle and common inventory can be applied at intervention points in cybercrime modelling techniques in a multi-disciplinary environment.
Introduction
The Digital 2023 Global Overview Report [1] indicates that internet users have grown by 98 million over the past year, and the number of global internet users stands at 5.16 billion at the start of 2023. Cybercriminal opportunities have also grown, with the Federal Bureau of Investigation’s (FBI’s) Internet Crime Complaint Center [2] noting that cybercrime complaints have grown from almost 50 000 in 2001 to nearly 850 000 in 2021 [2, 3].
Situational Crime Prevention (SCP) is a criminological approach that seeks to prevent crimes by reducing opportunities for crimes [4]. There are 25 techniques in SCP [5], which are grouped into five main strategies, with routine activities theory [6] ‘Crime Triangle’ [7] providing a conceptual way to consider operationalization of the 25 SCP techniques. SCP has been effective in combating crimes such as robberies and vehicle crimes [8], wildlife crimes [9–12], and terrorism [13–15]. Recent research demonstrates the potential of using SCP to prevent a diverse range of cybercrimes [16]. Despite SCP’s potential and success in preventing a range of crimes, at the time of writing, SCP’s application in cybercrime prevention is rare ([16], see [17, 18] as exceptions). Cybercrimes generally comprise cyber-enabled, such as cyberbullying and cyberstalking, and cyber-focused crimes [16], such as hacking and Distributed Denial of Service (DDoS). Effective cybercrime prevention requires a multi-disciplinary understanding of human and technical elements in criminology, cybersecurity, and computer science [16, 18–20].
One way to aid a multi-disciplinary approach to cybercrime prevention is to build a common inventory of cybersecurity controls that is mapped to the 25 SCP techniques [16]. This common inventory can accommodate cybersecurity controls from a variety of industry and government cybersecurity standards and guidelines such as the International Organization for Standardization and the International Electrotechnical Commission (ISO/IEC) 27002 controls [21], National Institute of Standards and Technology (NIST) Cybersecurity Framework [22], ISACA Control Objectives for Information Technology (COBIT) [23], and the Australian Cyber Security Centre (ACSC) Essential Eight [24]. With this inventory, both criminologists and cybersecurity professionals or researchers can leverage on each other’s expertise and choose the appropriate cybersecurity controls (that are already mapped to the appropriate SCP techniques) and apply them when modelling their cybercrimes.
The research question in this study is how to create a common inventory of cybersecurity controls from cybersecurity standards that is mapped to the 25 SCP techniques. Our study provides a structured approach that maps the cybersecurity controls listed in the ISO/IEC 27002:2022 into the SCP techniques. ISO/IEC 27002 details the security controls mentioned in ISO/IEC 27001. The ISO/IEC 27001 standard is one of the most widely adopted information systems management systems (ISMS) by most organizations around the world [25]. An ISMS seeks to maintain the confidentiality, integrity, and availability of information through a risk management process and gives confidence to organizations that their risks are managed appropriately [26]. We seek to explore how to improve multi-disciplinary collaboration between criminologists and cybersecurity researchers through our SCP-C3 (Concentrate, Comprehend, and Consider) cycle and common inventory.
Our study is structured into nine main sections. The section ‘Introduction’ introduces the background, motivations, purpose, and structure of this study. In the section ‘Literature review’, we review the extant research on SCP and ISO/IEC 27001 ISMS. In the section ‘Methodology’, we describe the methodology used to search existing literature to understand how SCP techniques are applied to cybercrimes and present the results of the literature in the section ‘Results’. In the section ‘Development of common inventory’, we discuss the development of the common inventory. In the section ‘SCP-C3 cycle and common inventory’, we propose the SCP-C3 cycle to facilitate multi-disciplinary research in SCP to prevent cybercrimes. We highlight the limitations of this study and future research in the section ‘Limitations and future works’ and provide a summary of our study in the final concluding section.
Literature review
Situational Crime Prevention
Table 1 shows the 25 SCP techniques, which are distributed equally under five key strategies [5]. Clarke [4] highlighted that the SCP theoretical background originates from three environmental criminological theories, namely (i) Routine Activities Theory, which forms the basis for the Crime Triangle [6]; (ii) crime pattern theory [27]; and (iii) the rational choice perspective [28, 29]. These three theoretical perspectives complement one another because they operate at different levels of crime aggregation. Routine Activities Theory (RAT) operates at the macro-level and deals with crime opportunities at the broad societal change level. Crime pattern theory discusses how offenders discover crime opportunities in their daily lives and focuses on cities or neighbourhoods at the meso-level. Finally, the rational choice perspective operates at the micro-level and deals with individual decisions that rational offenders make when committing crimes. SCP uses these theories to understand situational precipitators [30] that can stimulate crimes [31]. The three environmental criminological theories—RAT, crime pattern, and rational choice—are applicable to the cyberspace environment, where offenders converge to rationally seek criminal opportunities in cyberplaces [32, 33].
S1 Increase the Effort . | S2 Increase the Risks . | S3 Reduce the Rewards . | S4 Reduce Provocation . | S5 Remove Excuses . |
---|---|---|---|---|
#1 Harden Target | #6 Extend Guardianship | #11 Conceal Targets | #16 Reduce Frustrations and Stress | #21 Set Rules |
#2 Control Access to Facilities | #7 Assist Natural Surveillance | #12 Remove Targets | #17 Avoid Disputes | #22 Post Instructions |
#3 Screen Exits | #8 Reduce Anonymity | #13 Identify Property | #18 Reduce Emotional Arousal | #23 Alert Conscience |
#4 Deflect Offenders | #9 Utilise Place Managers | #14 Disrupt Markets | #19 Neutralise Peer Pressure | #24 Assist Compliance |
#5 Control Tools/Weapons | #10 Strengthen Formal Surveillance | #15 Deny Benefits | #20 Discourage Imitation | #25 Control Drugs and Alcohol |
S1 Increase the Effort . | S2 Increase the Risks . | S3 Reduce the Rewards . | S4 Reduce Provocation . | S5 Remove Excuses . |
---|---|---|---|---|
#1 Harden Target | #6 Extend Guardianship | #11 Conceal Targets | #16 Reduce Frustrations and Stress | #21 Set Rules |
#2 Control Access to Facilities | #7 Assist Natural Surveillance | #12 Remove Targets | #17 Avoid Disputes | #22 Post Instructions |
#3 Screen Exits | #8 Reduce Anonymity | #13 Identify Property | #18 Reduce Emotional Arousal | #23 Alert Conscience |
#4 Deflect Offenders | #9 Utilise Place Managers | #14 Disrupt Markets | #19 Neutralise Peer Pressure | #24 Assist Compliance |
#5 Control Tools/Weapons | #10 Strengthen Formal Surveillance | #15 Deny Benefits | #20 Discourage Imitation | #25 Control Drugs and Alcohol |
Source: Cornish and Clarke [5].
S1 Increase the Effort . | S2 Increase the Risks . | S3 Reduce the Rewards . | S4 Reduce Provocation . | S5 Remove Excuses . |
---|---|---|---|---|
#1 Harden Target | #6 Extend Guardianship | #11 Conceal Targets | #16 Reduce Frustrations and Stress | #21 Set Rules |
#2 Control Access to Facilities | #7 Assist Natural Surveillance | #12 Remove Targets | #17 Avoid Disputes | #22 Post Instructions |
#3 Screen Exits | #8 Reduce Anonymity | #13 Identify Property | #18 Reduce Emotional Arousal | #23 Alert Conscience |
#4 Deflect Offenders | #9 Utilise Place Managers | #14 Disrupt Markets | #19 Neutralise Peer Pressure | #24 Assist Compliance |
#5 Control Tools/Weapons | #10 Strengthen Formal Surveillance | #15 Deny Benefits | #20 Discourage Imitation | #25 Control Drugs and Alcohol |
S1 Increase the Effort . | S2 Increase the Risks . | S3 Reduce the Rewards . | S4 Reduce Provocation . | S5 Remove Excuses . |
---|---|---|---|---|
#1 Harden Target | #6 Extend Guardianship | #11 Conceal Targets | #16 Reduce Frustrations and Stress | #21 Set Rules |
#2 Control Access to Facilities | #7 Assist Natural Surveillance | #12 Remove Targets | #17 Avoid Disputes | #22 Post Instructions |
#3 Screen Exits | #8 Reduce Anonymity | #13 Identify Property | #18 Reduce Emotional Arousal | #23 Alert Conscience |
#4 Deflect Offenders | #9 Utilise Place Managers | #14 Disrupt Markets | #19 Neutralise Peer Pressure | #24 Assist Compliance |
#5 Control Tools/Weapons | #10 Strengthen Formal Surveillance | #15 Deny Benefits | #20 Discourage Imitation | #25 Control Drugs and Alcohol |
Source: Cornish and Clarke [5].
Willison [34] first looked into how SCP can be applied to prevent information security breaches in organizations. Subsequent research [35, 36] explored how the rational choice perspective and SCP can be applied to the information security domain to understand and overcome the perpetration of employee computer crime in organizations. Beebe and Rao [37] also examined the appropriateness of using SCP to address computer crime and subsequently proposed that the combination of the meso-level application of SCP and the risk management process can reduce information security risks [38]. Other researchers expanded the use of SCP on other IT areas such as insider threat and hacking [39–42], cloud security [43], campus employee computer misuse [44], cybercrime science [45], blockchain security [46], public Wi-Fi protection [47], cyberstalking [48], risk avoidance behaviour on darknet market places [19] and automotive cybersecurity [49]. There were also researchers [35, 37, 50–52] who proposed cybersecurity controls for the SCP techniques. However, their classification of cybersecurity controls is limited, not well explained, and focused heavily on technical controls—hindering the development of a well-accepted inventory of cybersecurity controls for SCP [16].
ISO/IEC 27001 ISMS
There are many cybersecurity standards and frameworks that organizations could adopt to improve their cybersecurity postures such as the NIST Cybersecurity Framework [22], ISACA COBIT [23], and the ISO/IEC 27001. These standards are usually developed by authoritative third-party entities and organizations adopt these standards because the standards help to secure the organizations’ cybersecurity assets in a recognized manner [53, 54]. This is especially true in a globally connected world such as the global outsourcing markets, where cybersecurity solutions are not standardized due to different regulations, legislations, and risks across different industries and geographies [55].
In this study, we selected cybersecurity controls from ISO/IEC 27002:2022 for mapping to the SCP techniques. ISO/IEC 27002:2022 is aligned to cybersecurity controls listed in ISO/IEC 27001:2022 ISMS. The ISO/IEC 27001 ISMS is widely adopted globally by many organizations. The newest version of ISO/IEC 27001:2022 ISMS was published in 2022 and is mainly about editorial updates, a new clause on planning for changes, and alignment with the 27002:2022 list of cybersecurity controls [56]. The ISO/IEC 27001:2022 requirement document provides organizations with the requirements to establish, implement, maintain, and continually improve an ISMS [26]. ISO/IEC 27002:2022 details the security controls mentioned in ISO/IEC 27001:2022. ISO/IEC 27001 is ISO’s fourth largest-adopted standard certification [57]. The number of organizations that have obtained the ISO/IEC 27001 certifications has steadily increased over the years [58]. For example, the ISO 2020 Survey registered a total of 44 499 valid ISO/IEC 27001 certifications [57], which is an increase of 22% over the ISO 2019 Survey. Organizations typically seek certification to the ISO/IEC 27001 standard to assure their stakeholders that they have complied with the standard.
The ISO/IEC 27001 standard is also popularly referred to as a cybersecurity standard in research. Ramalingam et al. [59] selected the ISO/IEC 27001 standard when they proposed a novel approach to measuring effectiveness and efficiency of information technology governance, risk management, and compliance (IT-GRC) controls using the Decision Making Trial and Evaluation Laboratory (DEMATEL). Antunes et al. [60] also used data from an ISO/IEC 27001 auditing project when developing a customisable web platform cybersecurity auditing information system. Theoharidou et al. [61] compared several criminological theories, including SCP and noted that a medium relationship between SCP and ISO/IEC 17799. ISO/IEC 17999:2005 was the predecessor of ISO/IEC 27002:2005 [53, 62]. Therefore, given the wide use and popularity of ISO/IEC 27001 in research, our study aims to classify the widely adopted cybersecurity controls in ISO/IEC 27002:2022 into the 25 SCP techniques to develop a common inventory for cybercrime prevention.
Methodology
This section presents our structured approach to classifying the cybersecurity controls in ISO/IEC 27002 to SCP techniques. Our overall approach was to search prevailing literature for examples of how SCP is presently used for cybercrime prevention, using appropriate SCP keywords. The purpose of this systematic review is to understand how cybersecurity controls can be related to SCP so that during the subsequent classification process, we can map the ISO/IEC 27002 cybersecurity controls appropriately to the correct SCP strategies and techniques. Figure 1 shows the flowchart of our approach, which consists of four key steps. Our search methodology followed the Preferred Reporting Items for Systematic Reviews and Meta-Analyses (PRISMA) 2020 flow diagram [63]. PRISMA aims to assist authors in improving the quality of reporting of systematic reviews and meta-analyses [64]. We used this method to ensure that the searches followed a robust framework with clear methods of how searches were conducted, as well as to ensure that the results are reproducible. The search results were then identified, screened, assessed for eligibility, and finally included for analysis using the PRISMA 2020 flow diagram, which is available in Appendix A.

Flowchart on structured approach for ISO/IEC 27002:2022 classification.
We began our first step in Fig. 1 by choosing the appropriate research databases to perform the PRISMA review. We selected three research databases, namely the ACM Digital Library, IEEE Xplore, and Criminal Justice Abstracts EBSCO (CJA) because they are acknowledged and known for quality publications in computer science, cybersecurity, and criminology. Many of the publications in these databases are highlighted in the 2022 Journal Citation Reports [65] and ranked by the Computing Research and Education Association of Australasia (CORE) [66]. We completed this PRISMA review in February 2023.
Our second step identified the appropriate keywords to search for in the research databases. We broke down the SCP techniques into suitable keywords for searching. The SCP techniques in Table 1 generally followed a verb and noun structure. For example, SCP technique ‘#1 Harden targets’ comprised the words ‘harden’, which is a verb, and ‘targets’, which is a noun. Our keyword searches were made of a combination of (i) ‘Verb Noun’, and (ii) ‘Cyber’ AND ‘Noun’, where AND is an operator. The former keyword explicitly spelled out the actual SCP techniques, while the latter searched for cyber-related SCP articles. Hence, for the SCP technique ‘#1 Harden targets’, we searched for the keywords (i) ‘harden targets’ and (ii) ‘cyber’ AND ‘targets’. There were instances where the search resulted in few or no articles. In such scenarios, we supplemented the search with keywords that were more general: (iii) ‘Verb’ AND ‘Noun’ and (iv) ‘Noun’ itself. However, such general keywords can result in hundreds or thousands of articles. For example, the general keyword ‘targets’ resulted in more than 20 000 articles. Hence, we concentrated our reviews on the first two keyword searches, which were more explicit and targeted, and supplemented them with the last two keywords where necessary. Next, in Step 3, detailed in the section ‘Results’, we reviewed the search results of the existing research on the application of SCP techniques in cybercrimes. After which, in Step 4, detailed in the section ‘Development of common inventory’, we classified the ISO/IEC 27002:2022 controls into the 25 SCP techniques. We provide the list of articles returned from our PRISMA search at: https://doi.org/10.48610/71aa67b.
We selected the keyword approaches above of (i) ‘Verb Noun’ because, to the best of our knowledge, there have not been any focused systematic reviews that examine in detail the application of SCP in this manner. As SCP techniques are reflected in its ‘Verb Noun’ structure, the selection of such keywords is fundamental to the focused systematic review of SCP, and the results can provide relevant and appropriate selection of articles that are specifically based on the individual SCP techniques. Our selection of keywords using (ii) ‘Cyber’ AND ‘Noun’ is a general synonym structure where we look for SCP articles that are related to cyber. The choice of ‘Cyber’ as the synonym is because we want to gain insights on how SCP techniques are presently used in cyberspace or cyber-related matters, which will allow us to classify the ISO/IEC 27002:2022 cybersecurity controls more appropriately to the SCP strategies and techniques. There are other possible synonyms that can be used to widen the scope of the review. One way is to use synonyms for each individual SCP technique and strategy, such as synonyms for the keywords ‘harden’ and ‘targets’. However, we did not do so because our current selection of keywords had already resulted in a large set of eligible articles to review (see the section ‘Results’). For a more thorough literature review of each individual SCP strategy and technique, future research could look into selecting keywords that are a permutation of relevant and appropriate synonyms of each individual SCP strategy or technique.
Results
In this section, we present an overview of the search results. Subsequently, we present the search results for each individual SCP strategy and technique. We then discuss the findings from the search results.
Overview of results
We screened 1788 eligible articles following our search methodology. The breakdown of the number of eligible articles for each SCP strategy is shown in Table 2. Following the PRISMA 2020 flow diagram (see Appendix A), we excluded inapplicable articles such as those that were duplicated, not in English, and did not have any research content, like court transcripts, interviews, and book reviews. We then reviewed the remaining articles.
SCP strategy . | ACM Digital Library . | IEEEXplore . | CJA . | Total . |
---|---|---|---|---|
S1 Increase the Efforts | 221 | 342 | 88 | 651 |
S2 Increase the Risks | 11 | 175 | 123 | 309 |
S3 Reduce the Rewards | 19 | 123 | 19 | 161 |
S4 Reduce Provocation | 175 | 166 | 98 | 439 |
S5 Remove Excuses | 106 | 91 | 31 | 228 |
Total: | 532 | 897 | 359 | 1788 |
SCP strategy . | ACM Digital Library . | IEEEXplore . | CJA . | Total . |
---|---|---|---|---|
S1 Increase the Efforts | 221 | 342 | 88 | 651 |
S2 Increase the Risks | 11 | 175 | 123 | 309 |
S3 Reduce the Rewards | 19 | 123 | 19 | 161 |
S4 Reduce Provocation | 175 | 166 | 98 | 439 |
S5 Remove Excuses | 106 | 91 | 31 | 228 |
Total: | 532 | 897 | 359 | 1788 |
SCP strategy . | ACM Digital Library . | IEEEXplore . | CJA . | Total . |
---|---|---|---|---|
S1 Increase the Efforts | 221 | 342 | 88 | 651 |
S2 Increase the Risks | 11 | 175 | 123 | 309 |
S3 Reduce the Rewards | 19 | 123 | 19 | 161 |
S4 Reduce Provocation | 175 | 166 | 98 | 439 |
S5 Remove Excuses | 106 | 91 | 31 | 228 |
Total: | 532 | 897 | 359 | 1788 |
SCP strategy . | ACM Digital Library . | IEEEXplore . | CJA . | Total . |
---|---|---|---|---|
S1 Increase the Efforts | 221 | 342 | 88 | 651 |
S2 Increase the Risks | 11 | 175 | 123 | 309 |
S3 Reduce the Rewards | 19 | 123 | 19 | 161 |
S4 Reduce Provocation | 175 | 166 | 98 | 439 |
S5 Remove Excuses | 106 | 91 | 31 | 228 |
Total: | 532 | 897 | 359 | 1788 |
The objective of our analysis of the eligible articles was to look into how SCP techniques were currently applied in the existing research literature to prevent cybercrimes. We started by analysing articles that were relevant to the application of SCP and its techniques to cybercrimes. We also looked separately at Cornish and Clarke’s [5] original definitions as well as the explanation provided by Smith and Clarke [31] and Eck and Clarke [67] on how to apply SCP to reduce criminal opportunities for crimes. We then combined both to arrive at a suitable interpretation of how SCP techniques can be adapted to be cyber relevant and prevent cybercrimes.
Search results
We present Table 3, which shows the number of eligible and relevant articles for the 25 SCP techniques, grouped under their respective SCP strategies.
. | Eligible . | Relevant . |
---|---|---|
‘S1 Increase the Effort’ | ||
#1 Harden Targets | 33 | 1 |
#2 Control Access to Facilities | 67 | 1 |
#3 Screen Exits | 75 | 0 |
#4 Deflect Offenders | 61 | 1 |
#5 Control Tools/Weapons | 415 | 1 |
‘S2 Increase the Risks’ | ||
#6 Extend Guardianship | 135 | 6 |
#7 Assist Natural Surveillance | 35 | 4 |
#8 Reduce Anonymity | 94 | 2 |
#9 Utilise Place Managers | 10 | 1 |
#10 Strengthen Formal Surveillance | 35 | 4 |
‘S3 Reduce the Rewards’ | ||
#11 Conceal Targets | 32 | 1 |
#12 Remove Targets | 33 | 1 |
#13 Identify Property | 41 | 0 |
#14 Disrupt Markets | 40 | 0 |
#15 Deny Benefits | 15 | 0 |
‘S4 Reduce Provocations’ | ||
#16 Reduce Frustrations and Stress | 73 | 2 |
#17 Avoid Disputes | 136 | 3 |
#18 Reduce Emotional Arousal | 31 | 1 |
#19 Neutralise Peer Pressure | 48 | 0 |
#20 Discourage Imitation | 151 | 0 |
‘S5 Remove Excuses’ | ||
#21 Set Rules | 77 | 2 |
#22 Post Instructions | 20 | 0 |
#23 Alert Conscience | 35 | 0 |
#24 Assist Compliance | 22 | 11 |
#25 Control Drugs and Alcohol | 74 | 11 |
Total: | 1788 | 53 |
. | Eligible . | Relevant . |
---|---|---|
‘S1 Increase the Effort’ | ||
#1 Harden Targets | 33 | 1 |
#2 Control Access to Facilities | 67 | 1 |
#3 Screen Exits | 75 | 0 |
#4 Deflect Offenders | 61 | 1 |
#5 Control Tools/Weapons | 415 | 1 |
‘S2 Increase the Risks’ | ||
#6 Extend Guardianship | 135 | 6 |
#7 Assist Natural Surveillance | 35 | 4 |
#8 Reduce Anonymity | 94 | 2 |
#9 Utilise Place Managers | 10 | 1 |
#10 Strengthen Formal Surveillance | 35 | 4 |
‘S3 Reduce the Rewards’ | ||
#11 Conceal Targets | 32 | 1 |
#12 Remove Targets | 33 | 1 |
#13 Identify Property | 41 | 0 |
#14 Disrupt Markets | 40 | 0 |
#15 Deny Benefits | 15 | 0 |
‘S4 Reduce Provocations’ | ||
#16 Reduce Frustrations and Stress | 73 | 2 |
#17 Avoid Disputes | 136 | 3 |
#18 Reduce Emotional Arousal | 31 | 1 |
#19 Neutralise Peer Pressure | 48 | 0 |
#20 Discourage Imitation | 151 | 0 |
‘S5 Remove Excuses’ | ||
#21 Set Rules | 77 | 2 |
#22 Post Instructions | 20 | 0 |
#23 Alert Conscience | 35 | 0 |
#24 Assist Compliance | 22 | 11 |
#25 Control Drugs and Alcohol | 74 | 11 |
Total: | 1788 | 53 |
. | Eligible . | Relevant . |
---|---|---|
‘S1 Increase the Effort’ | ||
#1 Harden Targets | 33 | 1 |
#2 Control Access to Facilities | 67 | 1 |
#3 Screen Exits | 75 | 0 |
#4 Deflect Offenders | 61 | 1 |
#5 Control Tools/Weapons | 415 | 1 |
‘S2 Increase the Risks’ | ||
#6 Extend Guardianship | 135 | 6 |
#7 Assist Natural Surveillance | 35 | 4 |
#8 Reduce Anonymity | 94 | 2 |
#9 Utilise Place Managers | 10 | 1 |
#10 Strengthen Formal Surveillance | 35 | 4 |
‘S3 Reduce the Rewards’ | ||
#11 Conceal Targets | 32 | 1 |
#12 Remove Targets | 33 | 1 |
#13 Identify Property | 41 | 0 |
#14 Disrupt Markets | 40 | 0 |
#15 Deny Benefits | 15 | 0 |
‘S4 Reduce Provocations’ | ||
#16 Reduce Frustrations and Stress | 73 | 2 |
#17 Avoid Disputes | 136 | 3 |
#18 Reduce Emotional Arousal | 31 | 1 |
#19 Neutralise Peer Pressure | 48 | 0 |
#20 Discourage Imitation | 151 | 0 |
‘S5 Remove Excuses’ | ||
#21 Set Rules | 77 | 2 |
#22 Post Instructions | 20 | 0 |
#23 Alert Conscience | 35 | 0 |
#24 Assist Compliance | 22 | 11 |
#25 Control Drugs and Alcohol | 74 | 11 |
Total: | 1788 | 53 |
. | Eligible . | Relevant . |
---|---|---|
‘S1 Increase the Effort’ | ||
#1 Harden Targets | 33 | 1 |
#2 Control Access to Facilities | 67 | 1 |
#3 Screen Exits | 75 | 0 |
#4 Deflect Offenders | 61 | 1 |
#5 Control Tools/Weapons | 415 | 1 |
‘S2 Increase the Risks’ | ||
#6 Extend Guardianship | 135 | 6 |
#7 Assist Natural Surveillance | 35 | 4 |
#8 Reduce Anonymity | 94 | 2 |
#9 Utilise Place Managers | 10 | 1 |
#10 Strengthen Formal Surveillance | 35 | 4 |
‘S3 Reduce the Rewards’ | ||
#11 Conceal Targets | 32 | 1 |
#12 Remove Targets | 33 | 1 |
#13 Identify Property | 41 | 0 |
#14 Disrupt Markets | 40 | 0 |
#15 Deny Benefits | 15 | 0 |
‘S4 Reduce Provocations’ | ||
#16 Reduce Frustrations and Stress | 73 | 2 |
#17 Avoid Disputes | 136 | 3 |
#18 Reduce Emotional Arousal | 31 | 1 |
#19 Neutralise Peer Pressure | 48 | 0 |
#20 Discourage Imitation | 151 | 0 |
‘S5 Remove Excuses’ | ||
#21 Set Rules | 77 | 2 |
#22 Post Instructions | 20 | 0 |
#23 Alert Conscience | 35 | 0 |
#24 Assist Compliance | 22 | 11 |
#25 Control Drugs and Alcohol | 74 | 11 |
Total: | 1788 | 53 |
SCP strategy ‘S1 Increase the Efforts’ comprises five SCP techniques that increase the efforts needed by criminal offenders by either blocking or limiting their actions or movements [5, 31, 67]. SCP technique ‘#1 Harden Targets’ makes it more difficult for the offender to get to or use the target to achieve their criminal ends. An example would be using a steering wheel lock to make it harder for criminals to steal a vehicle. SCP technique ‘#2 Control Access to Facilities’ aims to block access to places where an offender can carry out their criminal actions, such as having fences and gates. SCP technique ‘#3 Screen Exits’ makes it difficult for offenders to leave a place after they complete their criminal action or when they want to remove their criminal proceeds, such as needing a valid ticket/pass to exit a building. SCP technique ‘#4 Deflect Offenders’ changes offender existing or potential movement patterns, such as having separate bathrooms for different genders. SCP technique ‘#5 Control Tools/Weapons’ limits offender access to or use of instruments that are associated with their modus operandi, such as controlling or banning guns. When reviewing the eligible articles for relevancy, we examined whether the articles discussed the application of SCP to prevent cybercrimes and whether the articles provided insights on how SCP can be used according to the SCP technique description described by Smith and Clarke [31], as discussed in this paragraph. The insights obtained from this review can aid in the subsequent classification of the ISO/IEC 27002:2022 controls to SCP strategies and techniques.
For the SCP technique ‘#1 Harden Targets’, there were 33 eligible articles for review. However, we only identified one relevant article, by Miró-Llinares et al. [68], which discussed using a comparative research design to investigate cyber victims as cybercrime targets using routine activity theory. Their work concluded that cyber victimization should focus on identifying nuances of online users’ daily activities instead of the broader constructs of interactions and visibilities. The remainder of the articles mainly discussed research topics related to moving target defence (MTD) for cyber-physical systems, which is about changing the attack surface areas of a system to limit information gained from reconnaissance (John et al., 2014) and making computer networks less homogeneous, less static, and less deterministic to increase attack complexities (Priest et al., 2015). These articles were not identified as relevant because they did not discuss the application of SCP into cybercrimes or hardening the targets [31].
For the SCP technique ‘#2 Control Access to Facilities’, there were 67 eligible articles for review. We identified only one article as relevant: Zhang et al. [69], who suggested using wireless personal devices such as mobile phones as a two-factor authentication device to control access to facilities. The remaining articles mainly discussed facilities-related topics such as controlling and preventing infections at healthcare facilities and were therefore not relevant because they did not discuss the application of SCP to cybercrimes or were about blocking offender access to facilities [31].
For the SCP technique ‘#3 Screen Exits’, there were 75 eligible articles for review. However, we did not identify any relevant articles. The articles mainly discussed research topics related to Deep Neural Networks and computer programming, algorithms and architecture and were therefore not relevant because they did not discuss the application of SCP into cybercrimes or were about making it difficult for offenders to leave a place with their proceeds after a criminal event [31].
For the SCP technique ‘#4 Deflect Offenders’, there were 61 eligible articles for review. There was one relevant paper by Willison [70] who discussed the feasibility of applying SCP techniques and crime scripts [71] to combat cybercrimes. The remaining articles mainly discussed research topics related to the analysis, identification, detection, and attributes of offenders, such as their profiles, and were therefore not relevant because they neither discussed the application of SCP into cybercrimes nor discussed deflecting or changing offender movement patterns [31].
For the SCP technique ‘#5 Control Tools/Weapons’, there were 415 eligible articles for review. There was one relevant paper by Prunckun [72], who discussed how information and communication technology can be used as cyber weapons and argued that there was a need to legislate cyber weapons in order to control their misuse for criminal purposes. The remaining articles mainly discussed research topics related to conventional weapon systems and cyber-physical systems and were therefore not relevant because they neither discussed the application of SCP into cybercrimes nor discussed limiting offender access to or the use of instruments in committing cybercrimes [31].
For the remaining SCP strategies and associated techniques, see Appendix B for a more detailed discussion of their purpose and description of their relevant articles.
Analysis of search results
We present an analysis of our search results in Table 4 and Fig. 2.

Pie chart on breakdown of number of relevant articles for the five SCP strategies.
SCP Strategy . | Eligible Articles . | Relevant Articles . | |
---|---|---|---|
. | . | No. . | % . |
S1 Increase the Efforts | 651 | 4 | 8 |
S2 Increase the Risks | 309 | 17 | 32 |
S3 Reduce the Rewards | 161 | 2 | 4 |
S4 Reduce Provocation | 439 | 6 | 11 |
S5 Remove Excuses | 228 | 24 | 45 |
Total: | 1788 | 53 | 100 |
SCP Strategy . | Eligible Articles . | Relevant Articles . | |
---|---|---|---|
. | . | No. . | % . |
S1 Increase the Efforts | 651 | 4 | 8 |
S2 Increase the Risks | 309 | 17 | 32 |
S3 Reduce the Rewards | 161 | 2 | 4 |
S4 Reduce Provocation | 439 | 6 | 11 |
S5 Remove Excuses | 228 | 24 | 45 |
Total: | 1788 | 53 | 100 |
SCP Strategy . | Eligible Articles . | Relevant Articles . | |
---|---|---|---|
. | . | No. . | % . |
S1 Increase the Efforts | 651 | 4 | 8 |
S2 Increase the Risks | 309 | 17 | 32 |
S3 Reduce the Rewards | 161 | 2 | 4 |
S4 Reduce Provocation | 439 | 6 | 11 |
S5 Remove Excuses | 228 | 24 | 45 |
Total: | 1788 | 53 | 100 |
SCP Strategy . | Eligible Articles . | Relevant Articles . | |
---|---|---|---|
. | . | No. . | % . |
S1 Increase the Efforts | 651 | 4 | 8 |
S2 Increase the Risks | 309 | 17 | 32 |
S3 Reduce the Rewards | 161 | 2 | 4 |
S4 Reduce Provocation | 439 | 6 | 11 |
S5 Remove Excuses | 228 | 24 | 45 |
Total: | 1788 | 53 | 100 |
As Table 4 shows, there are only 53 relevant articles out of 1788 (3.1%) eligible articles that discuss the application of SCP into cybercrimes. Our findings are in line with prevailing research that indicates that SCP is not widely applied in cybercrime prevention [16–18].
Our SCP search methodology used the actual naming of SCP techniques as keywords (such as ‘Harden Targets’). Based on these keywords, the bulk of the articles focused on SCP strategies ‘S5 Remove Excuses’ (24 relevant articles or 45%) and ‘S2 Increase the Risks’ (17 relevant articles or 32%). The former presents techniques that clarify the responsibility of potential offenders in a setting, while the latter focuses on increasing the risks of detection for potential offenders.
SCP strategy ‘S3 Reduce the Rewards’, which focuses on techniques that reduce the rewards of crimes for offenders had the fewest number of relevant articles (2% or 4%). This is followed by SCP strategy ‘S1 Increase the Efforts’ (4% or 8%), which increases the efforts of offenders by either blocking or limiting their actions or movements; and SCP strategy ‘S4 Reduce Provocations’ (6% or 11%), which focuses on limiting provocative situation stimuli.
Development of common inventory
In this section, we seek to develop a common inventory of cybersecurity controls to facilitate multi-disciplinary research in cybercrime prevention using SCP. Cybersecurity and criminology researchers can use the mapped controls when designing appropriate intervention measures for cybercrimes. Our study classifies the 93 controls from ISO/IEC 27002:2022 into the 25 SCP techniques. The 93 controls in ISO/IEC 27002:2022 are divided into four sets of control clauses:
37 organizational controls that focus on the cybersecurity posture for organizations.
8 people controls, which focus on human resource matters such as employee background checks.
14 physical controls that focus on physical security such as physical perimeters.
34 technological controls, which focus on using technology to secure information assets.
We classified each ISO/IEC control into the most appropriate SCP technique within a single SCP strategy and did not classify an ISO/IEC control into more than one SCP strategy to prevent duplication.
‘S1 Increase the Efforts’
From our understanding of SCP in the previous sections, we begin by classifying the first SCP strategy ‘S1 Increase the Efforts’ and its associated SCP techniques in Table 5 and briefly explain our reasons for the classification. The column on ‘ISO/IEC Control’ in Table 5 is the title of the ISO/IEC control from the ISO/IEC 27002:2022, and as such, provides a brief description. A more thorough explanation of the ISO/IEC controls such as the controls’ description and purpose, and a more thorough explanation on the rationale of our classification are presented in Appendix C.
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#01 Harden Targets | Organizational | 5.08 Information security in project management |
#01 Harden Targets | Organizational | 5.19 Information security in supplier relationships |
#01 Harden Targets | Organizational | 5.20 Addressing information security within supplier agreements |
#01 Harden Targets | Organizational | 5.21 Managing information security in the ICT supply chain |
#01 Harden Targets | Organizational | 5.23 Information security for use of cloud services |
#01 Harden Targets | Organizational | 5.27 Learning from information security incidents |
#01 Harden Targets | Organizational | 5.29 Information security during disruption |
#01 Harden Targets | Organizational | 5.33 Protection of records |
#01 Harden Targets | Organizational | 5.35 Independent review of information security |
#01 Harden Targets | People | 6.07 Remote working |
#01 Harden Targets | Physical | 7.03 Securing offices, rooms and facilities |
#01 Harden Targets | Physical | 7.05 Protecting against physical and environmental threats |
#01 Harden Targets | Physical | 7.06 Working in secure areas |
#01 Harden Targets | Physical | 7.08 Equipment siting and protection |
#01 Harden Targets | Physical | 7.09 Security of assets off-premises |
#01 Harden Targets | Physical | 7.10 Storage media |
#01 Harden Targets | Physical | 7.11 Supporting utilities |
#01 Harden Targets | Physical | 7.12 Cabling security |
#01 Harden Targets | Physical | 7.13 Equipment maintenance |
#01 Harden Targets | Technological | 8.01 User endpoint devices |
#01 Harden Targets | Technological | 8.07 Protection against malware |
#01 Harden Targets | Technological | 8.08 Management of technical vulnerabilities |
#01 Harden Targets | Technological | 8.09 Configuration management |
#01 Harden Targets | Technological | 8.23 Web filtering |
#01 Harden Targets | Technological | 8.25 Secure development life cycle |
#01 Harden Targets | Technological | 8.26 Application security requirements |
#01 Harden Targets | Technological | 8.27 Secure system architecture and engineering principles |
#01 Harden Targets | Technological | 8.28 Secure coding |
#01 Harden Targets | Technological | 8.29 Security testing in development and acceptance |
#01 Harden Targets | Technological | 8.30 Outsourced development |
#01 Harden Targets | Technological | 8.32 Change management |
#01 Harden Targets | Technological | 8.33 Test information |
#01 Harden Targets | Technological | 8.34 Protection of information systems during audit testing |
#02 Control Access to Facilities | Organizational | 5.11 Return of assets |
#02 Control Access to Facilities | Organizational | 5.15 Access control |
#02 Control Access to Facilities | Organizational | 5.18 Access rights |
#02 Control Access to Facilities | Physical | 7.01 Physical security perimeters |
#02 Control Access to Facilities | Physical | 7.02 Physical entry |
#02 Control Access to Facilities | Technological | 8.02 Privileged access rights |
#02 Control Access to Facilities | Technological | 8.20 Networks security |
#02 Control Access to Facilities | Technological | 8.21 Security of network services |
#03 Screen Exits | Technological | 8.12 Data leakage prevention |
#04 Deflect Offenders | Technological | 8.22 Segregation of networks |
#04 Deflect Offenders | Technological | 8.31 Separation of development, test and production environments |
#05 Control Tools/Weapons | Technological | 8.18 Use of privileged utility programs |
#05 Control Tools/Weapons | Technological | 8.19 Installation of software on operational systems |
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#01 Harden Targets | Organizational | 5.08 Information security in project management |
#01 Harden Targets | Organizational | 5.19 Information security in supplier relationships |
#01 Harden Targets | Organizational | 5.20 Addressing information security within supplier agreements |
#01 Harden Targets | Organizational | 5.21 Managing information security in the ICT supply chain |
#01 Harden Targets | Organizational | 5.23 Information security for use of cloud services |
#01 Harden Targets | Organizational | 5.27 Learning from information security incidents |
#01 Harden Targets | Organizational | 5.29 Information security during disruption |
#01 Harden Targets | Organizational | 5.33 Protection of records |
#01 Harden Targets | Organizational | 5.35 Independent review of information security |
#01 Harden Targets | People | 6.07 Remote working |
#01 Harden Targets | Physical | 7.03 Securing offices, rooms and facilities |
#01 Harden Targets | Physical | 7.05 Protecting against physical and environmental threats |
#01 Harden Targets | Physical | 7.06 Working in secure areas |
#01 Harden Targets | Physical | 7.08 Equipment siting and protection |
#01 Harden Targets | Physical | 7.09 Security of assets off-premises |
#01 Harden Targets | Physical | 7.10 Storage media |
#01 Harden Targets | Physical | 7.11 Supporting utilities |
#01 Harden Targets | Physical | 7.12 Cabling security |
#01 Harden Targets | Physical | 7.13 Equipment maintenance |
#01 Harden Targets | Technological | 8.01 User endpoint devices |
#01 Harden Targets | Technological | 8.07 Protection against malware |
#01 Harden Targets | Technological | 8.08 Management of technical vulnerabilities |
#01 Harden Targets | Technological | 8.09 Configuration management |
#01 Harden Targets | Technological | 8.23 Web filtering |
#01 Harden Targets | Technological | 8.25 Secure development life cycle |
#01 Harden Targets | Technological | 8.26 Application security requirements |
#01 Harden Targets | Technological | 8.27 Secure system architecture and engineering principles |
#01 Harden Targets | Technological | 8.28 Secure coding |
#01 Harden Targets | Technological | 8.29 Security testing in development and acceptance |
#01 Harden Targets | Technological | 8.30 Outsourced development |
#01 Harden Targets | Technological | 8.32 Change management |
#01 Harden Targets | Technological | 8.33 Test information |
#01 Harden Targets | Technological | 8.34 Protection of information systems during audit testing |
#02 Control Access to Facilities | Organizational | 5.11 Return of assets |
#02 Control Access to Facilities | Organizational | 5.15 Access control |
#02 Control Access to Facilities | Organizational | 5.18 Access rights |
#02 Control Access to Facilities | Physical | 7.01 Physical security perimeters |
#02 Control Access to Facilities | Physical | 7.02 Physical entry |
#02 Control Access to Facilities | Technological | 8.02 Privileged access rights |
#02 Control Access to Facilities | Technological | 8.20 Networks security |
#02 Control Access to Facilities | Technological | 8.21 Security of network services |
#03 Screen Exits | Technological | 8.12 Data leakage prevention |
#04 Deflect Offenders | Technological | 8.22 Segregation of networks |
#04 Deflect Offenders | Technological | 8.31 Separation of development, test and production environments |
#05 Control Tools/Weapons | Technological | 8.18 Use of privileged utility programs |
#05 Control Tools/Weapons | Technological | 8.19 Installation of software on operational systems |
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#01 Harden Targets | Organizational | 5.08 Information security in project management |
#01 Harden Targets | Organizational | 5.19 Information security in supplier relationships |
#01 Harden Targets | Organizational | 5.20 Addressing information security within supplier agreements |
#01 Harden Targets | Organizational | 5.21 Managing information security in the ICT supply chain |
#01 Harden Targets | Organizational | 5.23 Information security for use of cloud services |
#01 Harden Targets | Organizational | 5.27 Learning from information security incidents |
#01 Harden Targets | Organizational | 5.29 Information security during disruption |
#01 Harden Targets | Organizational | 5.33 Protection of records |
#01 Harden Targets | Organizational | 5.35 Independent review of information security |
#01 Harden Targets | People | 6.07 Remote working |
#01 Harden Targets | Physical | 7.03 Securing offices, rooms and facilities |
#01 Harden Targets | Physical | 7.05 Protecting against physical and environmental threats |
#01 Harden Targets | Physical | 7.06 Working in secure areas |
#01 Harden Targets | Physical | 7.08 Equipment siting and protection |
#01 Harden Targets | Physical | 7.09 Security of assets off-premises |
#01 Harden Targets | Physical | 7.10 Storage media |
#01 Harden Targets | Physical | 7.11 Supporting utilities |
#01 Harden Targets | Physical | 7.12 Cabling security |
#01 Harden Targets | Physical | 7.13 Equipment maintenance |
#01 Harden Targets | Technological | 8.01 User endpoint devices |
#01 Harden Targets | Technological | 8.07 Protection against malware |
#01 Harden Targets | Technological | 8.08 Management of technical vulnerabilities |
#01 Harden Targets | Technological | 8.09 Configuration management |
#01 Harden Targets | Technological | 8.23 Web filtering |
#01 Harden Targets | Technological | 8.25 Secure development life cycle |
#01 Harden Targets | Technological | 8.26 Application security requirements |
#01 Harden Targets | Technological | 8.27 Secure system architecture and engineering principles |
#01 Harden Targets | Technological | 8.28 Secure coding |
#01 Harden Targets | Technological | 8.29 Security testing in development and acceptance |
#01 Harden Targets | Technological | 8.30 Outsourced development |
#01 Harden Targets | Technological | 8.32 Change management |
#01 Harden Targets | Technological | 8.33 Test information |
#01 Harden Targets | Technological | 8.34 Protection of information systems during audit testing |
#02 Control Access to Facilities | Organizational | 5.11 Return of assets |
#02 Control Access to Facilities | Organizational | 5.15 Access control |
#02 Control Access to Facilities | Organizational | 5.18 Access rights |
#02 Control Access to Facilities | Physical | 7.01 Physical security perimeters |
#02 Control Access to Facilities | Physical | 7.02 Physical entry |
#02 Control Access to Facilities | Technological | 8.02 Privileged access rights |
#02 Control Access to Facilities | Technological | 8.20 Networks security |
#02 Control Access to Facilities | Technological | 8.21 Security of network services |
#03 Screen Exits | Technological | 8.12 Data leakage prevention |
#04 Deflect Offenders | Technological | 8.22 Segregation of networks |
#04 Deflect Offenders | Technological | 8.31 Separation of development, test and production environments |
#05 Control Tools/Weapons | Technological | 8.18 Use of privileged utility programs |
#05 Control Tools/Weapons | Technological | 8.19 Installation of software on operational systems |
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#01 Harden Targets | Organizational | 5.08 Information security in project management |
#01 Harden Targets | Organizational | 5.19 Information security in supplier relationships |
#01 Harden Targets | Organizational | 5.20 Addressing information security within supplier agreements |
#01 Harden Targets | Organizational | 5.21 Managing information security in the ICT supply chain |
#01 Harden Targets | Organizational | 5.23 Information security for use of cloud services |
#01 Harden Targets | Organizational | 5.27 Learning from information security incidents |
#01 Harden Targets | Organizational | 5.29 Information security during disruption |
#01 Harden Targets | Organizational | 5.33 Protection of records |
#01 Harden Targets | Organizational | 5.35 Independent review of information security |
#01 Harden Targets | People | 6.07 Remote working |
#01 Harden Targets | Physical | 7.03 Securing offices, rooms and facilities |
#01 Harden Targets | Physical | 7.05 Protecting against physical and environmental threats |
#01 Harden Targets | Physical | 7.06 Working in secure areas |
#01 Harden Targets | Physical | 7.08 Equipment siting and protection |
#01 Harden Targets | Physical | 7.09 Security of assets off-premises |
#01 Harden Targets | Physical | 7.10 Storage media |
#01 Harden Targets | Physical | 7.11 Supporting utilities |
#01 Harden Targets | Physical | 7.12 Cabling security |
#01 Harden Targets | Physical | 7.13 Equipment maintenance |
#01 Harden Targets | Technological | 8.01 User endpoint devices |
#01 Harden Targets | Technological | 8.07 Protection against malware |
#01 Harden Targets | Technological | 8.08 Management of technical vulnerabilities |
#01 Harden Targets | Technological | 8.09 Configuration management |
#01 Harden Targets | Technological | 8.23 Web filtering |
#01 Harden Targets | Technological | 8.25 Secure development life cycle |
#01 Harden Targets | Technological | 8.26 Application security requirements |
#01 Harden Targets | Technological | 8.27 Secure system architecture and engineering principles |
#01 Harden Targets | Technological | 8.28 Secure coding |
#01 Harden Targets | Technological | 8.29 Security testing in development and acceptance |
#01 Harden Targets | Technological | 8.30 Outsourced development |
#01 Harden Targets | Technological | 8.32 Change management |
#01 Harden Targets | Technological | 8.33 Test information |
#01 Harden Targets | Technological | 8.34 Protection of information systems during audit testing |
#02 Control Access to Facilities | Organizational | 5.11 Return of assets |
#02 Control Access to Facilities | Organizational | 5.15 Access control |
#02 Control Access to Facilities | Organizational | 5.18 Access rights |
#02 Control Access to Facilities | Physical | 7.01 Physical security perimeters |
#02 Control Access to Facilities | Physical | 7.02 Physical entry |
#02 Control Access to Facilities | Technological | 8.02 Privileged access rights |
#02 Control Access to Facilities | Technological | 8.20 Networks security |
#02 Control Access to Facilities | Technological | 8.21 Security of network services |
#03 Screen Exits | Technological | 8.12 Data leakage prevention |
#04 Deflect Offenders | Technological | 8.22 Segregation of networks |
#04 Deflect Offenders | Technological | 8.31 Separation of development, test and production environments |
#05 Control Tools/Weapons | Technological | 8.18 Use of privileged utility programs |
#05 Control Tools/Weapons | Technological | 8.19 Installation of software on operational systems |
SCP strategy ‘S1 Increase the Efforts’ increases the efforts needed by offenders (such as cybercriminals and malware) and makes it more difficult for them to commit criminal actions by blocking or limiting offender actions or movements [31]. With this in mind, we classify a total of 46 ISO/IEC controls in Table 5 for this SCP strategy. We explain more about SCP vocabularies in the cyberspace context, such as malware as offenders, in the subsequent section ‘SCP-C3 cycle and common inventory’.
The SCP technique ‘#1 Harden Targets’ aims to make it more difficult for offenders (such as cybercriminals and malware) to get to or use the target (such as computing devices and virtual artefacts like data) to achieve their cybercriminal purposes (such as hacking and ransomware). Therefore, the ISO/IEC controls such as mandating information security in project management (ISO/IEC 27002 Clause 5.08; for brevity, we will use the ‘ISO/IEC number’ notation to depict ISO/IEC 27002 clauses), supplier agreements and relationships (ISO/IEC 5.19, 5.20), ICT supply chain (ISO/IEC 5.21), and cloud security (ISO/IEC 5.23) harden these targets and make it difficult for cybercriminals to achieve their purposes. Likewise, protective actions such as securing records (ISO/IEC 5.33), offices (ISO/IEC 7.3), secure areas (ISO/IEC 7.6), equipment (ISO/IEC 7.8), and storage media (ISO/IEC 7.10) also harden these targets and make it difficult for cybercriminals to get to these targets.
The SCP technique ‘#2 Control Access to Facilities’ aims to block physical places (such as data centres) and virtual places (such as applications and websites) from cybercriminals. Hence, we classified controls such as securing access controls (ISO/IEC 5.15), access rights (ISO/IEC 5.18), privileged access rights (ISO/IEC 8.02), networks (ISO/IEC 8.20), network services (ISO/IEC 8.21), physical perimeters (ISO/IEC 7.01), and physical entry (ISO/IEC 7.02) under this SCP technique.
The SCP technique ‘#3 Screen Exits’ aims to make it difficult for offenders to leave a place after a criminal action with their criminal proceeds (such as data). Hence, the control on preventing data leakages (ISO/IEC 8.12) from an organization is suited to be classified under this SCP technique. The ISO/IEC 7.01 control on physical security perimeters is about defining security perimeters to prevent unauthorized access rather than making it difficult for offenders to leave a place and hence is more suited to be classified under the previous SCP technique ‘#2 Control Access to Facilities’. The SCP technique ‘#4 Deflect Offenders’ changes the movement patterns of offenders. Therefore, we can classify the controls that segregate networks (ISO/IEC 8.22) and development, test, and production environments (ISO/IEC 8.31) under this SCP technique.
The SCP technique ‘#5 Control Tools/Weapons’ limits offenders’ access to tools (such as operating system software tools) that can be used for cybercriminal actions. As such, actions to control the use of privileged utility programs (ISO/IEC 8.18) that can be inadvertently used in hacking scripts and to control the installation of software (ISO/IEC 8.19) so that they cannot be hijacked or turned to malware can be classified under this SCP technique. Furthermore, the control to require employees to return their assets (ISO/IEC 5.11) upon change or termination of their employment can be classified under this SCP technique. This is especially pertinent when the employee feels disgruntled upon sudden or forceful termination and misuses assets such as computing devices, keys, or access cards to data centres that allow certain access to the organization’s places [73].
‘S2 Increase the Risks’
The SCP strategy ‘S2 Increase the Risks’ increases the risks faced by offenders by providing more or better guardianship that increases the likelihood of detecting criminal activities [31]. We classified a total of 17 ISO/IEC controls, shown in Table 6, for this SCP strategy.
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#06 Extend Guardianships | People | 6.08 Information security event reporting |
#07 Assist natural surveillance | Organizational | 5.22 Monitoring, review, and change management of supplier services |
#08 Reduce Anonymity | Organizational | 5.06 Contact with special interest groups |
#08 Reduce Anonymity | People | 6.01 Screening |
#08 Reduce Anonymity | Technological | 8.05 Secure authentication |
#08 Reduce Anonymity | Organizational | 5.16 Identity management |
#08 Reduce Anonymity | Organizational | 5.17 Authentication information |
#09 Utilise Place Managers | Organizational | 5.02 Information security roles and responsibilities |
#10 Strengthen Formal Surveillance | Organizational | 5.03 Segregation of duties |
#10 Strengthen Formal Surveillance | Organizational | 5.07 Threat intelligence |
#10 Strengthen Formal Surveillance | Organizational | 5.24 Information security incident management planning and preparation |
#10 Strengthen Formal Surveillance | Organizational | 5.25 Assessment and decision on information security events |
#10 Strengthen Formal Surveillance | Organizational | 5.28 Collection of evidence |
#10 Strengthen Formal Surveillance | Physical | 7.04 Physical security monitoring |
#10 Strengthen Formal Surveillance | Technological | 8.15 Logging |
#10 Strengthen Formal Surveillance | Technological | 8.16 Monitoring activities |
#10 Strengthen Formal Surveillance | Technological | 8.17 Clock synchronisation |
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#06 Extend Guardianships | People | 6.08 Information security event reporting |
#07 Assist natural surveillance | Organizational | 5.22 Monitoring, review, and change management of supplier services |
#08 Reduce Anonymity | Organizational | 5.06 Contact with special interest groups |
#08 Reduce Anonymity | People | 6.01 Screening |
#08 Reduce Anonymity | Technological | 8.05 Secure authentication |
#08 Reduce Anonymity | Organizational | 5.16 Identity management |
#08 Reduce Anonymity | Organizational | 5.17 Authentication information |
#09 Utilise Place Managers | Organizational | 5.02 Information security roles and responsibilities |
#10 Strengthen Formal Surveillance | Organizational | 5.03 Segregation of duties |
#10 Strengthen Formal Surveillance | Organizational | 5.07 Threat intelligence |
#10 Strengthen Formal Surveillance | Organizational | 5.24 Information security incident management planning and preparation |
#10 Strengthen Formal Surveillance | Organizational | 5.25 Assessment and decision on information security events |
#10 Strengthen Formal Surveillance | Organizational | 5.28 Collection of evidence |
#10 Strengthen Formal Surveillance | Physical | 7.04 Physical security monitoring |
#10 Strengthen Formal Surveillance | Technological | 8.15 Logging |
#10 Strengthen Formal Surveillance | Technological | 8.16 Monitoring activities |
#10 Strengthen Formal Surveillance | Technological | 8.17 Clock synchronisation |
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#06 Extend Guardianships | People | 6.08 Information security event reporting |
#07 Assist natural surveillance | Organizational | 5.22 Monitoring, review, and change management of supplier services |
#08 Reduce Anonymity | Organizational | 5.06 Contact with special interest groups |
#08 Reduce Anonymity | People | 6.01 Screening |
#08 Reduce Anonymity | Technological | 8.05 Secure authentication |
#08 Reduce Anonymity | Organizational | 5.16 Identity management |
#08 Reduce Anonymity | Organizational | 5.17 Authentication information |
#09 Utilise Place Managers | Organizational | 5.02 Information security roles and responsibilities |
#10 Strengthen Formal Surveillance | Organizational | 5.03 Segregation of duties |
#10 Strengthen Formal Surveillance | Organizational | 5.07 Threat intelligence |
#10 Strengthen Formal Surveillance | Organizational | 5.24 Information security incident management planning and preparation |
#10 Strengthen Formal Surveillance | Organizational | 5.25 Assessment and decision on information security events |
#10 Strengthen Formal Surveillance | Organizational | 5.28 Collection of evidence |
#10 Strengthen Formal Surveillance | Physical | 7.04 Physical security monitoring |
#10 Strengthen Formal Surveillance | Technological | 8.15 Logging |
#10 Strengthen Formal Surveillance | Technological | 8.16 Monitoring activities |
#10 Strengthen Formal Surveillance | Technological | 8.17 Clock synchronisation |
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#06 Extend Guardianships | People | 6.08 Information security event reporting |
#07 Assist natural surveillance | Organizational | 5.22 Monitoring, review, and change management of supplier services |
#08 Reduce Anonymity | Organizational | 5.06 Contact with special interest groups |
#08 Reduce Anonymity | People | 6.01 Screening |
#08 Reduce Anonymity | Technological | 8.05 Secure authentication |
#08 Reduce Anonymity | Organizational | 5.16 Identity management |
#08 Reduce Anonymity | Organizational | 5.17 Authentication information |
#09 Utilise Place Managers | Organizational | 5.02 Information security roles and responsibilities |
#10 Strengthen Formal Surveillance | Organizational | 5.03 Segregation of duties |
#10 Strengthen Formal Surveillance | Organizational | 5.07 Threat intelligence |
#10 Strengthen Formal Surveillance | Organizational | 5.24 Information security incident management planning and preparation |
#10 Strengthen Formal Surveillance | Organizational | 5.25 Assessment and decision on information security events |
#10 Strengthen Formal Surveillance | Organizational | 5.28 Collection of evidence |
#10 Strengthen Formal Surveillance | Physical | 7.04 Physical security monitoring |
#10 Strengthen Formal Surveillance | Technological | 8.15 Logging |
#10 Strengthen Formal Surveillance | Technological | 8.16 Monitoring activities |
#10 Strengthen Formal Surveillance | Technological | 8.17 Clock synchronisation |
The SCP technique ‘#6 Extend Guardianship’ encourages unofficial guardians (such as other non-cybersecurity employees) to act or be more effective. Therefore, the ISO/IEC 6.08 control on ‘information security event reporting’, which is a mechanism for employees to report observed or suspected information security events (ISO/IEC 6.08) is suited for this SCP technique. By doing so, this ISO/IEC 6.08 control increases the risk of detection of offenders and is similar to the community safety applications that were highlighted by Reynald [74] on digital guardianships.
The SCP technique ‘#7 Assist Natural Surveillance’ increases the likelihood of potential guardians seeing criminal actions occurring in places. Hence, regularly monitoring and reviewing the changes in the supplier information security practices and service delivery (ISO/IEC 5.22) can help to detect criminal actions occurring at suppliers’ places.
The SCP technique ‘#8 Reduce Anonymity’ increases the likelihood that potential guardians can identify the features of offenders. Controls that focus on knowing potential offenders, such as identify management (ISO/IEC 5.16), authentication (ISO/IEC 5.17), background screening (ISO/IEC 6.01) and secure authentication (ISO/IEC 8.05) can be classified under this SCP technique. Furthermore, liaising with external specialist security groups (ISO/IEC 5.06), such as Forum of Incident Response and Security Teams (FIRST) and online cybersecurity information sharing platforms such as CIAC can reduce the anonymity of cyber offenders [75, 76].
The SCP technique ‘#9 Utilise Place Managers’ uses existing or new employees as potential guardians in places such as data centres and virtual places such as websites. The control that defines information security roles and responsibilities in an organization (ISO/IEC 5.02) is therefore suitable for this SCP technique. This is also in line with research from Ho et al. [33], where their vignette experimental study highlights that preventing cybercrimes requires a team of skilled and assigned place managers, such as cybersecurity professionals working in the SOC.
The SCP technique ‘#10 Strengthen Formal Surveillance’ increases the ability of official or formal guardians such as cybersecurity professionals working in a Security Operations Centre (SOC) to be more effective. Therefore, common SOC activities that increase cyber capability, such as managing threat intelligence (ISO/IEC 5.07), collecting and assessing information security events (ISO/IEC 5.25, 5.28) and conducting cybersecurity monitoring (ISO/IEC 7.04, 8.16), are classified under this SCP technique. Technological controls such as data collection and logging information (ISO/IEC 8.15) and clock synchronization (ISO/IEC 8.17) also improve the monitoring abilities of cybersecurity professionals in the SOC and thereby strengthen the formal surveillance capability of official guardians. These controls contain features similar to the CyberTrafficking Surveillance System (CyTraSS) that Chung et al. [77] propose on the analysis of social media content to counter cyber-trafficking. Furthermore, the control on segregation of duties (ISO/IEC 5.03) such as requiring superuser accounts to be created and approved formally by two different administrators in an application can help the administrators (acting as guardians) to detect the unauthorized creation of superuser accounts.
‘S3 Reduce the Rewards’
The SCP strategy ‘S3 Reduce the Rewards’ reduces the rewards for offenders by limiting the value of their target (such as data stolen in a ransomware attack) or their ability to find the target [31]. We classified a total of 17 ISO/IEC controls, shown in Table 7, for this SCP strategy.
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#11 Conceal Targets | Organizational | 5.12 Classification of information |
#11 Conceal Targets | Physical | 7.07 Clear desk and clear screen |
#11 Conceal Targets | Technological | 8.03 Information access restriction |
#11 Conceal Targets | Technological | 8.04 Access to source code |
#11 Conceal Targets | Technological | 8.11 Data masking |
#11 Conceal Targets | Technological | 8.24 Use of cryptography |
#12 Remove Targets | Physical | 7.14 Secure disposal or re-use of equipment |
#12 Remove Targets | Technological | 8.10 Information deletion |
#13 Identify Property | Organizational | 5.09 Inventory of information and other associated assets |
#13 Identify Property | Organizational | 5.13 Labelling of information |
#14 Disrupt Markets | Organizational | 5.05 Contact with authorities |
#14 Disrupt Markets | Organizational | 5.14 Information transfer |
#14 Disrupt Markets | Organizational | 5.26 Response to information security incidents |
#15 Deny Benefits | Organizational | 5.30 ICT readiness for business continuity |
#15 Deny Benefits | Technological | 8.06 Capacity management |
#15 Deny Benefits | Technological | 8.13 Information backup |
#15 Deny Benefits | Technological | 8.14 Redundancy of information processing facilities |
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#11 Conceal Targets | Organizational | 5.12 Classification of information |
#11 Conceal Targets | Physical | 7.07 Clear desk and clear screen |
#11 Conceal Targets | Technological | 8.03 Information access restriction |
#11 Conceal Targets | Technological | 8.04 Access to source code |
#11 Conceal Targets | Technological | 8.11 Data masking |
#11 Conceal Targets | Technological | 8.24 Use of cryptography |
#12 Remove Targets | Physical | 7.14 Secure disposal or re-use of equipment |
#12 Remove Targets | Technological | 8.10 Information deletion |
#13 Identify Property | Organizational | 5.09 Inventory of information and other associated assets |
#13 Identify Property | Organizational | 5.13 Labelling of information |
#14 Disrupt Markets | Organizational | 5.05 Contact with authorities |
#14 Disrupt Markets | Organizational | 5.14 Information transfer |
#14 Disrupt Markets | Organizational | 5.26 Response to information security incidents |
#15 Deny Benefits | Organizational | 5.30 ICT readiness for business continuity |
#15 Deny Benefits | Technological | 8.06 Capacity management |
#15 Deny Benefits | Technological | 8.13 Information backup |
#15 Deny Benefits | Technological | 8.14 Redundancy of information processing facilities |
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#11 Conceal Targets | Organizational | 5.12 Classification of information |
#11 Conceal Targets | Physical | 7.07 Clear desk and clear screen |
#11 Conceal Targets | Technological | 8.03 Information access restriction |
#11 Conceal Targets | Technological | 8.04 Access to source code |
#11 Conceal Targets | Technological | 8.11 Data masking |
#11 Conceal Targets | Technological | 8.24 Use of cryptography |
#12 Remove Targets | Physical | 7.14 Secure disposal or re-use of equipment |
#12 Remove Targets | Technological | 8.10 Information deletion |
#13 Identify Property | Organizational | 5.09 Inventory of information and other associated assets |
#13 Identify Property | Organizational | 5.13 Labelling of information |
#14 Disrupt Markets | Organizational | 5.05 Contact with authorities |
#14 Disrupt Markets | Organizational | 5.14 Information transfer |
#14 Disrupt Markets | Organizational | 5.26 Response to information security incidents |
#15 Deny Benefits | Organizational | 5.30 ICT readiness for business continuity |
#15 Deny Benefits | Technological | 8.06 Capacity management |
#15 Deny Benefits | Technological | 8.13 Information backup |
#15 Deny Benefits | Technological | 8.14 Redundancy of information processing facilities |
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#11 Conceal Targets | Organizational | 5.12 Classification of information |
#11 Conceal Targets | Physical | 7.07 Clear desk and clear screen |
#11 Conceal Targets | Technological | 8.03 Information access restriction |
#11 Conceal Targets | Technological | 8.04 Access to source code |
#11 Conceal Targets | Technological | 8.11 Data masking |
#11 Conceal Targets | Technological | 8.24 Use of cryptography |
#12 Remove Targets | Physical | 7.14 Secure disposal or re-use of equipment |
#12 Remove Targets | Technological | 8.10 Information deletion |
#13 Identify Property | Organizational | 5.09 Inventory of information and other associated assets |
#13 Identify Property | Organizational | 5.13 Labelling of information |
#14 Disrupt Markets | Organizational | 5.05 Contact with authorities |
#14 Disrupt Markets | Organizational | 5.14 Information transfer |
#14 Disrupt Markets | Organizational | 5.26 Response to information security incidents |
#15 Deny Benefits | Organizational | 5.30 ICT readiness for business continuity |
#15 Deny Benefits | Technological | 8.06 Capacity management |
#15 Deny Benefits | Technological | 8.13 Information backup |
#15 Deny Benefits | Technological | 8.14 Redundancy of information processing facilities |
The SCP technique ‘#11 Conceal Targets’ limits offenders’ ability to see targets such as data. Therefore, we classified controls that are related to information classification (ISO/IEC 5.12), restriction (ISO/IEC 8.03), and access (ISO/IEC 8.04) under this SCP technique along with controls that deal with hiding or obscuring information such as clearing desks and screens (ISO/IEC 7.07), data masking (ISO/IEC 8.11), and cryptography (ISO/IEC 8.24).
The SCP technique ‘#12 Remove Targets’ takes potential targets away from places or removes the valuable aspects of it. Hence, the control on secure disposal of storage media (ISO/IEC 7.14) that can contain important data and secure deletion of information (ISO/IEC 8.10) fit well under this SCP technique.
The SCP technique ‘#13 Identify Property’ marks potential targets such as data to make them traceable to the owner or make it more difficult for the offender to claim ownership. Controls that are suitable to be classified under this SCP technique are those that require the labelling of information (ISO/IEC 5.13) and maintaining the inventory of information and computing assets (ISO/IEC 5.09).
The SCP technique ‘#14 Disrupt Markets’ makes it difficult for offenders to transfer the proceeds of their crimes to others, such as selling the data they have obtained. Therefore, controls about contacting with authorities on potential cybercrimes (ISO/IEC 5.05), having strict rules on transferring information (ISO/IEC 5.14) and responding effectively and efficiently on information security incidents (ISO/IEC 5.26) can make it difficult for cybercriminals to realize the benefits of their actions because they face difficulties in transferring the results of the proceeds elsewhere.
The SCP technique ‘#15 Deny Benefits’ makes it difficult for offenders to use their crime targets, such as stolen data, for their intended purposes. Controls that provide IT availability and redundancies such as managing information processing capacities (ISO/IEC 8.06), additional facilities (ISO/IEC 8.14), business continuity (ISO/IEC 5.30), and backup of information (ISO/IEC 8.13), make it difficult for perpetrators of DDoS and ransomware attacks to be successful, thereby denying them the benefits of these attacks.
‘S4 Reduce Provocations’
The SCP Strategy ‘S4 Reduce Provocations’ limits situational stimuli that can precipitate negative emotional outbursts such as anger, frustration, and stress that could result in criminal actions [31]. We could not observe any suitable ISO/IEC controls that are appropriate to be classified under this SCP strategy. There are organizational rules that regulate employees’ behaviour such as Acceptable Use Policy (AUP) and employment terms and conditions but we find it more appropriate to classify them under the next SCP strategy.
‘S5 Remove Excuses’
The SCP strategy ‘S5 Remove Excuses’ removes excuses that offenders give, such as pleading ignorance, by presenting or reminding or implementing situational controls that clarify offenders’ responsibilities [31]. The offenders could be people who directly caused the crimes, such as jaywalkers who claimed ignorance because they saw others jaywalking. It could also be about people who ‘indirectly’ facilitated crimes to happen due to their behaviour such as being careless, inattentive, ignorant, negligent, lack of due care and due diligence. For example, an employee negligently leaving a key or access card unattended on the table, which subsequently led to thefts. In the context of ISO/IEC 27002:2022, this SCP strategy focuses on human behaviour in the organization, which involves the people in organization such as employees, vendors, and users. For example, one key activity of a successful ransomware attack is usually an ignorant or negligent employee clicking on a malicious link in a phishing email [78]. We classified a total of 13 ISO/IEC controls, shown in Table 8, for this SCP strategy.
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#21 Set Rules | Organizational | 5.01 Policies for information security |
#21 Set Rules | Organizational | 5.10 Acceptable use of information and other associated assets |
#21 Set Rules | People | 6.02 Terms and conditions of employment |
#21 Set Rules | People | 6.04 Disciplinary process |
#21 Set Rules | People | 6.05 Responsibilities after termination or change of employment |
#21 Set Rules | People | 6.06 Confidentiality or non-disclosure agreements |
#22 Post Instructions | Organizational | 5.37 Documented operating procedures |
#22 Post Instructions | People | 6.03 Information security awareness, education and training |
#24 Assist Compliance | Organizational | 5.04 Management responsibilities |
#24 Assist compliance | Organizational | 5.31 Legal, statutory, regulatory, and contractual requirements |
#24 Assist compliance | Organizational | 5.32 Intellectual property rights |
#24 Assist compliance | Organizational | 5.34 Privacy and protection of PII |
#24 Assist compliance | Organizational | 5.36 Conformance with policies, rules, and standards for information security |
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#21 Set Rules | Organizational | 5.01 Policies for information security |
#21 Set Rules | Organizational | 5.10 Acceptable use of information and other associated assets |
#21 Set Rules | People | 6.02 Terms and conditions of employment |
#21 Set Rules | People | 6.04 Disciplinary process |
#21 Set Rules | People | 6.05 Responsibilities after termination or change of employment |
#21 Set Rules | People | 6.06 Confidentiality or non-disclosure agreements |
#22 Post Instructions | Organizational | 5.37 Documented operating procedures |
#22 Post Instructions | People | 6.03 Information security awareness, education and training |
#24 Assist Compliance | Organizational | 5.04 Management responsibilities |
#24 Assist compliance | Organizational | 5.31 Legal, statutory, regulatory, and contractual requirements |
#24 Assist compliance | Organizational | 5.32 Intellectual property rights |
#24 Assist compliance | Organizational | 5.34 Privacy and protection of PII |
#24 Assist compliance | Organizational | 5.36 Conformance with policies, rules, and standards for information security |
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#21 Set Rules | Organizational | 5.01 Policies for information security |
#21 Set Rules | Organizational | 5.10 Acceptable use of information and other associated assets |
#21 Set Rules | People | 6.02 Terms and conditions of employment |
#21 Set Rules | People | 6.04 Disciplinary process |
#21 Set Rules | People | 6.05 Responsibilities after termination or change of employment |
#21 Set Rules | People | 6.06 Confidentiality or non-disclosure agreements |
#22 Post Instructions | Organizational | 5.37 Documented operating procedures |
#22 Post Instructions | People | 6.03 Information security awareness, education and training |
#24 Assist Compliance | Organizational | 5.04 Management responsibilities |
#24 Assist compliance | Organizational | 5.31 Legal, statutory, regulatory, and contractual requirements |
#24 Assist compliance | Organizational | 5.32 Intellectual property rights |
#24 Assist compliance | Organizational | 5.34 Privacy and protection of PII |
#24 Assist compliance | Organizational | 5.36 Conformance with policies, rules, and standards for information security |
SCP Technique . | Clause Type . | ISO/IEC Control . |
---|---|---|
#21 Set Rules | Organizational | 5.01 Policies for information security |
#21 Set Rules | Organizational | 5.10 Acceptable use of information and other associated assets |
#21 Set Rules | People | 6.02 Terms and conditions of employment |
#21 Set Rules | People | 6.04 Disciplinary process |
#21 Set Rules | People | 6.05 Responsibilities after termination or change of employment |
#21 Set Rules | People | 6.06 Confidentiality or non-disclosure agreements |
#22 Post Instructions | Organizational | 5.37 Documented operating procedures |
#22 Post Instructions | People | 6.03 Information security awareness, education and training |
#24 Assist Compliance | Organizational | 5.04 Management responsibilities |
#24 Assist compliance | Organizational | 5.31 Legal, statutory, regulatory, and contractual requirements |
#24 Assist compliance | Organizational | 5.32 Intellectual property rights |
#24 Assist compliance | Organizational | 5.34 Privacy and protection of PII |
#24 Assist compliance | Organizational | 5.36 Conformance with policies, rules, and standards for information security |
The SCP technique ‘#21 Set Rules’ provides information about unacceptable behaviours in a setting. Therefore, we found it more appropriate to classify controls that regulate employees’ behaviour, such as having information security policies (ISO/IEC 5.01), AUP (ISO/IEC 5.10), responsibilities, terms and conditions of employment (ISO/IEC 6.02, 6.05), a formalized disciplinary process (ISO/IEC 6.04) and confidentiality or non-disclosure agreements (ISO/IEC 6.06), under this SCP technique.
The SCP technique ‘#22 Post Instructions’ focuses on providing detailed information on how to meet behavioural requirements in a setting. Therefore, controls that provide detailed instructions on employees’ behaviour, such as having documented operating procedures for information processing facilities (ISO/IEC 5.37) and information security awareness, education, and training (ISO/IEC 6.03), are suited for this SCP technique.
The SCP technique ‘#24 Assist Compliance’ creates situations that make it easier for people to carry out acceptable behaviours in a setting. Hence, controls such as having organizational and management support to apply information security in the organization (ISO/IEC 5.04), complying with legal, regulatory, and contractual requirements (ISO/IEC 5.31), intellectual property rights (ISO/IEC 5.32), privacy and protection of Personable Identifiable Information (PII) (ISO/IEC 5.34), and conformance with policies and standards for information security (ISO/IEC 5.36), are appropriate for this SCP technique.
We have not classified any ISO/IEC controls under the SCP technique ‘#23 Alert Conscience’ and SCP technique ‘#25 Control Drugs and Alcohol’. The former is about providing situational reminders of unacceptable aspects of certain behaviours. The latter is about limiting the ingestion of substances, such as drugs and alcohol, that distort thinking or disinhibit behaviours. One possible reason why there are no suitable ISO/IEC controls for the latter SCP technique could be that not ingesting substances is already part of the employment terms.
ISO/IEC 27002:2022 and SCP strategies
Analysis of classification
We present our analysis of the results of the classification in Table 9. Almost half of the ISO/IEC controls centre on the SCP Strategy ‘S1 Increase the Efforts’ (46 ISO/IEC controls or 49%). Out of these 46 ISO/IEC controls, almost half of these (22 ISO/IEC controls or 48%) focus on technology. There is only one ISO/IEC control that focuses on people. We classified an equal number of 17 (18%) ISO/IEC controls for the second and third SCP strategies ‘S2 Increase the Risks’ and ‘S3 Reduce the Rewards’. We did not classify any controls for SCP strategy ‘S4 Reduce Provocation’. The fifth SCP strategy has 13 (15%) ISO/IEC controls, which are mainly related to organizational and people.
SCP Strategy . | ISO Clauses . | No. . | Total . |
---|---|---|---|
S1 Increase the Efforts | Organizational | 12 | 46 (49%) |
People | 1 | ||
Physical | 11 | ||
Technological | 22 | ||
S2 Increase the Risks | Organizational | 10 | 17 (18%) |
People | 2 | ||
Physical | 1 | ||
Technological | 4 | ||
S3 Reduce the Rewards | Organizational | 7 | 17 (18%) |
People | 0 | ||
Physical | 2 | ||
Technological | 8 | ||
S4 Reduce Provocation | Organizational | 0 | 0 (0%) |
People | 0 | ||
Physical | 0 | ||
Technological | 0 | ||
S5 Remove Excuses | Organizational | 8 | 13 (15%) |
People | 5 | ||
Physical | 0 | ||
Technological | 0 | ||
Total: | 93 (100%) |
SCP Strategy . | ISO Clauses . | No. . | Total . |
---|---|---|---|
S1 Increase the Efforts | Organizational | 12 | 46 (49%) |
People | 1 | ||
Physical | 11 | ||
Technological | 22 | ||
S2 Increase the Risks | Organizational | 10 | 17 (18%) |
People | 2 | ||
Physical | 1 | ||
Technological | 4 | ||
S3 Reduce the Rewards | Organizational | 7 | 17 (18%) |
People | 0 | ||
Physical | 2 | ||
Technological | 8 | ||
S4 Reduce Provocation | Organizational | 0 | 0 (0%) |
People | 0 | ||
Physical | 0 | ||
Technological | 0 | ||
S5 Remove Excuses | Organizational | 8 | 13 (15%) |
People | 5 | ||
Physical | 0 | ||
Technological | 0 | ||
Total: | 93 (100%) |
SCP Strategy . | ISO Clauses . | No. . | Total . |
---|---|---|---|
S1 Increase the Efforts | Organizational | 12 | 46 (49%) |
People | 1 | ||
Physical | 11 | ||
Technological | 22 | ||
S2 Increase the Risks | Organizational | 10 | 17 (18%) |
People | 2 | ||
Physical | 1 | ||
Technological | 4 | ||
S3 Reduce the Rewards | Organizational | 7 | 17 (18%) |
People | 0 | ||
Physical | 2 | ||
Technological | 8 | ||
S4 Reduce Provocation | Organizational | 0 | 0 (0%) |
People | 0 | ||
Physical | 0 | ||
Technological | 0 | ||
S5 Remove Excuses | Organizational | 8 | 13 (15%) |
People | 5 | ||
Physical | 0 | ||
Technological | 0 | ||
Total: | 93 (100%) |
SCP Strategy . | ISO Clauses . | No. . | Total . |
---|---|---|---|
S1 Increase the Efforts | Organizational | 12 | 46 (49%) |
People | 1 | ||
Physical | 11 | ||
Technological | 22 | ||
S2 Increase the Risks | Organizational | 10 | 17 (18%) |
People | 2 | ||
Physical | 1 | ||
Technological | 4 | ||
S3 Reduce the Rewards | Organizational | 7 | 17 (18%) |
People | 0 | ||
Physical | 2 | ||
Technological | 8 | ||
S4 Reduce Provocation | Organizational | 0 | 0 (0%) |
People | 0 | ||
Physical | 0 | ||
Technological | 0 | ||
S5 Remove Excuses | Organizational | 8 | 13 (15%) |
People | 5 | ||
Physical | 0 | ||
Technological | 0 | ||
Total: | 93 (100%) |
Areas of improvements for ISO/IEC 27002:2022 from SCP perspective
The large number of ISO/IEC controls (49%) classified in the SCP Strategy ‘S1 Increase the Efforts’ could be because ISO/IEC 27002:2022 focuses on cybersecurity and therefore emphasizes preventing (or making it harder to commit) cybercrimes. On the other hand, there are zero and 13 ISO/IEC controls (15%) for the SCP Strategies ‘S4 Reduce Provocation’ and ‘S5 Remove Excuses’, respectively, which focus more on the human elements of crime. In addition, out of the 93 ISO/IEC controls, there are 34 ISO/IEC controls (37%) for technological clauses while there are only 8 ISO/IEC controls (9%) for the people clauses.
There could be several reasons for the underemphasis on the human elements in ISO/IEC 27002. One possible reason is that the development of the ISO/IEC 27002 controls is led by cybersecurity professionals who are more likely to be familiar with technological controls and less familiar with criminology and human behaviour [16]. Furthermore, the ISO/IEC 27002 controls are formulated by common practice and authority through the anecdotal experiences of cybersecurity professionals rather than through robust validation methods [54].
Another reason could be that employees are expected to behave in a professional manner and not behave carelessly or recklessly or be prone to provocations. Therefore, it may be seen as unnecessary to include any ISO/IEC controls for the SCP Strategy ‘S4 Reduce Provocation’. However, it is unwise to rely on this professional code of conduct because disgruntled employees who are dissatisfied with their organizations have been shown to commit cybercrimes [73, 79]. The psychological aspects and human factors are important elements in having effective cybersecurity in an organization [80, 81], especially when it comes to insider or employee threats [42]. Therefore, there is room for further thoughts and research to improve the ISO/IEC 27002 controls to accommodate more SCP strategies and techniques on human factors. One example would be to anticipate and manage negative issues in the workplace by having clear and consistent human resource policies to deal with employee issues justly, so that situational precipitators such as perceived injustices, frustrations, and anger that could result in IT sabotage or cybercrimes can be avoided [82]. Another could be to involve employees during the cybersecurity design and implementation processes to reduce possible user friction and situational precipitators, especially when cybersecurity controls can lead to inconveniences and frustrations for employees. The SCP perspective is not just useful for and applicable to the ISO/IEC 27002 but also to other cybersecurity standards such as NIST Cybersecurity Framework [22] and ISACA COBIT [23].
SCP-C3 cycle and common inventory
Facilitating multi-disciplinary approach using SCP
Offenders do not pigeonhole themselves into committing only cyber-enabled or cyber-focused crimes. A cybercrime can include elements of both cyber-enabled and cyber-focused crimes. An IT-savvy cyberstalker, for example, can stalk the victim’s social media accounts (cyber-enabled) as well as hack the victim’s IT assets (cyber-focused). Therefore, there is an awareness among the research community that a multi-disciplinary approach is necessary to handle complex societal issues such as crime science and cybercrimes [16, 18–20, 83].
One possible way to facilitate multi-disciplinary research into cybercrimes is to provide instruments, such as frameworks and models, which combine criminology and cybersecurity concepts and ideas. This can provide a shortcut, where criminologists can use these instruments (that have cybersecurity elements) in their cybercrime research and vice versa for the cybersecurity researcher. However, our research indicates that no such instruments exist. Therefore, in addition to the development of the common inventory where we mapped ISO/IEC controls to SCP, we also propose the development of the SCP-C3 cycle in the sub-sections below and discuss how this SCP-C3 cycle can be used in conjunction with our common inventory of SCP cybersecurity controls as instruments to facilitate multi-disciplinary research by cybercrime researchers regardless of their original criminology or cybersecurity background.
SCP-C3 cycle
SCP-C3 cycle background
Our SCP-C3 cycle is developed by incorporating key ideas from SCP and the Plan-Do-Check-Act (PDCA) continuous improvement cycle. SCP emphasizes five principles of intervention [4]. SCP Principle #1 (SP1) focuses on highly specific categories of crimes such as domestic violence rather than on broad categories of crimes such as general violence or robberies at commercial establishments rather than all robberies. SCP Principle #2 (SP2) emphasizes the need to focus on crime concentrations following the 80-20 Pareto Principle [84]. Opportunities for crimes are infinite, so SCP stresses designing situational interventions on crime concentrations to obtain the largest preventive benefits. SCP Principle #3 (SP3) stresses that it is important to understand how the crime is committed, especially from the offender’s perspective, in order to use the appropriate SCP interventions. A more detailed understanding of the crime processes can lead to a more diverse choice of SCP interventions. SCP Principle #4 (SP4) advocates an action-research model when analysing a crime problem because SCP solutions to the crime problem must be assessed for effectiveness. The 25 SCP techniques generate many ways to reduce opportunities for crimes and therefore SCP Principle #5 (SP5) states that the most suitable solutions should be used after careful assessments of their costs and benefits. These five SCP principles can be applied to cybercrimes as well.
The PDCA cycle [85] is a continuous quality management approach that is popularly used in many diverse fields such as production and cybersecurity standards such as ISO/IEC 27001 [86]. Cybersecurity professionals who are familiar with ISO/IEC 27001 ISMS are already familiar with the PDCA cycle. On the other hand, criminologists are also likely to be familiar with SCP. Hence, combining both of them into the SCP-C3 cycle is a middle ground approach that will allow both criminologists and cybersecurity professionals to speak in a unified and common language by using SCP to prevent cybercrimes.
SCP- C3 cycle details
Figure 3 shows a visual diagram of our proposed SCP-C3 cycle, which was developed based on the five SCP principles and the PDCA cycle. Our SCP-C3 cycle compromises three key nodes, namely (1) Concentrate, (2) Comprehend, and (3) Consider, which are cyclical to denote its continuous improvement nature. The first node on Concentrate is about focusing on specific and important cybercrimes. In this activity node, we determine the specific type of cybercrime to concentrate on (SP1). The type of cybercrime to concentrate on should also be cybercrimes that have great impact and crime concentrations (SP2).

The second node on Comprehend is about understanding cybercrimes and their possible SCP invention measures. Once the specific type of cybercrime is determined, the next step is to understand (SP3) how the cybercrime is committed using an action-research approach (SP4) and how we can prevent it using SCP cybersecurity controls. One way to do so is by first modelling cybercrimes using an established modelling methodology such as the Lockheed Martin Cyber Kill Chain [87], crime scripts [71], and business process modelling [88]. Subsequently, we identify potential intervention points in the model that can prevent cybercrimes. Once the potential intervention points are identified, we can then select appropriate intervention measures from the common inventory of SCP cybersecurity controls and apply them to the intervention points that were identified previously. The effectiveness of the intervention measures that were selected previously can also be assessed.
The third node on Consider is about deciding suitable SCP cybersecurity controls to use. We consider which of the SCP cybersecurity controls that we identified in the previous activity node to be suitable for final implementation. When considering the SCP cybersecurity controls, the assessment should also consider (SP5) both the financial and non-financial aspects such as social and ethical costs like intrusiveness, inconvenience, and discrimination [4].
Applying SCP-C3 cycle and common inventory
We illustrate how to apply the SCP-C3 cycle through a ransomware example. We begin by concentrating our efforts on specific and important types of cybercrimes. We concentrate on ransomware or RaaS, which is a specific form of malware/cybercrime and a top cybercrime threat [89]. Next, we seek to comprehend how ransomware work. We can start by modelling the key activities of ransomware in Fig. 4. The model breaks down the ransomware activity into a series of key actions performed by the various entities. Next, in the model, we identify potential intervention points and select suitable controls from the common inventory of SCP cybersecurity controls. There can be many controls that can be applied within the SCP intervention points, so research can be conducted to assess the effectiveness of these controls. Finally, with all the research information available, organizations can consider the type of SCP cybersecurity controls that is suitable to be implemented, taking into account the financial and non-financial aspects.

Applying common inventory using ISO controls to control ransomware. For brevity, we use the ‘ISO number’ notation to depict ISO/IEC 27002 clauses. Adapted from: Ho et al. [16].
Advantages of common inventory
With our common inventory, criminologists who are well versed in SCP but not knowledgeable about cybersecurity need not worry about the types of suitable ISO/IEC cybersecurity controls to use in their models and vice versa for the cybersecurity professionals. For example, in Fig. 4, a criminologist may propose to increase the efforts (S1) needed by the offender (ransomware) before the victim receives material such as a phishing email that contains the link to the ransomware. Among the various SCP techniques, the criminologist could consider ways to harden (SCP #01) the ransomware target. Even if the criminologist is unfamiliar with cybersecurity controls, they can refer to our common inventory to select suitable cybersecurity controls under this SCP technique, such as applying web filtering techniques (ISO 8.23), securing user endpoint devices (8.01), and applying protection measures against malware (ISO 8.07). In another example, the criminologist may be thinking of ways to reduce the rewards of a ransomware attack, such as disrupting the cybercriminal markets (SCP #14) to make it difficult for the offender to dispose of the data taken using ransomware and denying benefits (SCP #15) of the ransomware attack. From our common inventory, the criminologist can consider using controls on information backups (ISO 8.13) that can restore data lost from ransomware attacks or work with the authorities (ISO 5.06) on the aftermath of ransomware attacks.
Another advantage of our common inventory is that it espouses SCP strategies and its principles as its key pillars and is built using the popular ISO/IEC 27002 controls. By doing so, it adopts a more holistic approach to cybercrime prevention by covering the people (such as psychology and sociology), processes (such as organizational), and technology elements rather than overly focusing on a single-dimensional approach. Our study contributes to research calls for cybercrimes to be more multi-disciplinary [16, 18, 83].
Furthermore, organizations, especially those who have ISO certifications or are already implementing ISO/IEC controls, are more likely to accept the relevance of the research. Additionally, with its sheer number of controls, ISO/IEC 27002 is meant to provide a comprehensive and general all-purpose cybersecurity protection rather than targeting any specific cybercrimes [16]. It takes a lot of time, human resources and financial ability to fully implement ISO/IEC 27002, which organizations, especially smaller ones, may lack. It may be of greater value for organizations to focus first on ISO/IEC controls in our common inventory that target specific cybercrimes, especially those that are listed as top threats, such as ransomware [89]. This is in line with the Concentrate activity node of our SCP-C3 cycle.
Extending common inventory to other standards
Our common inventory can accept controls from other popular cybersecurity industry and government regulations, frameworks, standards, and guidelines such as ACSC Essential Eight [90], MITRE ATT&CK [91], NIST Cybersecurity Framework [22], other ISO/IEC Technical References, and Monetary Authority of Singapore (MAS) Technology Risk Management Guidelines [92]. This can supplement the ISO/IEC controls and further enrich the common inventory. This is especially true for standards that are also widely adopted by organizations and the industry such as the NIST Cybersecurity Framework [22], and standards that are more technical such as the MITRE ATT&CK [91].
Our common inventory would then be structured around the widely adopted SCP criminology practice and comprise (eventually) cybersecurity controls from all popular cybersecurity industry and government frameworks and standards. Once the common inventory is widely used by researchers and organizations, this can also make it easier for researchers to investigate the effectiveness of SCP techniques and ISO/IEC controls because there will be a large pool of samples from organizations that implement ISO/IEC controls that researchers can draw from. This aligns well with our Comprehend and Consider activity node of our SCP-C3 cycle.
Limitations and future works
Our study reviews the extant literature on applying SCP techniques to cybercrimes. The result of our review is in line with the existing research [16–18], which indicates that the use of SCP in preventing cybercrimes, while not exactly new, is still limited. Our review methodology, while structured, relied on using the SCP keywords to search for related SCP articles. One possible limitation of our keyword selection is that we may have unknowingly missed SCP-related articles that did not use the SCP techniques keyword. However, the chances of this occurring should be low because an article that discusses a particular SCP technique should logically mention the SCP technique keyword in its title. Our keyword search also can have another limitation where a popular cybersecurity control, such as cryptography, does not mention its corresponding SCP techniques in its title because the researchers may not be aware or are unfamiliar with SCP. On the other hand, part of our research objective is to investigate how cybersecurity controls are consciously used as an SCP technique in cybercrime prevention, so missing out these articles does not greatly impact our research outcome.
We have attempted to rationalize and explain our classification of ISO/IEC controls into the appropriate SCP techniques. However, this is by no means final. There is still room for adjustments in the classification as new thoughts and ideas develop in the use of SCP in cyberspace. It is possible that SCP techniques may need to evolve to take into account the nature of cyberspace and cybercrimes. Furthermore, our development of the common inventory is based on a cybersecurity industry standard (i.e. ISO/IEC), which focuses mainly on addressing organizational-level ‘non-compliant’ behaviours that can lead to cybercrimes. There are also other types of individual and societal-wide behaviours (such as spreading misinformation and cyberbullying) that need to be addressed as well. Hence, there is room for more research on expanding our common inventory and utilizing our SCP-C3 cycle in terms of their usage as instruments to facilitate multi-disciplinary research in cybercrime prevention.
Our SCP-C3 cycle provides an instrument for both criminologists and cybersecurity researchers to apply a holistic criminology and cybersecurity perspective to cybercrime prevention while our common inventory provides a ready-made toolkit of SCP cybersecurity controls. However, presently both are untested. For example, the ransomware event described in Fig. 4 is only a conceptual illustration on how ransomware may be investigated and prevented through a combination of criminology and cybersecurity perspectives via our SCP-C3 cycle and common inventory. More in-depth research is needed to investigate the prevention of ransomware using our SCP-C3 cycle and common inventory. The usefulness and applicability of the SCP-C3 cycle and the common inventory will subsequently depend on how they are used in future research.
Our common inventory presently focused on mapping the ISO/IEC cybersecurity controls to SCP due to the popularity and global adoption of the ISO/IEC cybersecurity standard in the industry. Yet, despite ISO/IEC popularity, there are also other competing standards that are popular in the industry such as MITRE and those from governments such as ACSC in Australia and NIST in the United States. Therefore, there is space for our common inventory to grow in terms of comprehensiveness and richness by incorporating the different cybersecurity controls from other standards, frameworks, and guidelines. For example, the MITRE mitigation techniques and controls are more technically specific compared to ISO/IEC controls and incorporating them to our common inventory can provide more technical solutions. In another example, future research could explore embedding our SCP-C3 into the NIST Core Cybersecurity Framework Core ‘Govern’ function, which could then allow organizations to consider their risk management strategy with a criminology perspective and potentially result in policies that are more appropriate and effective in controlling cybercrimes.
Concluding remarks
Since its inception in the seventies [4], the SCP approach has been successfully embraced by governments in combating a variety of crimes [8, 9, 13]. However, despite crime perpetuation evolving from just physical to also include cyber-focused and cyber-enabled crimes, the adoption of SCP to combat cybercrimes appears to be less widespread. Although there have been early attempts since 2000s to extend SCP to cybercrimes [34], the momentum has not picked up much as expected given SCP’s successful track record in dealing with other crimes. This was supported by recent SCP research [16, 17] and our review results, where we note that there are only 53 out of 1788 (3%) articles directly related to SCP techniques in cybercrime prevention.
Part of this could be the inherently complex nature of cybercrimes. Cybercrimes span from the more human-centric cyber-enabled crimes to the more technology-centric cyber-focused crimes. Collectively, preventing cybercrimes effectively can demand in-depth knowledge from a variety of fields such as computer science, criminology, and cybersecurity. The awareness that preventing cybercrimes encompasses multiple fields is not new and there have been research calls in recent years for multi-disciplinary efforts to study cybercrimes, including using SCP [16, 18–20]. However, from our literature review and review results, we argue that despite these calls, there has not been any significant headway made to promote multi-disciplinary collaboration or facilitate research from a different discipline such as criminology to another discipline such as cybersecurity. In addition, while we note that while there have been attempts to map cybersecurity controls to SCP [35, 37, 50–52], these efforts were unstructured, incomprehensive, and lacked proper explanation, leading to uncertainties. This could be the reason why these SCP cybersecurity controls are not widely recognized and used [16].
Therefore, we propose the SCP-C3 cycle in an effort to provide a viable instrument to ease criminologists and cybersecurity professionals to a common ground where they can apply their combined expertise and overcome their inherent unfamiliarity with cybercrime prevention. We have illustrated how the SCP-C3 cycle can be applied and the benefits it can bring to a multi-disciplinary SCP research environment. We also have demonstrated a structured approach on how to develop a common inventory of SCP cybersecurity controls using the ISO/IEC 27002:2022 and how the common inventory can be extended to accommodate other popular industry and government cybersecurity standards, frameworks, and guidelines. By doing so, we have created a common inventory that can be used with greater confidence even by researchers who may not be well versed in cybersecurity, SCP, or criminology.
Acknowledgements
The authors would like to acknowledge the University of Queensland Cyber Research Centre (UQ Cyber) strategic funding, and the Singapore Institute of Technology for Ho’s PhD scholarship. The authors would also like to thank the journal editors and anonymous expert reviewers for their time and constructive feedback when reviewing this manuscript.
Author contributions
Heemeng Ho (Conceptualization [lead], Investigation [lead], Methodology [lead], Project administration [lead], Writing – original draft [lead]), Ryan Ko (Conceptualization [supporting], Supervision [lead], Writing – review & editing [lead]), Lorraine Mazerolle (Conceptualization [supporting], Supervision [lead], Writing – review & editing [lead]), John Gilmour (Conceptualization [supporting], Supervision [supporting], Writing – review & editing [supporting]), and Cheng Miao (Investigation [supporting], Project administration [supporting], Writing – review & editing [supporting])
Appendix A
PRISMA 2020 Flow Diagram.
Appendix B
Detailed Discussion on Search Results for SCP Strategies and Techniques in the section ‘Results’.
‘S2 Increase the Risks’
The SCP strategy ‘S2 Increase the Risks’ comprises five SCP techniques that increase the risks of detection for potential criminal offenders [5, 31, 67]. The SCP technique ‘#6 Extend Guardianship’ intends to provide incentives to encourage unofficial guardians to act or to be more effective. Examples include having people go out in groups at night and leaving signs of occupancy. The SCP technique ‘#7 Assist Natural Surveillance’ is about creating situations where guardians are more likely to see criminal actions occurring in places, such as having improved street lighting. The SCP technique ‘#8 Reduce Anonymity’ is about creating circumstances where guardians are more likely to identify features of offenders, such as having school uniforms. The SCP technique ‘#9 Utilise Place Managers’ is about having existing or new employees emerge as potential guardians, such as providing Close Circuit Televisions (CCTVs) for bus drivers in double-decker buses. The SCP technique ‘#10 Strengthen formal surveillance’ is about creating circumstances that make formal or official guardians more effective, such as employing security guards. Table B.1 shows the number of eligible and relevant articles for this SCP strategy.
‘S2 Increase the Risks’ . | Eligible . | Relevant . |
---|---|---|
#6 Extend Guardianship | 135 | 6 |
#7 Assist Natural Surveillance | 35 | 4 |
#8 Reduce Anonymity | 94 | 2 |
#9 Utilise Place Managers | 10 | 1 |
#10 Strengthen Formal Surveillance | 35 | 4 |
Total: | 309 | 17 |
‘S2 Increase the Risks’ . | Eligible . | Relevant . |
---|---|---|
#6 Extend Guardianship | 135 | 6 |
#7 Assist Natural Surveillance | 35 | 4 |
#8 Reduce Anonymity | 94 | 2 |
#9 Utilise Place Managers | 10 | 1 |
#10 Strengthen Formal Surveillance | 35 | 4 |
Total: | 309 | 17 |
‘S2 Increase the Risks’ . | Eligible . | Relevant . |
---|---|---|
#6 Extend Guardianship | 135 | 6 |
#7 Assist Natural Surveillance | 35 | 4 |
#8 Reduce Anonymity | 94 | 2 |
#9 Utilise Place Managers | 10 | 1 |
#10 Strengthen Formal Surveillance | 35 | 4 |
Total: | 309 | 17 |
‘S2 Increase the Risks’ . | Eligible . | Relevant . |
---|---|---|
#6 Extend Guardianship | 135 | 6 |
#7 Assist Natural Surveillance | 35 | 4 |
#8 Reduce Anonymity | 94 | 2 |
#9 Utilise Place Managers | 10 | 1 |
#10 Strengthen Formal Surveillance | 35 | 4 |
Total: | 309 | 17 |
For the SCP techniques ‘#6 Extend Guardianship’, there were 135 eligible articles for review. There were six relevant articles. Bossler and Holt [93] used RAT as a framework to explain the relationships between online activities, guardianship, and malware infections and noted that reducing malware infection requires both cybersecurity solutions and behavioural changes. Vakhitova and Reynald [94] presented an empirical analysis of guardianship against cyber abuse such as cyberstalking and noted that active guardianship processes such as contextual awareness in the physical world worked in a similar manner in cyberspace. Reyns et al. [95] used RAT to examine the concept of guardianship and its role in reducing cyberstalking victimization. Reynald et al. [96] examined the importance of micro-level environmental factors in the development of new directions in guardianship research such as in cyberspace. Reynald [74] proposed a conceptual paper to advance and extend digital guardianships using technological advancements such as digital neighbourhood watch or community safety applications. Ylang [97] discussed the concept of guardianships against online identity theft and examined the demographic differences in individuals who practice self-guardianship. The remaining articles were not relevant because they did not discuss the application of SCP to cybercrimes or were not about encouraging unofficial guardians to act or be more effective [31].
The SCP techniques ‘#7 Assist Natural Surveillance’ and ‘#10 Strengthen Formal Surveillance’ share the common keyword ‘surveillance’ and both resulted in the same list of 35 eligible research articles. There were four relevant articles that offered insights on cyber-related surveillance that could help guardians detect offenders. Huey and Rosenberg [98] discussed the growth in internet surveillance and policing after the signing by countries of the Convention on Cybercrime in 2001 that mandates Internet Service Providers to provide assistance to law enforcement. Palasinki and Bowman-Grieve [99] highlighted the tension and the need to balance surveillance with counter communication in tackling cyberterrorism. Snášel et al. [100] proposed a framework for cyber-surveillance for critical infrastructure using computational grids, which could assist guardians in identifying cybercriminal activities. Chung et al. [77] proposed a Cyber-Trafficking Surveillance System that supports analysis of social media content to counter cyber-trafficking. The remaining articles discussed technical details on surveillance largely in the areas of cyber-physical systems, drone, video, and air traffic surveillance and were not relevant because they did not discuss the application of SCP to cybercrimes or were not about creating situations where guardians are more likely to see criminal actions [31].
For the SCP technique ‘#8 Reduce Anonymity’, there were 94 eligible articles for review. There were two relevant articles. David and Sakurai [75] and Murdoch and Leaver [76] both proposed the creation of cyber-entities, such as the Cyber Intelligence Analysis Center (CIAC) to develop and share information to reduce offenders’ anonymity. The remaining articles were not relevant. They mainly discussed the impact, preservation, and improvements of anonymity and were not related to the application of SCP into cybercrimes or suggested any ways to make it easier for guardians to reduce offenders’ anonymity [31].
For the SCP technique ‘#9 Utilise Place Managers’, there were 10 eligible articles for review. There was one relevant article. Reyns [48] discussed the use of SCP techniques, especially by cyberplace managers to control and limit cyberstalking. The remaining articles were not relevant because they did not discuss the role of existing or new employees or managers as guardians in cyberspace to limit cybercrime opportunities [31].
‘S3 Reduce the Rewards’
The SCP strategy ‘S3 Remove the Rewards’ aims to present situational control techniques that can reduce the rewards of the crime for the offender [5, 31, 67]. The SCP technique ‘#11 Conceal Targets’ and the SCP technique ‘#12 Remove Targets’ limit the offender’s ability to see the target or victim either through concealment or by removing them or their value. This makes it difficult for the offender to find the target or victim in a situation, for example, using unmarked armoured trucks to transport valuables. The third SCP technique in this strategy, ‘#13 Identify Property’, marks items to make them traceable to the owner or makes it more difficult for the offender to claim ownership. For example, vehicle licensing makes it hard for offenders to claim ownership of stolen vehicles when stopped by law enforcement. The SCP techniques ‘#14 Disrupt Markets’ and ‘#15 Deny Benefits’ make it difficult for offenders to realize the benefits of their crimes. The former increases the difficulty for offenders to transfer or dispose of their illegal criminal proceeds while the latter makes it hard for offenders to use their crime targets for their intended purpose. For example, putting speed humps on roads makes it difficult for offenders to speed. Table B.2 shows the number of eligible and relevant articles for this SCP strategy.
‘S3 Reduce the Rewards’ . | Eligible . | Relevant . |
---|---|---|
#11 Conceal Targets | 32 | 1 |
#12 Remove Targets | 33 | 1 |
#13 Identify Property | 41 | 0 |
#14 Disrupt Markets | 40 | 0 |
#15 Deny Benefits | 15 | 0 |
Total: | 161 | 2 |
‘S3 Reduce the Rewards’ . | Eligible . | Relevant . |
---|---|---|
#11 Conceal Targets | 32 | 1 |
#12 Remove Targets | 33 | 1 |
#13 Identify Property | 41 | 0 |
#14 Disrupt Markets | 40 | 0 |
#15 Deny Benefits | 15 | 0 |
Total: | 161 | 2 |
‘S3 Reduce the Rewards’ . | Eligible . | Relevant . |
---|---|---|
#11 Conceal Targets | 32 | 1 |
#12 Remove Targets | 33 | 1 |
#13 Identify Property | 41 | 0 |
#14 Disrupt Markets | 40 | 0 |
#15 Deny Benefits | 15 | 0 |
Total: | 161 | 2 |
‘S3 Reduce the Rewards’ . | Eligible . | Relevant . |
---|---|---|
#11 Conceal Targets | 32 | 1 |
#12 Remove Targets | 33 | 1 |
#13 Identify Property | 41 | 0 |
#14 Disrupt Markets | 40 | 0 |
#15 Deny Benefits | 15 | 0 |
Total: | 161 | 2 |
There were 32 and 33 eligible articles for review on the SCP techniques ‘#11 Conceal Targets’ and ‘#12 Remove Targets’, respectively. These articles largely engage with the same concepts as the previous SCP technique ‘#1 Harden Targets’, including one relevant article by Miró-Llinares et al. [68] that was discussed in Section ‘4.1.1’. The remaining articles were not relevant because they did not discuss the application of SCP into cybercrimes or were not about concealing or removing targets from the offender [31].
There were 41 eligible articles for review on the SCP technique ‘#13 Identify Property’. The articles mainly discussed research topics related to investigation and analysis on the attributes and properties of cyber-physical systems, computer hardware, bioinformatics, and legal matters. There were no relevant articles related to the application of SCP to cybercrimes or about identifying or marking targets to make them traceable [31].
There were 40 eligible articles for review on the SCP technique ‘#14 Disrupt Markets’. The articles mainly discussed research topics related to the cyber insurance market, electrical and power energy markets, and dark net markets. There were no relevant articles related to the application of SCP to cybercrimes or about disrupting the criminal markets to make it difficult for offenders to transfer the proceeds of crime [31].
There were 15 eligible articles for review on the SCP technique ‘#15 Deny Benefits’. The articles mainly discussed research into cyber-physical systems. There were no relevant articles related to the application of SCP into cybercrimes or that suggested any ways to make it difficult for offenders to use crime targets for their intended purpose [31].
‘S4 Reduce Provocations’
The SCP strategy ‘S4 Reduce Provocations’ aims to address Wortley’s [30] emotionally driven situational precipitators such as frustrations and stress. It presents situational control techniques that limit situational stimuli that can lead to criminal actions [5, 31, 67]. The SCP technique ‘#16 Reduce Frustrations’ promotes settings that are calming or procedures that are efficient, which in turn reduces peoples’ frustrations. For example, having soothing music or ensuring efficient queues and creating polite service can reduce frustrations and stress and prevent aggressive behaviour. The SCP technique ‘#17 Avoid Disputes’ limits circumstances that promote conflicts or disputes or encourage their escalation, such as having fixed cab fares so that there will not be any fare disputes. The SCP technique ‘#18 Reduce Emotional Arousal’ limits emotional or insulting behaviours or stimuli in a setting, such as prohibiting racial slurs in a setting that could otherwise trigger aggressive reactions. The SCP technique ‘#19 Neutralise Peer Pressure’ reduces the desire to gain acceptance through criminal actions. The SCP technique ‘#20 Discourage Imitation’ seeks to limit access to details of the crime commission processes to prevent criminal copycats. Table B.3 shows the number of eligible and relevant articles for this SCP strategy.
Number of eligible and relevant articles for SCP ‘S4 Reduce Provocation’.
‘S4 Reduce Provocations’ . | Eligible . | Relevant . |
---|---|---|
#16 Reduce Frustrations and Stress | 73 | 2 |
#17 Avoid Disputes | 136 | 3 |
#18 Reduce Emotional Arousal | 31 | 1 |
#19 Neutralise Peer Pressure | 48 | 0 |
#20 Discourage Imitation | 151 | 0 |
Total: | 439 | 6 |
‘S4 Reduce Provocations’ . | Eligible . | Relevant . |
---|---|---|
#16 Reduce Frustrations and Stress | 73 | 2 |
#17 Avoid Disputes | 136 | 3 |
#18 Reduce Emotional Arousal | 31 | 1 |
#19 Neutralise Peer Pressure | 48 | 0 |
#20 Discourage Imitation | 151 | 0 |
Total: | 439 | 6 |
Number of eligible and relevant articles for SCP ‘S4 Reduce Provocation’.
‘S4 Reduce Provocations’ . | Eligible . | Relevant . |
---|---|---|
#16 Reduce Frustrations and Stress | 73 | 2 |
#17 Avoid Disputes | 136 | 3 |
#18 Reduce Emotional Arousal | 31 | 1 |
#19 Neutralise Peer Pressure | 48 | 0 |
#20 Discourage Imitation | 151 | 0 |
Total: | 439 | 6 |
‘S4 Reduce Provocations’ . | Eligible . | Relevant . |
---|---|---|
#16 Reduce Frustrations and Stress | 73 | 2 |
#17 Avoid Disputes | 136 | 3 |
#18 Reduce Emotional Arousal | 31 | 1 |
#19 Neutralise Peer Pressure | 48 | 0 |
#20 Discourage Imitation | 151 | 0 |
Total: | 439 | 6 |
There were 73 eligible articles for review on the SCP technique ‘#16 Reduce Frustrations and Stress’. There were two relevant articles. Sandoval et al. [101] discussed factors that can make cyber operations stressful and suggested the use of cyber-physical systems, biometric stress instrumentation, and new technologies such as augmented reality and virtual reality, to manage stress. Hone [102] suggested that female embodied agents may be more effective in reducing user frustrations in human–computer interaction systems. The remaining non-relevant articles mainly discussed issues related to material science and did not discuss the application of SCP to cybercrimes or to creating settings that were calming [31].
There were 136 eligible articles for review on the SCP technique ‘#17 Avoid Disputes’. There were three relevant articles. Sondheimer et al. [103] highlighted the need to prevent and resolve disputes in the networked health IT arena and suggested solutions such as designing the systems for privacy and providing support tools. Billings and Watts [104] described how conflicts in online text-based web communities such as Wikipedia can be effectively managed through appropriate policies and technical measures. Osterweil and Clarke [105] discussed how software technology can support dispute resolution. The remaining articles were mainly on resolving disputes in the facility construction or legal disputes and were not about the application of SCP into cybercrimes or about limiting situations that promote conflicts or disputes [31].
For the SCP technique ‘#18 Reduce Emotional Arousal’, there were 31 eligible articles for review. There was one relevant article. Lu et al. [106] highlighted that cyber scam prevention posters should focus on the emotions of potential victims to be more effective. The remaining articles were not relevant because they mainly discussed research on the effects of emotions and were not related to the application of SCP into cybercrimes or did not suggest any ways to remove or limit emotional or insulting behaviours or stimuli [31].
There were 48 eligible articles for review on the SCP technique ‘#19 Neutralise Peer Pressure’. The articles mainly discussed research topics related to adolescent peer pressure. There were no relevant articles related to the application of SCP to cybercrimes or about discouraging the desire to gain acceptance through criminal actions [31].
There were 151 eligible articles for review on the SCP technique ‘#20 Discourage Imitation’. The articles mainly discussed research topics related to young children or artificial intelligence. There were no relevant articles related to the application of SCP to cybercrimes or about limiting access to details of the crime processes that can prevent criminal copycats [31].
‘S5 Remove Excuses’
The SCP strategy ‘S5 Remove Excuses’ aims to present situational control techniques that can clarify the responsibility of a potential offender in a setting such as a workplace in an organization [5, 31]. It incorporates strategies that were adapted from Wortley [30] on situational precipitators. The SCP technique ‘#21 Set Rules’ is about providing information about what are unacceptable behaviours in a situation or setting, such as a rental agreement. The SCP technique ‘#22 Post Instructions’ provides information on how to meet the behavioural requirements of a setting, such as posting ‘No Parking’ signs. The SCP technique ‘#23 Alert conscience’ is about providing situational reminders on the unacceptable aspects of certain behaviours in a setting, such as having a roadside speed display board to remind drivers not to go beyond a certain speed limit. The SCP technique ‘#24 Assist compliance’ is about creating situations or aids that can make it easier for people to carry out acceptable behaviour, such as providing litter receptacles for easier waste disposal. The SCP technique ‘#25 Control drugs and alcohol’ is about limiting drugs and alcohol, which can influence a person’s thinking and behaviour. Table B.4 shows the number of eligible and relevant articles for this SCP strategy.
‘S5 Remove Excuses’ . | Eligible . | Relevant . |
---|---|---|
#21 Set Rules | 77 | 2 |
#22 Post Instructions | 20 | 0 |
#23 Alert Conscience | 35 | 0 |
#24 Assist Compliance | 22 | 11 |
#25 Control Drugs and Alcohol | 74 | 11 |
Total: | 228 | 24 |
‘S5 Remove Excuses’ . | Eligible . | Relevant . |
---|---|---|
#21 Set Rules | 77 | 2 |
#22 Post Instructions | 20 | 0 |
#23 Alert Conscience | 35 | 0 |
#24 Assist Compliance | 22 | 11 |
#25 Control Drugs and Alcohol | 74 | 11 |
Total: | 228 | 24 |
‘S5 Remove Excuses’ . | Eligible . | Relevant . |
---|---|---|
#21 Set Rules | 77 | 2 |
#22 Post Instructions | 20 | 0 |
#23 Alert Conscience | 35 | 0 |
#24 Assist Compliance | 22 | 11 |
#25 Control Drugs and Alcohol | 74 | 11 |
Total: | 228 | 24 |
‘S5 Remove Excuses’ . | Eligible . | Relevant . |
---|---|---|
#21 Set Rules | 77 | 2 |
#22 Post Instructions | 20 | 0 |
#23 Alert Conscience | 35 | 0 |
#24 Assist Compliance | 22 | 11 |
#25 Control Drugs and Alcohol | 74 | 11 |
Total: | 228 | 24 |
There were 77 eligible articles for review on the SCP technique ‘#21 Set Rules’. There were two relevant articles [107, 108] that highlighted the challenge and use of international rules and legislation to prevent unacceptable behaviours in cyberspace to combat cybercrimes. The remaining articles either referred to mathematical, logic, or software rules used in computer science domains such as databases or referred to trademark and maritime transportation rules. Such articles were not relevant to our study because they did not discuss the application of SCP to cybercrimes or were not about setting rules on unacceptable behaviours in a setting, especially on cyberspace [31].
There were 20 eligible articles for review on the SCP technique ‘#22 Post Instructions’. All the articles discussed research topics related to computer hardware and software instructions, court cases and post-traumatic stress disorder. There were no relevant articles related to the application of SCP to cybercrimes or about putting up instructions on meeting behavioural requirements in a setting [31].
There were 35 eligible articles for review on the SCP technique ‘#23 Alert Conscience’. All these articles discussed either human/political conscience in the context of professional activities and the use of anti-personnel mines or mainly discussed computer conscience mechanisms in the context of neural networks, AI, virtual reality (VR), data mining, and robotics. Such articles were not relevant as they were not related to the application of SCP to cybercrimes or about providing situational reminders on unacceptable aspects of certain behaviours in a setting [31].
For the SCP technique ‘#24 Assist Compliance’, there were 22 eligible articles for review. There were 11 relevant articles. These articles [109–119] described various tools and methods to aid compliance with cybersecurity practices in order to prevent cyberattacks and cybercrimes. For example, Kienzle et al. [109] proposed a system to monitor the endpoint configuration of an end-user system for compliance purposes. All approaches discussed in the articles essentially made it easier for people to carry out acceptable behaviour in an organizational setting to prevent cyberattacks and cybercrimes. The remaining non-relevant articles discussed non-cybersecurity or cybercrime compliances such as social distancing compliances, medication compliances, and electronic compliance controls with to mobility devices, such as wheelchairs and wearable power assist equipment. These articles were not relevant because they did not discuss the application of SCP to cybercrimes or were not about assisting people to comply with acceptable behaviours in a setting [31].
For the SCP technique ‘#25 Control Drugs and Alcohol’, there were 74 eligible articles for review. There were 11 relevant articles [120–130]. These articles mainly suggested different ways and methods using hardware or software tools to detect the consumption of alcohol, which can be used by organizations to detect and limit employees’ drugs and alcohol consumption. For example, You et al. [127] proposed using transdermal sensing wristbands as a personal tool to track alcohol use. The remaining articles were not relevant because they were about issues or effects of drug and alcohol abuse and did not focus on limiting the availability of drugs and alcohol in situations related to cybercrimes [31].
Appendix C
Detailed Explanation of Classification of ISO/IEC 27002:2022 Controls into SCP Strategies and Techniques
No. . | SCP technique . | Clause type . | ISO/IEC control . | ISO/IEC control description and purpose . | Rationale . |
---|---|---|---|---|---|
S1 INCREASE THE EFFORTS aims to block or limit the actions or movements of offenders[31]. | |||||
SCP ‘#01 Harden Targets’ makes it more difficult for offenders to get to or use the target to achieve their criminal purposes [31]. | |||||
1 | #01 Harden Targets | Organizational | 5.08 Information security in project management | Information security should be integrated into project management. The purpose is to ensure information security risks related to projects and deliverables are effectively addressed in project management throughout the project life cycle. | Integrating information security into project management can make the project more secure and therefore more difficult for the offender to get to or use the target to achieve criminal purposes (such as ransomware or DDoS attacks). |
2 | #01 Harden Targets | Organizational | 5.19 Information security in supplier relationships | Processes and procedures should be defined and implemented to manage the information security risks associated with the use of supplier's products or services. The purpose is to maintain an agreed level of information security in supplier relationships. | Managing information security risks about the use of supplier products and services can make it more difficult for the offender to get to or use the target (such as the supplier products and services) to achieve criminal purposes (such as ransomware or DDoS attacks). |
3 | #01 Harden Targets | Organizational | 5.20 Addressing information security within supplier agreements | Relevant information security requirements should be established and agreed with each supplier based on the type of supplier relationship. The purpose is to maintain an agreed level of information security in supplier relationships. | Establishing information security requirements for suppliers can make it more difficult for the offender to get to or use the target (such as the supplier products and services) to achieve criminal purposes (such as ransomware or DDoS attacks). |
4 | #01 Harden Targets | Organizational | 5.21 Managing information security in the ICT supply chain | Processes and procedures should be defined and implemented to manage information security risks associated with the ICT products and services supply chain. The purpose is to maintain an agreed level of information security in supplier relationships. | Managing information security risks about the ICT products and services supply chain can make it more difficult for the offender to get to or use the target (such as ICT supply chain) to achieve criminal purposes (such as ransomware or DDoS attacks). |
5 | #01 Harden Targets | Organizational | 5.23 Information security for use of cloud services | Processes for acquisition, use, management, and exit from cloud services should be established in accordance with the organization's information security requirements. The purpose is to specify and manage information security for the use of cloud services. | Specifying and managing information security for the use of cloud services can make it more difficult for the offender to get to or use the target (such as information systems and data stored in cloud) to achieve criminal purposes. |
6 | #01 Harden Targets | Organizational | 5.27 Learning from information security incidents | Knowledge gained from information security incidents should be used to strengthen and improve the information security controls. The purpose is to reduce the likelihood or consequences of future incidents. | Learning from information security events can reduce the likelihood or consequences of future incidents. This in turn makes it more difficult for the offender to get to or use the target to achieve the criminal purpose (such as ransomware or DDoS attacks). |
7 | #01 Harden Targets | Organizational | 5.29 Information security during disruption | The organization should plan how to maintain information security at an appropriate level during disruption. The purpose is to protect information and other associated assets during disruption. | The ability to maintain information security despite disruption can make it more difficult for the offender to get to or use the target (such as information systems that are affected by disruption) to achieve criminal purposes (such as ransomware or DDoS attacks). |
8 | #01 Harden Targets | Organizational | 5.33 Protection of records | Records should be protected from loss, destruction, falsification, unauthorized access, and unauthorized release. The purpose is to ensure compliance with legal, statutory, regulatory, and contractual requirements, as well as community or societal expectations related to the protection and availability of records. | Ensuring that the records are protected can make it more difficult for offenders to use the crime targets (such as data losses) for their intended purposes (such as DDoS and ransomware attacks). |
9 | #01 Harden Targets | Organizational | 5.35 Independent review of information security | The organization’s approach to managing information security and its implementation, including people, processes, and technologies, should be reviewed independently at planned intervals, or when significant changes occur. The purpose is to ensure the continuing suitability, adequacy, and effectiveness of the organization’s approach to managing information security. | Having an independent review of information security can identify potential weaknesses that can be fixed before they are actually exploited by offenders. This in turn makes it more difficult for the offender to get to or use the target to achieve the criminal purpose (such as ransomware or DDoS attacks). |
10 | #01 Harden Targets | People | 6.07 Remote working | Security measures should be implemented when personnel are working remotely to protect information accessed, processed, or stored outside the organization’s premises. The purpose is to ensure the security of information when personnel are working remotely. | Implementing security measures when personnel are working remotely will make it more difficult for offender to get to or use the target (such as employees working remotely) to achieve the criminal purposes (such as ransomware or DDoS attacks). |
11 | #01 Harden Targets | Physical | 7.03 Securing offices, rooms, and facilities | Physical security for offices, rooms and facilities should be designed and implemented. The purpose is to prevent unauthorized physical access, damage and interference to the organization’s information and other associated assets in offices, rooms and facilities. | Securing offices, rooms, and facilities can make it more difficult for the offender to get to or use the target (such as offices) to achieve criminal purposes (such as ransomware or DDoS attacks). |
12 | #01 Harden Targets | Physical | 7.05 Protecting against physical and environmental threats | Protection against physical and environmental threats, such as natural disasters and other intentional or unintentional physical threats to infrastructure should be designed and implemented. The purpose is to prevent or reduce the consequences of events originating from physical and environmental threats. | Protection against physical and environmental threats can make it more difficult for offenders to make use of these threats to get to or use the target (such as computing infrastructure) to achieve criminal purposes (such as ransomware or DDoS attacks). |
13 | #01 Harden Targets | Physical | 7.06 Working in secure areas | Security measures for working in secure areas should be designed and implemented. The purpose is to protect information and other associated assets in secure areas from damage and unauthorized interference by personnel working in these areas. | Security measures for working in secure areas can make it more difficult for the offender to get to or use the target (such as sensitive office areas) to achieve the criminal purposes (such as ransomware or DDoS attacks). |
14 | #01 Harden Targets | Physical | 7.08 Equipment siting and protection | Equipment should be sited securely and protected. The purpose is to reduce the risks from physical and environmental threats, and from unauthorized access and damage. | Equipment that is sited securely and protected can make it more difficult for the offender to get to or use the target to achieve criminal purposes. |
15 | #01 Harden Targets | Physical | 7.09 Security of assets off-premises | Off-site assets should be protected. The purpose is to prevent loss, damage, theft, or compromise of off-site assets and interruption to the organization’s operations. | Protecting off-site assets can make it more difficult for the offender to get to or use the target (such as assets) to achieve criminal purposes (such as ransomware or DDoS attacks). |
16 | #01 Harden Targets | Physical | 7.10 Storage media | Storage media should be managed through its life cycle of acquisition, use, transportation, and disposal in accordance with the organization’s classification scheme and handling requirements. The purpose is to ensure only authorized disclosure, modification, removal, or destruction of information on storage media. | Managing storage media can make it more difficult for the offender to get to or use the target (such as storage media) to achieve criminal purposes (such as ransomware or DDoS attacks). |
17 | #01 Harden Targets | Physical | 7.11 Supporting utilities | Information processing facilities should be protected from power failures and other disruptions caused by failures in supporting utilities. The purpose is to prevent loss, damage, or compromise of information and other associated assets, or interruption to the organization’s operations due to the failure and disruption of supporting utilities. | Information processing facilities should be protected from power failures and other disruptions caused by failures in supporting utilities. |
18 | #01 Harden Targets | Physical | 7.12 Cabling security | Cables carrying power, data, or supporting information services should be protected from interception, interference, or damage. The purpose is to prevent loss, damage, theft, or compromise of information and other associated assets and interruption to the organization’s operations related to power and communications cabling. | Protecting cables can make it more difficult for the offender to get to or use the target (such as cables) to achieve criminal purposes (such as ransomware or DDoS attacks). |
19 | #01 Harden Targets | Physical | 7.13 Equipment maintenance | Equipment should be maintained correctly to ensure availability, integrity, and confidentiality of information. The purpose is to prevent loss, damage, theft, or compromise of information and other associated assets and interruption to the organization’s operations caused by lack of maintenance. | Maintaining equipment can make it more difficult for the offender to get to or use the target (such as equipment) to achieve criminal purposes (such as ransomware or DDoS attacks). |
20 | #01 Harden Targets | Technological | 8.01 User endpoint devices | Information stored on, processed by, or accessible via user endpoint devices should be protected. The purpose is to protect information against the risks introduced by using user endpoint devices. | Protecting user endpoint devices can make it more difficult for the offender to get to or use the target (such as user endpoint devices) to achieve criminal purposes (such as ransomware or DDoS attacks). |
21 | #01 Harden Targets | Technological | 8.07 Protection against malware | Protection against malware should be implemented and supported by appropriate user awareness. The purpose is to ensure information and other associated assets are protected against malware. | Protection against malware can make it more difficult for the offender to get to or use the target (such as computing devices) to achieve criminal purposes (such as ransomware or DDoS attacks). |
22 | #01 Harden Targets | Technological | 8.08 Management of technical vulnerabilities | 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. The purpose is to prevent exploitation of technical vulnerabilities. | Managing technical vulnerabilities in information systems can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
23 | #01 Harden Targets | Technological | 8.09 Configuration management | Configurations, including security configurations, of hardware, software, services, and networks should be established, documented, implemented, monitored, and reviewed. The purpose is to ensure hardware, software, services, and networks function correctly with required security settings, and configuration is not altered by unauthorized or incorrect changes. | Managing configurations can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
24 | #01 Harden Targets | Technological | 8.23 Web filtering | Access to external websites should be managed to reduce exposure to malicious content. The purpose is to protect systems from being compromised by malware and to prevent access to unauthorized web resources. | Managing access to external websites can make it more difficult for the offender to get to or use the target (such as external websites) to achieve criminal purposes (such as downloading malware for subsequent cyberattacks). |
25 | #01 Harden Targets | Technological | 8.25 Secure development life cycle | Rules for the secure development of software and systems should be established and applied. The purpose is to ensure information security is designed and implemented within the secure development life cycle of software and systems. | Secure development of software can make it more difficult for the offender to get to or use the target (such as software) to achieve criminal purposes (such as ransomware or DDoS attacks). |
26 | #01 Harden Targets | Technological | 8.26 Application security requirements | Information security requirements should be identified, specified, and approved when developing or acquiring applications. The purpose is to ensure all information security requirements are identified and addressed when developing or acquiring applications. | Identifying and addressing application security requirements can make it more difficult for the offender to get to or use the target (such as application) to achieve criminal purposes (such as ransomware or DDoS attacks). |
27 | #01 Harden Targets | Technological | 8.27 Secure system architecture and engineering principles | Principles for engineering secure systems should be established, documented, maintained, and applied to any information system development activities. The purpose is to ensure information systems are securely designed, implemented, and operated within the development life cycle. | Applying secure system architecture and engineering principles can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
28 | #01 Harden Targets | Technological | 8.28 Secure coding | Secure coding principles should be applied to software development. The purpose is to ensure software is written securely, thereby reducing the number of potential information security vulnerabilities in the software. | Applying secure coding principles can make it more difficult for the offender to get to or use the target (such as software) to achieve criminal purposes (such as ransomware or DDoS attacks). |
29 | #01 Harden Targets | Technological | 8.29 Security testing in development and acceptance | Security testing processes should be defined and implemented in the development life cycle. The purpose is to validate if information security requirements are met when applications or code are deployed to the production environment. | Security testing can make it more difficult for the offender to get to or use the target (such as applications and websites) to achieve criminal purposes (such as ransomware or DDoS attacks). |
30 | #01 Harden Targets | Technological | 8.30 Outsourced development | The organization should direct, monitor, and review the activities related to outsourced system development. The purpose is to ensure information security measures required by the organization are implemented in outsourced system development. | Ensuring that information security measures required by the organization are implemented in outsourced system development can make it more difficult for the offender to get to or use the target to achieve criminal purposes. |
31 | #01 Harden Targets | Technological | 8.32 Change management | Changes to information processing facilities and information systems should be subject to change management procedures. The purpose is to preserve information security when executing changes. | Managing change management can make it more difficult for the offender to get to or use the target (such as applications and websites) to achieve criminal purposes (such as ransomware or DDoS attacks). |
32 | #01 Harden Targets | Technological | 8.33 Test information | Test information should be appropriately selected, protected, and managed. The purpose is to ensure relevance of testing and protection of operational information used for testing. | Protecting test information can make it more difficult for the offender to get to or use the target (such as test information) to achieve criminal purposes (such as cyber reconnaissance). |
33 | #01 Harden Targets | Technological | 8.34 Protection of information systems during audit testing | Audit tests and other assurance activities involving assessment of operational systems should be planned and agreed between the tester and appropriate management. The purpose is to minimize the impact of audit and other assurance activities on operational systems and business processes. | Protecting information systems during audit testing can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
SCP ‘#02 Control Access to Facilities’ aims to block offenders access to places where they may carry out a criminal action [31]. | |||||
34 | #05 Control Tools/Weapons | Organizational | 5.15 Access control | Returning the organization’s assets upon the end of the employment, contract, or agreement can prevent and block the ex-employee from using the organization’s assets (such as notebooks, access cards, and keys) to access the organization’s places and assets. | Returning the organization’s assets upon the end of the employment, contract, or agreement can limit offender access to these instruments (such as notebooks, access cards, and keys) associated with particular modus operandi (such as hacking, DDoS, and ransomware attacks). |
35 | #02 Control Access to Facilities | Organizational | 5.15 Access 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. The purpose is to ensure authorized access and to prevent unauthorized access to information and other associated assets. | Controlling physical and logical access to information and related assets can block access to places (such as applications and websites) where a criminal action (such as data breach) may be carried out. |
36 | #02 Control Access to Facilities | Organizational | 5.18 Access rights | Access rights to information and other associated assets should be provisioned, reviewed, modified, and removed in accordance with the organization’s topic-specific policy on and rules for access control. The purpose is to ensure access to information and other associated assets is defined and authorized according to the business requirements. | Controlling the access rights to information and associated assets can block access to places (such as applications and websites) where a criminal action (such as data breach) may be carried out. |
37 | #02 Control Access to Facilities | Physical | 7.01 Physical security perimeters | Security perimeters should be defined and used to protect areas that contain information and other associated assets. | Physical security perimeters can block access to places (such as data centres) where a criminal action (such as hacking) may be carried out. |
38 | #02 Control Access to Facilities | Physical | 7.02 Physical entry | Secure areas should be protected by appropriate entry controls and access points. The purpose is to ensure only authorized physical access to the organization’s information and other associated assets occurs. | Physical entries can block access to places (such as data centres) where a criminal action (such as hacking) may be carried out. |
39 | #02 Control Access to Facilities | Technological | 8.02 Privileged access rights | The allocation and use of privileged access rights should be restricted and managed. The purpose is to ensure only authorized users, software components, and services are provided with privileged access rights. | Controlling privileged access rights can block access to places (such as applications and websites) where criminal action (such as ransomware and hacking) may be carried out. |
40 | #02 Control Access to Facilities | Technological | 8.20 Networks security | Networks and network devices should be secured, managed, and controlled to protect information in systems and applications. The purpose is to protect information in networks and its supporting information processing facilities from compromise via the network. | Protecting networks, which are gateways to places (such as computing devices and websites) can block access to places where criminal actions (such as hacking and data breaches) may be carried out. |
41 | #02 Control Access to Facilities | Technological | 8.21 Security of network services | Security mechanisms, service levels, and service requirements of network services should be identified, implemented, and monitored. The purpose is to ensure security in the use of network services. | Protecting network services, which are gateways to places (such as computing devices and websites) can block access to places where criminal actions (such as hacking and data breaches) may be carried out. |
SCP ‘#03 Screen Exits’ aims to make it more difficult for the offender to leave a place after their criminal action [31]. | |||||
42 | #03 Screen Exits | Technological | 8.12 Data leakage prevention | Data leakage prevention measures should be applied to systems, networks, and any other devices that process, store, or transmit sensitive information. The purpose is to detect and prevent the unauthorized disclosure and extraction of information by individuals or systems. | Data leakage prevention measures can make it more difficult for the offender to leave a place (such as network perimeter) after a criminal action (such as data leakage). |
SCP ‘#04 Deflect offenders’ aims to change the offender’s existing or potential movement patterns [31]. | |||||
43 | #04 Deflect offenders | Technological | 8.22 Segregation of networks | Groups of information services, users, and information systems should be segregated in the organization’s networks. The purpose is to split the network in security boundaries and to control traffic between them based on business needs. | Segregating networks can change existing or potential offender movement patterns (such as hacking patterns). |
44 | #04 Deflect offenders | Technological | 8.31 Separation of development, test and production environments | Development, testing, and production environments should be separated and secured. The purpose is to protect the production environment and data from compromise by development and test activities. | Separating the development, test, and production environments can change existing or potential offender movement patterns (such as hacking patterns). |
SCP ‘#05 Control Tools/Weapons’ aims to limit offender access to or use instruments associated with a criminal modus operandi [31]. | |||||
45 | #05 Control Tools/Weapons | Technological | 8.18 Use of privileged utility programs | The use of utility programs that can be capable of overriding system and application controls should be restricted and tightly controlled. The purpose is to ensure the use of utility programs does not harm system and application controls for information security. | Restricting and controlling privileged utility programs that can be misused can limit offender access to these instruments (such as privileged utility programs) associated with particular modus operandi (such as hacking, DDoS, and ransomware attacks). |
46 | #05 Control Tools/Weapons | Technological | 8.19 Installation of software on operational systems | Procedures and measures should be implemented to securely manage software installation on operational systems. The purpose is to ensure the integrity of operational systems and prevent exploitation of technical vulnerabilities. | Managing installation of software that can be misused (such as rootkits and trojans) can limit offender access to these instruments (such as software on operational systems) associated with particular modus operandi (such as hacking, DDoS, and ransomware attacks). |
S2 Increase the Risks aims to provide more or better guardianship to increase the likelihood of detecting offenders[31]. | |||||
SCP ‘#06 Extend Guardianships’ aims to provide incentives to encourage unofficial guardians to act or be more effective [31]. | |||||
47 | #06 Extend Guardianships | People | 6.08 Information security event reporting | The organization should provide a mechanism for personnel to report observed or suspected information security events through appropriate channels in a timely manner. The purpose is to support timely, consistent, and effective reporting of information security events that can be identified by personnel. | A mechanism for personnel to report information security events will provide incentives to encourage unofficial guardians (such as employees, contractors, and users) to act or be more effective because there is a channel for them to report. |
SCP ‘#07 Assist natural surveillance’ aims to increase the likelihood that potential guardians will see criminal actions happening in places [31]. | |||||
48 | #07 Assist natural surveillance | Organizational | 5.22 Monitoring, review and change management of supplier services | The organization should regularly monitor, review, evaluate, and manage change in supplier information security practices and service delivery. The purpose is to maintain an agreed level of information security and service delivery in line with supplier agreements. | Regularly reviewing supplier information security practices and service delivery can increase the likelihood that guardians (such as owners of supplier services) will see any criminal actions occurring in places belonging to the supplier. |
SCP ‘#08 Reduce Anonymity’ aims to increase the likelihood that potential guardians will identify the features of offenders [31]. | |||||
49 | #08 Reduce Anonymity | Organizational | 5.06 Contact with special interest groups | The organization should establish and maintain contact with special interest groups or other specialist security forums and professional associations. The purpose is to ensure appropriate flow of information takes place with respect to information security. | Contacting special interest groups or other specialist security forums and professional associations to exchange cybersecurity information increases the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of potential offenders (such as hackers). |
50 | #08 Reduce Anonymity | Organizational | 5.16 Identity management | The full life cycle of identities should be managed. The purpose is to allow for the unique identification of individuals and systems accessing the organization’s information and other associated assets and to enable appropriate assignment of access rights. | Identity management increases the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of potential offenders (such as hackers). |
51 | #08 Reduce Anonymity | Organizational | 5.17 Authentication information | Allocation and management of authentication information should be controlled by a management process, including advising personnel of appropriate handling of authentication information. The purpose is to ensure proper entity authentication and prevent failures of authentication processes. | Properly managing authentication information increases the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of potential offenders (such as hackers). |
52 | #08 Reduce Anonymity | People | 6.01 Screening | Background verification checks on all candidates to become personnel should be carried out prior to joining the organization and on an ongoing basis taking into consideration applicable laws, regulations, and ethics, and be proportional to the business requirements, the classification of the information to be accessed, and the perceived risks. The purpose is to ensure all personnel are eligible and suitable for the roles for which they are considered and remain eligible and suitable during their employment. | Background screening can increase the likelihood that potential guardians (such as human resource department) can identify the features of the offenders (such as insiders). |
53 | #08 Reduce Anonymity | Technological | 8.05 Secure authentication | Secure authentication technologies and procedures should be implemented based on information access restrictions and the topic-specific policy on access control. The purpose is to ensure a user, or an entity is securely authenticated, when access to systems, applications, and services is granted. | Secure authentication can increase the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of offenders (such as hackers). |
SCP ‘#09 Utilise Place Managers’ aims to use existing or new employees or managers as potential guardians or to change the settings to limit criminal opportunities [31]. | |||||
54 | #09 Utilise Place Managers | Organizational | 5.02 Information security roles and responsibilities | Information security roles and responsibilities should be defined and allocated according to the organization needs. The purpose is to establish a defined, approved, and understood structure for the implementation, operation, and management of information security within the organization. | Existing or new employees are used as potential guardians (such as cybersecurity professionals and Security Operation Centres) in information security roles. |
SCP ‘#10 Strengthen Formal Surveillance’ aims to provide official or formal guardians or increase their ability to be more effective in dealing with criminal opportunities [31]. | |||||
55 | #10 Strengthen Formal Surveillance | Organizational | 5.03 Segregation of duties | Conflicting duties and areas of responsibility should be segregated. The purpose is to reduce the risk of fraud, error, and bypassing of information security controls. | Segregation of duties increases the official or formal guardians’ ability to supervise activities because the official or formal guardians are checking one another or involved in each other’s activities. |
56 | #10 Strengthen Formal Surveillance | Organizational | 5.07 Threat intelligence | Information relating to information security threats should be collected and analysed to produce threat intelligence. The purpose is to provide awareness of the organization’s threat environment so that the appropriate mitigation actions can be taken. | Collecting threat intelligence information for analysis to provide awareness of the organization’s threat environment can increase the ability of official or formal guardians' (such as cybersecurity professionals and Security Operation Centres) ability to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
57 | #10 Strengthen Formal Surveillance | Organizational | 5.24 Information security incident management planning and preparation | The organization should plan and prepare for managing information security incidents by defining, establishing, and communicating information security incident management processes, roles, and responsibilities. The purpose is to ensure quick, effective, consistent, and orderly response to information security incidents, including communication on information security events. | Quick and orderly response to information security incidents allows organizations to react in a timely manner to such incidents and can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
58 | #10 Strengthen Formal Surveillance | Organizational | 5.25 Assessment and decision on information security events | The organization should assess information security events and decide if they are to be categorized as information security incidents. The purpose is to ensure effective categorization and prioritization of information security events. | Assessing information security events for more effective categorization and prioritization increases the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as ransomware or DDOS attacks). |
59 | #10 Strengthen Formal Surveillance | Organizational | 5.28 Collection of evidence | The organization should establish and implement procedures for the identification, collection, acquisition, and preservation of evidence related to information security events. | Collecting evidence of information security events increases the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as ransomware or DDOS attacks). |
60 | #10 Strengthen Formal Surveillance | Physical | 7.04 Physical security monitoring | Premises should be continuously monitored for unauthorized physical access. | Physical security monitoring can assist official or formal guardians (such as cybersecurity professionals and Security Operation Centres) or increase their ability to be effective in situations with potential crime opportunities (such as thefts). |
61 | #10 Strengthen Formal Surveillance | Technological | 8.15 Logging | Logs that record activities, exceptions, faults, and other relevant events should be produced, stored, protected, and analysed. The purpose is to record events, generate evidence, ensure the integrity of log information, prevent against unauthorized access, identify information security events that can lead to an information security incident, and to support investigations. | Logging provides information on potential information security incidents. which can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
62 | #10 Strengthen Formal Surveillance | Technological | 8.16 Monitoring activities | Networks, systems, and applications should be monitored for anomalous behaviour and appropriate actions taken to evaluate potential information security incidents. The purpose is to detect anomalous behaviour and potential information security incidents. | Monitoring activities can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
63 | #10 Strengthen Formal Surveillance | Technological | 8.17 Clock synchronization | The clocks of information processing systems used by the organization should be synchronized to approved time sources. The purpose is to enable the correlation and analysis of security-related events and other recorded data, and to support investigations into information security incidents. | Clock synchronization of information processing systems can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
S3 Reduce the Rewards aims to limit the value of a target (or victim) for the offender or their ability to find their target or victim[31]. | |||||
SCP ‘#11 Conceal Targets’ aims to limit the offenders’ ability to see targets [31]. | |||||
64 | #11 Conceal Targets | Organizational | 5.12 Classification of information | Information should be classified according to the information security needs of the organization based on confidentiality, integrity, availability, and relevant interested party requirements. The purpose is to ensure identification and understanding of protection needs of information in accordance with its importance to the organization. | Classifying information according to their information security needs can limit the offenders’ ability to see targets (such as information) that are classified more strictly. |
65 | #11 Conceal Targets | People | 7.07 Clear desk and clear screen | Clear desk rules for papers and removable storage media and clear screen rules for information processing facilities should be defined and appropriately enforced. The purpose is to reduce the risks of unauthorized access, loss of, and damage to information on desks, screens, and in other accessible locations during and outside normal working hours. | Clearing desks and screens can limit offenders' ability to see crime targets (such as information on the desk or screen). |
66 | #11 Conceal Targets | Technological | 8.03 Information access restriction | Access to information and other associated assets should be restricted in accordance with the established topic-specific policy on access control. The purpose is to ensure only authorized access and to prevent unauthorized access to information and other associated assets. | Restricting access to information or associated assets can limit the offenders' ability to see these targets (such as information). |
67 | #11 Conceal Targets | Technological | 8.04 Access to source code | Read and write access to source code, development tools, and software libraries should be appropriately managed. The purpose is to prevent the introduction of unauthorized functionality, avoid unintentional or malicious changes, and to maintain the confidentiality of valuable intellectual property. | Restricting access to source codes can limit the offenders' ability to see these targets (such as source codes). |
68 | #11 Conceal Targets | Technological | 8.11 Data masking | Data masking should be used in accordance with the organization’s topic-specific policy on access control and other related topic-specific, and business requirements, taking applicable legislation into consideration. The purpose is to limit the exposure of sensitive data, including personally identifiable information, and to comply with legal, statutory, regulatory, and contractual requirements. | Masking data can limit the offenders’ ability to see these targets (such as data). |
69 | #11 Conceal Targets | Technological | 8.24 Use of cryptography | Rules for the effective use of cryptography, including cryptographic key management, should be defined and implemented. The purpose is to ensure proper and effective use of cryptography to protect the confidentiality, authenticity, or integrity of information according to business and information security requirements, and taking into consideration legal, statutory, regulatory, and contractual requirements related to cryptography. | Using cryptography can limit the offenders’ ability to see crime targets (such as information). |
SCP ‘#12 Remove Targets’ aims to take away potential targets or remove the valuable aspects of them [31]. | |||||
70 | #12 Remove Targets | Physical | 7.14 Secure disposal or re-use of equipment | 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. The purpose is to prevent leakage of information from equipment to be disposed or re-used. | Secure disposal of storage media can remove the valuable aspects of the targets (such as data in the storage media). |
71 | #12 Remove Targets | Technological | 8.10 Information deletion | Information stored in information systems, devices, or in any other storage media should be deleted when no longer required. The purpose is to prevent unnecessary exposure of sensitive information and to conform with legal, statutory, regulatory, and contractual requirements for information deletion. | Deleting information when no longer required can remove the valuable aspects of the targets (such as value of the data itself). |
SCP ‘#13 Identify Property’ aims to mark potential targets to make them traceable to the owner or to reduce the ability of offenders to claim ownerships [31]. | |||||
72 | #13 Identify Property | Organizational | 5.09 Inventory of information and other associated assets | An inventory of information and other associated assets, including owners, should be developed and maintained. The purpose is to identify the organization's information and other associated assets in order to preserve their information security and assign appropriate ownership. | Maintaining an inventory of information and related assets marks information and related assets to make them traceable to the owner and reduces the ability of the offender to claim ownership. |
73 | #13 Identify Property | Organizational | 5.13 Labelling of information | An appropriate set of procedures for information labelling should be developed and implemented in accordance with the information classification scheme adopted by the organization. The purpose is to facilitate the communication of classification of information and support automation of information processing and management. | Labelling information marks and identifies the information so that it can be more traceable to the owner and reduce the ability of the offender to claim ownership. |
SCP ‘#14 Disrupt Markets’ aims to make it difficult for offenders to transfer their criminal proceeds to others [31]. | |||||
74 | #14 Disrupt Markets | Organizational | 5.05 Contact with authorities | The organization should establish and maintain contact with relevant authorities. The purpose is to ensure appropriate flow of information takes place with respect to information security between the organization and relevant legal, regulatory, and supervisory authorities. | Contacting authorities makes it difficult for offenders (such as hackers) to transfer their proceeds (such as data) to others. |
75 | #14 Disrupt Markets | Organizational | 5.14 Information transfer | Information transfer rules, procedures, or agreements should be in place for all types of transfer facilities within the organization and between the organization and other parties. The purpose is to maintain the security of information transferred within an organization and with any external interested party. | Having information transfer rules can make it difficult for offenders to transfer the proceeds of their crimes (such as data) to others. |
76 | #14 Disrupt Markets | Organizational | 5.26 Response to information security incidents | Information security incidents should be responded to in accordance with the documented procedures. The purpose is to ensure efficient and effective response to information security incidents. | Responding to information security incidents in a timely manner can make it difficult for the offender to transfer the proceeds of crime (such as data) to others. |
SCP ‘#15 Deny Benefits’ aims to make it difficult for offenders to use their criminal targets for their intended purposes [31]. | |||||
77 | #15 Deny Benefits | Organizational | 5.30 ICT readiness for business continuity | ICT readiness should be planned, implemented, maintained, and tested based on business continuity objectives and ICT continuity requirements. The purpose is to ensure the availability of the organization’s information and other associated assets during disruption. | Ensuring that there is ICT readiness and availability in the organization can make it difficult for offenders to use the crime targets (such as data losses) for their intended purposes (such as DDoS and ransomware attacks). |
78 | #15 Deny Benefits | Technological | 8.06 Capacity management | The use of resources should be monitored and adjusted in line with current and expected capacity requirements. The purpose is to ensure the required capacity of information processing facilities, human resources, offices, and other facilities. | Managing resources capacity can make it difficult for offenders to use crime targets (such as information processing facilities) for the intended purpose such as denying the availability of the resources. |
79 | #15 Deny Benefits | Technological | 8.13 Information backup | Backup copies of information, software, and systems should be maintained and regularly tested in accordance with the agreed topic-specific policy on backup. | Backup of information, software, and systems can make it difficult for offenders to use crime targets (such as data losses) for the intended purpose (such as ransomware attacks). |
80 | #15 Deny Benefits | Technological | 8.14 Redundancy of information processing facilities | Information processing facilities should be implemented with redundancy sufficient to meet availability requirements. The purpose is to ensure the continuous operation of information processing facilities. | Redundancy of information processing facilities (such as data centres) can make it difficult for offenders to use crime targets (data centres) for the intended purpose (such as DDoS attacks). |
S5 Remove Excuses that offenders can give by presenting, explaining and reminding them about their responsibility[31]. | |||||
SCP ‘#21 Set Rules’ aims to provide information about unacceptable behaviours in a setting [31]. | |||||
81 | #21 Set Rules | Organizational | 5.01 Policies for information security | 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. The purpose is to ensure continuing suitability, adequacy, effectiveness of management direction, and support for information security in accordance with business requirements, legal, statutory, regulatory, and contractual requirements. | Having policies for information security sets rules on what is unacceptable information security practices in the organization. |
82 | #21 Set Rules | Organizational | 5.10 Acceptable use of information and other associated assets | Rules for the acceptable use and procedures for handling information and other associated assets should be identified, documented, and implemented. The purpose is to ensure information and other associated assets are appropriately protected, used, and handled. | Setting rules for acceptable use and procedures for handling information provide information about unacceptable behaviours on use of information in the organization. |
83 | #21 Set Rules | People | 6.02 Terms and conditions of employment | The employment contractual agreements should state the personnel's and the organization's responsibilities for information security. The purpose is to ensure personnel understand their information security responsibilities for the roles for which they are considered. | Having terms and conditions of employment provide information about employee responsibilities and their behaviours during the employment period in the organization. |
84 | #21 Set Rules | People | 6.04 Disciplinary process | 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. The purpose is to ensure personnel and other relevant interested parties understand the consequences of information security policy violation, to deter and appropriately deal with personnel who committed the violation. | A formalized disciplinary process that is communicated to employees provides information about unacceptable behaviours on committing an information security policy violation in the organization. |
85 | #21 Set Rules | People | 6.05 Responsibilities after termination or change of employment | 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. The purpose is to protect the organiation's interests as part of the process of changing or terminating employment or contracts. | Communicating information security responsibilities and duties that remain valid even after termination provides information about unacceptable behaviours on shirking information security responsibilities in the organization. |
86 | #21 Set Rules | People | 6.06 Confidentiality or non-disclosure agreements | 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. The purpose is to maintain confidentiality of information accessible by personnel or external parties. | Having confidentiality or non-disclosure agreements signed by employees can provide information about unacceptable behaviours on leaking confidential information in the organization. |
SCP ‘#22 Post Instructions’ aims to provide detailed information about how to meet the behavioural requirements in a setting [31]. | |||||
87 | #22 Post Instructions | Organizational | 5.37 Documented operating procedures | Operating procedures for information processing facilities should be documented and made available to personnel who need them. The purpose is to ensure the correct and secure operation of information processing facilities. | Documenting operating procedures for information processing facilities provides detailed information on the expectations of the employees in ensuring the correct and secure operation of the information processing facilities. |
88 | #22 Post Instructions | People | 6.03 Information security awareness, education, and training | Personnel of the organization and relevant interested parties should receive appropriate information security awareness, education and training, and regular updates of the organization’s information security policy, topic-specific policies and procedures, as relevant for their job function. The purpose is to ensure personnel and relevant interested parties are aware of and fulfil their information security responsibilities. | Information security awareness education and training provide detailed instructions about how to meet the behavioural requirements on information security in the organization. |
SCP ‘#24 Assist Compliance’ aims to make it easier to carry out acceptable behaviours in a setting [31]. | |||||
89 | #24 Assist Compliance | Organizational | 5.04 Management responsibilities | Management should require all personnel to apply information security in accordance with the established information security policy, topic-specific policies and procedures of the organization. The purpose is to ensure management understand their role in information security and undertake actions aiming to ensure all personnel are aware of and fulfil their information security responsibilities. | Having management to require personnel to apply information security in accordance with established information security policies and procedures in the organization makes it easier for all personnel in the organization to know and carry out acceptable information security behaviours. |
90 | #24 Assist Compliance | Organizational | 5.31 Legal, statutory, regulatory, and contractual requirements | Legal, statutory, regulatory, and contractual requirements relevant to information security and the organization’s approach to meet these requirements should be identified, documented, and kept up-to-date. | Complying with legal, statutory, regulatory, and contractual requirements can make it easier for employees to meet their information security obligations in the organization. |
91 | #24 Assist Compliance | Organizational | 5.32 Intellectual property rights | The organization should implement appropriate procedures to protect intellectual property rights. The purpose is to ensure compliance with legal, statutory, regulatory, and contractual requirements related to intellectual property rights and use of proprietary products. | Having procedures to protect intellectual property rights can assist in the compliance with legal, statutory, regulatory, and contractual requirements, which in turn can make it easier for the employees to meet their legal obligations in the organization. |
92 | #24 Assist Compliance | Organizational | 5.34 Privacy and protection of PII | The organization should identify and meet the requirements regarding the preservation of privacy and protection of PII according to applicable laws and regulations and contractual requirements. The purpose is to ensure compliance with legal, statutory, regulatory, and contractual requirements related to the information security aspects of the protection of PII. | Meeting PII requirements in compliance with legal, statutory, regulatory, and contractual requirements can make it easier for employees to meet their legal obligations in the organization. |
93 | #24 Assist Compliance | Organizational | 5.36 Conformance with policies, rules, and standards for information security | Compliance with the organization’s information security policy, topic-specific policies, rules, and standards should be regularly reviewed. The purpose is to ensure that information security is implemented and operated in accordance with the organization’s information security policy, topic-specific policies, rules, and standards. | Regularly reviewing the organization’s information security policies and related matters can ensure that the policies are up-to-date, and this can make it easier for employees to carry out their information security obligations in an up-to-date manner. |
No. . | SCP technique . | Clause type . | ISO/IEC control . | ISO/IEC control description and purpose . | Rationale . |
---|---|---|---|---|---|
S1 INCREASE THE EFFORTS aims to block or limit the actions or movements of offenders[31]. | |||||
SCP ‘#01 Harden Targets’ makes it more difficult for offenders to get to or use the target to achieve their criminal purposes [31]. | |||||
1 | #01 Harden Targets | Organizational | 5.08 Information security in project management | Information security should be integrated into project management. The purpose is to ensure information security risks related to projects and deliverables are effectively addressed in project management throughout the project life cycle. | Integrating information security into project management can make the project more secure and therefore more difficult for the offender to get to or use the target to achieve criminal purposes (such as ransomware or DDoS attacks). |
2 | #01 Harden Targets | Organizational | 5.19 Information security in supplier relationships | Processes and procedures should be defined and implemented to manage the information security risks associated with the use of supplier's products or services. The purpose is to maintain an agreed level of information security in supplier relationships. | Managing information security risks about the use of supplier products and services can make it more difficult for the offender to get to or use the target (such as the supplier products and services) to achieve criminal purposes (such as ransomware or DDoS attacks). |
3 | #01 Harden Targets | Organizational | 5.20 Addressing information security within supplier agreements | Relevant information security requirements should be established and agreed with each supplier based on the type of supplier relationship. The purpose is to maintain an agreed level of information security in supplier relationships. | Establishing information security requirements for suppliers can make it more difficult for the offender to get to or use the target (such as the supplier products and services) to achieve criminal purposes (such as ransomware or DDoS attacks). |
4 | #01 Harden Targets | Organizational | 5.21 Managing information security in the ICT supply chain | Processes and procedures should be defined and implemented to manage information security risks associated with the ICT products and services supply chain. The purpose is to maintain an agreed level of information security in supplier relationships. | Managing information security risks about the ICT products and services supply chain can make it more difficult for the offender to get to or use the target (such as ICT supply chain) to achieve criminal purposes (such as ransomware or DDoS attacks). |
5 | #01 Harden Targets | Organizational | 5.23 Information security for use of cloud services | Processes for acquisition, use, management, and exit from cloud services should be established in accordance with the organization's information security requirements. The purpose is to specify and manage information security for the use of cloud services. | Specifying and managing information security for the use of cloud services can make it more difficult for the offender to get to or use the target (such as information systems and data stored in cloud) to achieve criminal purposes. |
6 | #01 Harden Targets | Organizational | 5.27 Learning from information security incidents | Knowledge gained from information security incidents should be used to strengthen and improve the information security controls. The purpose is to reduce the likelihood or consequences of future incidents. | Learning from information security events can reduce the likelihood or consequences of future incidents. This in turn makes it more difficult for the offender to get to or use the target to achieve the criminal purpose (such as ransomware or DDoS attacks). |
7 | #01 Harden Targets | Organizational | 5.29 Information security during disruption | The organization should plan how to maintain information security at an appropriate level during disruption. The purpose is to protect information and other associated assets during disruption. | The ability to maintain information security despite disruption can make it more difficult for the offender to get to or use the target (such as information systems that are affected by disruption) to achieve criminal purposes (such as ransomware or DDoS attacks). |
8 | #01 Harden Targets | Organizational | 5.33 Protection of records | Records should be protected from loss, destruction, falsification, unauthorized access, and unauthorized release. The purpose is to ensure compliance with legal, statutory, regulatory, and contractual requirements, as well as community or societal expectations related to the protection and availability of records. | Ensuring that the records are protected can make it more difficult for offenders to use the crime targets (such as data losses) for their intended purposes (such as DDoS and ransomware attacks). |
9 | #01 Harden Targets | Organizational | 5.35 Independent review of information security | The organization’s approach to managing information security and its implementation, including people, processes, and technologies, should be reviewed independently at planned intervals, or when significant changes occur. The purpose is to ensure the continuing suitability, adequacy, and effectiveness of the organization’s approach to managing information security. | Having an independent review of information security can identify potential weaknesses that can be fixed before they are actually exploited by offenders. This in turn makes it more difficult for the offender to get to or use the target to achieve the criminal purpose (such as ransomware or DDoS attacks). |
10 | #01 Harden Targets | People | 6.07 Remote working | Security measures should be implemented when personnel are working remotely to protect information accessed, processed, or stored outside the organization’s premises. The purpose is to ensure the security of information when personnel are working remotely. | Implementing security measures when personnel are working remotely will make it more difficult for offender to get to or use the target (such as employees working remotely) to achieve the criminal purposes (such as ransomware or DDoS attacks). |
11 | #01 Harden Targets | Physical | 7.03 Securing offices, rooms, and facilities | Physical security for offices, rooms and facilities should be designed and implemented. The purpose is to prevent unauthorized physical access, damage and interference to the organization’s information and other associated assets in offices, rooms and facilities. | Securing offices, rooms, and facilities can make it more difficult for the offender to get to or use the target (such as offices) to achieve criminal purposes (such as ransomware or DDoS attacks). |
12 | #01 Harden Targets | Physical | 7.05 Protecting against physical and environmental threats | Protection against physical and environmental threats, such as natural disasters and other intentional or unintentional physical threats to infrastructure should be designed and implemented. The purpose is to prevent or reduce the consequences of events originating from physical and environmental threats. | Protection against physical and environmental threats can make it more difficult for offenders to make use of these threats to get to or use the target (such as computing infrastructure) to achieve criminal purposes (such as ransomware or DDoS attacks). |
13 | #01 Harden Targets | Physical | 7.06 Working in secure areas | Security measures for working in secure areas should be designed and implemented. The purpose is to protect information and other associated assets in secure areas from damage and unauthorized interference by personnel working in these areas. | Security measures for working in secure areas can make it more difficult for the offender to get to or use the target (such as sensitive office areas) to achieve the criminal purposes (such as ransomware or DDoS attacks). |
14 | #01 Harden Targets | Physical | 7.08 Equipment siting and protection | Equipment should be sited securely and protected. The purpose is to reduce the risks from physical and environmental threats, and from unauthorized access and damage. | Equipment that is sited securely and protected can make it more difficult for the offender to get to or use the target to achieve criminal purposes. |
15 | #01 Harden Targets | Physical | 7.09 Security of assets off-premises | Off-site assets should be protected. The purpose is to prevent loss, damage, theft, or compromise of off-site assets and interruption to the organization’s operations. | Protecting off-site assets can make it more difficult for the offender to get to or use the target (such as assets) to achieve criminal purposes (such as ransomware or DDoS attacks). |
16 | #01 Harden Targets | Physical | 7.10 Storage media | Storage media should be managed through its life cycle of acquisition, use, transportation, and disposal in accordance with the organization’s classification scheme and handling requirements. The purpose is to ensure only authorized disclosure, modification, removal, or destruction of information on storage media. | Managing storage media can make it more difficult for the offender to get to or use the target (such as storage media) to achieve criminal purposes (such as ransomware or DDoS attacks). |
17 | #01 Harden Targets | Physical | 7.11 Supporting utilities | Information processing facilities should be protected from power failures and other disruptions caused by failures in supporting utilities. The purpose is to prevent loss, damage, or compromise of information and other associated assets, or interruption to the organization’s operations due to the failure and disruption of supporting utilities. | Information processing facilities should be protected from power failures and other disruptions caused by failures in supporting utilities. |
18 | #01 Harden Targets | Physical | 7.12 Cabling security | Cables carrying power, data, or supporting information services should be protected from interception, interference, or damage. The purpose is to prevent loss, damage, theft, or compromise of information and other associated assets and interruption to the organization’s operations related to power and communications cabling. | Protecting cables can make it more difficult for the offender to get to or use the target (such as cables) to achieve criminal purposes (such as ransomware or DDoS attacks). |
19 | #01 Harden Targets | Physical | 7.13 Equipment maintenance | Equipment should be maintained correctly to ensure availability, integrity, and confidentiality of information. The purpose is to prevent loss, damage, theft, or compromise of information and other associated assets and interruption to the organization’s operations caused by lack of maintenance. | Maintaining equipment can make it more difficult for the offender to get to or use the target (such as equipment) to achieve criminal purposes (such as ransomware or DDoS attacks). |
20 | #01 Harden Targets | Technological | 8.01 User endpoint devices | Information stored on, processed by, or accessible via user endpoint devices should be protected. The purpose is to protect information against the risks introduced by using user endpoint devices. | Protecting user endpoint devices can make it more difficult for the offender to get to or use the target (such as user endpoint devices) to achieve criminal purposes (such as ransomware or DDoS attacks). |
21 | #01 Harden Targets | Technological | 8.07 Protection against malware | Protection against malware should be implemented and supported by appropriate user awareness. The purpose is to ensure information and other associated assets are protected against malware. | Protection against malware can make it more difficult for the offender to get to or use the target (such as computing devices) to achieve criminal purposes (such as ransomware or DDoS attacks). |
22 | #01 Harden Targets | Technological | 8.08 Management of technical vulnerabilities | 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. The purpose is to prevent exploitation of technical vulnerabilities. | Managing technical vulnerabilities in information systems can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
23 | #01 Harden Targets | Technological | 8.09 Configuration management | Configurations, including security configurations, of hardware, software, services, and networks should be established, documented, implemented, monitored, and reviewed. The purpose is to ensure hardware, software, services, and networks function correctly with required security settings, and configuration is not altered by unauthorized or incorrect changes. | Managing configurations can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
24 | #01 Harden Targets | Technological | 8.23 Web filtering | Access to external websites should be managed to reduce exposure to malicious content. The purpose is to protect systems from being compromised by malware and to prevent access to unauthorized web resources. | Managing access to external websites can make it more difficult for the offender to get to or use the target (such as external websites) to achieve criminal purposes (such as downloading malware for subsequent cyberattacks). |
25 | #01 Harden Targets | Technological | 8.25 Secure development life cycle | Rules for the secure development of software and systems should be established and applied. The purpose is to ensure information security is designed and implemented within the secure development life cycle of software and systems. | Secure development of software can make it more difficult for the offender to get to or use the target (such as software) to achieve criminal purposes (such as ransomware or DDoS attacks). |
26 | #01 Harden Targets | Technological | 8.26 Application security requirements | Information security requirements should be identified, specified, and approved when developing or acquiring applications. The purpose is to ensure all information security requirements are identified and addressed when developing or acquiring applications. | Identifying and addressing application security requirements can make it more difficult for the offender to get to or use the target (such as application) to achieve criminal purposes (such as ransomware or DDoS attacks). |
27 | #01 Harden Targets | Technological | 8.27 Secure system architecture and engineering principles | Principles for engineering secure systems should be established, documented, maintained, and applied to any information system development activities. The purpose is to ensure information systems are securely designed, implemented, and operated within the development life cycle. | Applying secure system architecture and engineering principles can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
28 | #01 Harden Targets | Technological | 8.28 Secure coding | Secure coding principles should be applied to software development. The purpose is to ensure software is written securely, thereby reducing the number of potential information security vulnerabilities in the software. | Applying secure coding principles can make it more difficult for the offender to get to or use the target (such as software) to achieve criminal purposes (such as ransomware or DDoS attacks). |
29 | #01 Harden Targets | Technological | 8.29 Security testing in development and acceptance | Security testing processes should be defined and implemented in the development life cycle. The purpose is to validate if information security requirements are met when applications or code are deployed to the production environment. | Security testing can make it more difficult for the offender to get to or use the target (such as applications and websites) to achieve criminal purposes (such as ransomware or DDoS attacks). |
30 | #01 Harden Targets | Technological | 8.30 Outsourced development | The organization should direct, monitor, and review the activities related to outsourced system development. The purpose is to ensure information security measures required by the organization are implemented in outsourced system development. | Ensuring that information security measures required by the organization are implemented in outsourced system development can make it more difficult for the offender to get to or use the target to achieve criminal purposes. |
31 | #01 Harden Targets | Technological | 8.32 Change management | Changes to information processing facilities and information systems should be subject to change management procedures. The purpose is to preserve information security when executing changes. | Managing change management can make it more difficult for the offender to get to or use the target (such as applications and websites) to achieve criminal purposes (such as ransomware or DDoS attacks). |
32 | #01 Harden Targets | Technological | 8.33 Test information | Test information should be appropriately selected, protected, and managed. The purpose is to ensure relevance of testing and protection of operational information used for testing. | Protecting test information can make it more difficult for the offender to get to or use the target (such as test information) to achieve criminal purposes (such as cyber reconnaissance). |
33 | #01 Harden Targets | Technological | 8.34 Protection of information systems during audit testing | Audit tests and other assurance activities involving assessment of operational systems should be planned and agreed between the tester and appropriate management. The purpose is to minimize the impact of audit and other assurance activities on operational systems and business processes. | Protecting information systems during audit testing can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
SCP ‘#02 Control Access to Facilities’ aims to block offenders access to places where they may carry out a criminal action [31]. | |||||
34 | #05 Control Tools/Weapons | Organizational | 5.15 Access control | Returning the organization’s assets upon the end of the employment, contract, or agreement can prevent and block the ex-employee from using the organization’s assets (such as notebooks, access cards, and keys) to access the organization’s places and assets. | Returning the organization’s assets upon the end of the employment, contract, or agreement can limit offender access to these instruments (such as notebooks, access cards, and keys) associated with particular modus operandi (such as hacking, DDoS, and ransomware attacks). |
35 | #02 Control Access to Facilities | Organizational | 5.15 Access 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. The purpose is to ensure authorized access and to prevent unauthorized access to information and other associated assets. | Controlling physical and logical access to information and related assets can block access to places (such as applications and websites) where a criminal action (such as data breach) may be carried out. |
36 | #02 Control Access to Facilities | Organizational | 5.18 Access rights | Access rights to information and other associated assets should be provisioned, reviewed, modified, and removed in accordance with the organization’s topic-specific policy on and rules for access control. The purpose is to ensure access to information and other associated assets is defined and authorized according to the business requirements. | Controlling the access rights to information and associated assets can block access to places (such as applications and websites) where a criminal action (such as data breach) may be carried out. |
37 | #02 Control Access to Facilities | Physical | 7.01 Physical security perimeters | Security perimeters should be defined and used to protect areas that contain information and other associated assets. | Physical security perimeters can block access to places (such as data centres) where a criminal action (such as hacking) may be carried out. |
38 | #02 Control Access to Facilities | Physical | 7.02 Physical entry | Secure areas should be protected by appropriate entry controls and access points. The purpose is to ensure only authorized physical access to the organization’s information and other associated assets occurs. | Physical entries can block access to places (such as data centres) where a criminal action (such as hacking) may be carried out. |
39 | #02 Control Access to Facilities | Technological | 8.02 Privileged access rights | The allocation and use of privileged access rights should be restricted and managed. The purpose is to ensure only authorized users, software components, and services are provided with privileged access rights. | Controlling privileged access rights can block access to places (such as applications and websites) where criminal action (such as ransomware and hacking) may be carried out. |
40 | #02 Control Access to Facilities | Technological | 8.20 Networks security | Networks and network devices should be secured, managed, and controlled to protect information in systems and applications. The purpose is to protect information in networks and its supporting information processing facilities from compromise via the network. | Protecting networks, which are gateways to places (such as computing devices and websites) can block access to places where criminal actions (such as hacking and data breaches) may be carried out. |
41 | #02 Control Access to Facilities | Technological | 8.21 Security of network services | Security mechanisms, service levels, and service requirements of network services should be identified, implemented, and monitored. The purpose is to ensure security in the use of network services. | Protecting network services, which are gateways to places (such as computing devices and websites) can block access to places where criminal actions (such as hacking and data breaches) may be carried out. |
SCP ‘#03 Screen Exits’ aims to make it more difficult for the offender to leave a place after their criminal action [31]. | |||||
42 | #03 Screen Exits | Technological | 8.12 Data leakage prevention | Data leakage prevention measures should be applied to systems, networks, and any other devices that process, store, or transmit sensitive information. The purpose is to detect and prevent the unauthorized disclosure and extraction of information by individuals or systems. | Data leakage prevention measures can make it more difficult for the offender to leave a place (such as network perimeter) after a criminal action (such as data leakage). |
SCP ‘#04 Deflect offenders’ aims to change the offender’s existing or potential movement patterns [31]. | |||||
43 | #04 Deflect offenders | Technological | 8.22 Segregation of networks | Groups of information services, users, and information systems should be segregated in the organization’s networks. The purpose is to split the network in security boundaries and to control traffic between them based on business needs. | Segregating networks can change existing or potential offender movement patterns (such as hacking patterns). |
44 | #04 Deflect offenders | Technological | 8.31 Separation of development, test and production environments | Development, testing, and production environments should be separated and secured. The purpose is to protect the production environment and data from compromise by development and test activities. | Separating the development, test, and production environments can change existing or potential offender movement patterns (such as hacking patterns). |
SCP ‘#05 Control Tools/Weapons’ aims to limit offender access to or use instruments associated with a criminal modus operandi [31]. | |||||
45 | #05 Control Tools/Weapons | Technological | 8.18 Use of privileged utility programs | The use of utility programs that can be capable of overriding system and application controls should be restricted and tightly controlled. The purpose is to ensure the use of utility programs does not harm system and application controls for information security. | Restricting and controlling privileged utility programs that can be misused can limit offender access to these instruments (such as privileged utility programs) associated with particular modus operandi (such as hacking, DDoS, and ransomware attacks). |
46 | #05 Control Tools/Weapons | Technological | 8.19 Installation of software on operational systems | Procedures and measures should be implemented to securely manage software installation on operational systems. The purpose is to ensure the integrity of operational systems and prevent exploitation of technical vulnerabilities. | Managing installation of software that can be misused (such as rootkits and trojans) can limit offender access to these instruments (such as software on operational systems) associated with particular modus operandi (such as hacking, DDoS, and ransomware attacks). |
S2 Increase the Risks aims to provide more or better guardianship to increase the likelihood of detecting offenders[31]. | |||||
SCP ‘#06 Extend Guardianships’ aims to provide incentives to encourage unofficial guardians to act or be more effective [31]. | |||||
47 | #06 Extend Guardianships | People | 6.08 Information security event reporting | The organization should provide a mechanism for personnel to report observed or suspected information security events through appropriate channels in a timely manner. The purpose is to support timely, consistent, and effective reporting of information security events that can be identified by personnel. | A mechanism for personnel to report information security events will provide incentives to encourage unofficial guardians (such as employees, contractors, and users) to act or be more effective because there is a channel for them to report. |
SCP ‘#07 Assist natural surveillance’ aims to increase the likelihood that potential guardians will see criminal actions happening in places [31]. | |||||
48 | #07 Assist natural surveillance | Organizational | 5.22 Monitoring, review and change management of supplier services | The organization should regularly monitor, review, evaluate, and manage change in supplier information security practices and service delivery. The purpose is to maintain an agreed level of information security and service delivery in line with supplier agreements. | Regularly reviewing supplier information security practices and service delivery can increase the likelihood that guardians (such as owners of supplier services) will see any criminal actions occurring in places belonging to the supplier. |
SCP ‘#08 Reduce Anonymity’ aims to increase the likelihood that potential guardians will identify the features of offenders [31]. | |||||
49 | #08 Reduce Anonymity | Organizational | 5.06 Contact with special interest groups | The organization should establish and maintain contact with special interest groups or other specialist security forums and professional associations. The purpose is to ensure appropriate flow of information takes place with respect to information security. | Contacting special interest groups or other specialist security forums and professional associations to exchange cybersecurity information increases the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of potential offenders (such as hackers). |
50 | #08 Reduce Anonymity | Organizational | 5.16 Identity management | The full life cycle of identities should be managed. The purpose is to allow for the unique identification of individuals and systems accessing the organization’s information and other associated assets and to enable appropriate assignment of access rights. | Identity management increases the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of potential offenders (such as hackers). |
51 | #08 Reduce Anonymity | Organizational | 5.17 Authentication information | Allocation and management of authentication information should be controlled by a management process, including advising personnel of appropriate handling of authentication information. The purpose is to ensure proper entity authentication and prevent failures of authentication processes. | Properly managing authentication information increases the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of potential offenders (such as hackers). |
52 | #08 Reduce Anonymity | People | 6.01 Screening | Background verification checks on all candidates to become personnel should be carried out prior to joining the organization and on an ongoing basis taking into consideration applicable laws, regulations, and ethics, and be proportional to the business requirements, the classification of the information to be accessed, and the perceived risks. The purpose is to ensure all personnel are eligible and suitable for the roles for which they are considered and remain eligible and suitable during their employment. | Background screening can increase the likelihood that potential guardians (such as human resource department) can identify the features of the offenders (such as insiders). |
53 | #08 Reduce Anonymity | Technological | 8.05 Secure authentication | Secure authentication technologies and procedures should be implemented based on information access restrictions and the topic-specific policy on access control. The purpose is to ensure a user, or an entity is securely authenticated, when access to systems, applications, and services is granted. | Secure authentication can increase the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of offenders (such as hackers). |
SCP ‘#09 Utilise Place Managers’ aims to use existing or new employees or managers as potential guardians or to change the settings to limit criminal opportunities [31]. | |||||
54 | #09 Utilise Place Managers | Organizational | 5.02 Information security roles and responsibilities | Information security roles and responsibilities should be defined and allocated according to the organization needs. The purpose is to establish a defined, approved, and understood structure for the implementation, operation, and management of information security within the organization. | Existing or new employees are used as potential guardians (such as cybersecurity professionals and Security Operation Centres) in information security roles. |
SCP ‘#10 Strengthen Formal Surveillance’ aims to provide official or formal guardians or increase their ability to be more effective in dealing with criminal opportunities [31]. | |||||
55 | #10 Strengthen Formal Surveillance | Organizational | 5.03 Segregation of duties | Conflicting duties and areas of responsibility should be segregated. The purpose is to reduce the risk of fraud, error, and bypassing of information security controls. | Segregation of duties increases the official or formal guardians’ ability to supervise activities because the official or formal guardians are checking one another or involved in each other’s activities. |
56 | #10 Strengthen Formal Surveillance | Organizational | 5.07 Threat intelligence | Information relating to information security threats should be collected and analysed to produce threat intelligence. The purpose is to provide awareness of the organization’s threat environment so that the appropriate mitigation actions can be taken. | Collecting threat intelligence information for analysis to provide awareness of the organization’s threat environment can increase the ability of official or formal guardians' (such as cybersecurity professionals and Security Operation Centres) ability to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
57 | #10 Strengthen Formal Surveillance | Organizational | 5.24 Information security incident management planning and preparation | The organization should plan and prepare for managing information security incidents by defining, establishing, and communicating information security incident management processes, roles, and responsibilities. The purpose is to ensure quick, effective, consistent, and orderly response to information security incidents, including communication on information security events. | Quick and orderly response to information security incidents allows organizations to react in a timely manner to such incidents and can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
58 | #10 Strengthen Formal Surveillance | Organizational | 5.25 Assessment and decision on information security events | The organization should assess information security events and decide if they are to be categorized as information security incidents. The purpose is to ensure effective categorization and prioritization of information security events. | Assessing information security events for more effective categorization and prioritization increases the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as ransomware or DDOS attacks). |
59 | #10 Strengthen Formal Surveillance | Organizational | 5.28 Collection of evidence | The organization should establish and implement procedures for the identification, collection, acquisition, and preservation of evidence related to information security events. | Collecting evidence of information security events increases the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as ransomware or DDOS attacks). |
60 | #10 Strengthen Formal Surveillance | Physical | 7.04 Physical security monitoring | Premises should be continuously monitored for unauthorized physical access. | Physical security monitoring can assist official or formal guardians (such as cybersecurity professionals and Security Operation Centres) or increase their ability to be effective in situations with potential crime opportunities (such as thefts). |
61 | #10 Strengthen Formal Surveillance | Technological | 8.15 Logging | Logs that record activities, exceptions, faults, and other relevant events should be produced, stored, protected, and analysed. The purpose is to record events, generate evidence, ensure the integrity of log information, prevent against unauthorized access, identify information security events that can lead to an information security incident, and to support investigations. | Logging provides information on potential information security incidents. which can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
62 | #10 Strengthen Formal Surveillance | Technological | 8.16 Monitoring activities | Networks, systems, and applications should be monitored for anomalous behaviour and appropriate actions taken to evaluate potential information security incidents. The purpose is to detect anomalous behaviour and potential information security incidents. | Monitoring activities can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
63 | #10 Strengthen Formal Surveillance | Technological | 8.17 Clock synchronization | The clocks of information processing systems used by the organization should be synchronized to approved time sources. The purpose is to enable the correlation and analysis of security-related events and other recorded data, and to support investigations into information security incidents. | Clock synchronization of information processing systems can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
S3 Reduce the Rewards aims to limit the value of a target (or victim) for the offender or their ability to find their target or victim[31]. | |||||
SCP ‘#11 Conceal Targets’ aims to limit the offenders’ ability to see targets [31]. | |||||
64 | #11 Conceal Targets | Organizational | 5.12 Classification of information | Information should be classified according to the information security needs of the organization based on confidentiality, integrity, availability, and relevant interested party requirements. The purpose is to ensure identification and understanding of protection needs of information in accordance with its importance to the organization. | Classifying information according to their information security needs can limit the offenders’ ability to see targets (such as information) that are classified more strictly. |
65 | #11 Conceal Targets | People | 7.07 Clear desk and clear screen | Clear desk rules for papers and removable storage media and clear screen rules for information processing facilities should be defined and appropriately enforced. The purpose is to reduce the risks of unauthorized access, loss of, and damage to information on desks, screens, and in other accessible locations during and outside normal working hours. | Clearing desks and screens can limit offenders' ability to see crime targets (such as information on the desk or screen). |
66 | #11 Conceal Targets | Technological | 8.03 Information access restriction | Access to information and other associated assets should be restricted in accordance with the established topic-specific policy on access control. The purpose is to ensure only authorized access and to prevent unauthorized access to information and other associated assets. | Restricting access to information or associated assets can limit the offenders' ability to see these targets (such as information). |
67 | #11 Conceal Targets | Technological | 8.04 Access to source code | Read and write access to source code, development tools, and software libraries should be appropriately managed. The purpose is to prevent the introduction of unauthorized functionality, avoid unintentional or malicious changes, and to maintain the confidentiality of valuable intellectual property. | Restricting access to source codes can limit the offenders' ability to see these targets (such as source codes). |
68 | #11 Conceal Targets | Technological | 8.11 Data masking | Data masking should be used in accordance with the organization’s topic-specific policy on access control and other related topic-specific, and business requirements, taking applicable legislation into consideration. The purpose is to limit the exposure of sensitive data, including personally identifiable information, and to comply with legal, statutory, regulatory, and contractual requirements. | Masking data can limit the offenders’ ability to see these targets (such as data). |
69 | #11 Conceal Targets | Technological | 8.24 Use of cryptography | Rules for the effective use of cryptography, including cryptographic key management, should be defined and implemented. The purpose is to ensure proper and effective use of cryptography to protect the confidentiality, authenticity, or integrity of information according to business and information security requirements, and taking into consideration legal, statutory, regulatory, and contractual requirements related to cryptography. | Using cryptography can limit the offenders’ ability to see crime targets (such as information). |
SCP ‘#12 Remove Targets’ aims to take away potential targets or remove the valuable aspects of them [31]. | |||||
70 | #12 Remove Targets | Physical | 7.14 Secure disposal or re-use of equipment | 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. The purpose is to prevent leakage of information from equipment to be disposed or re-used. | Secure disposal of storage media can remove the valuable aspects of the targets (such as data in the storage media). |
71 | #12 Remove Targets | Technological | 8.10 Information deletion | Information stored in information systems, devices, or in any other storage media should be deleted when no longer required. The purpose is to prevent unnecessary exposure of sensitive information and to conform with legal, statutory, regulatory, and contractual requirements for information deletion. | Deleting information when no longer required can remove the valuable aspects of the targets (such as value of the data itself). |
SCP ‘#13 Identify Property’ aims to mark potential targets to make them traceable to the owner or to reduce the ability of offenders to claim ownerships [31]. | |||||
72 | #13 Identify Property | Organizational | 5.09 Inventory of information and other associated assets | An inventory of information and other associated assets, including owners, should be developed and maintained. The purpose is to identify the organization's information and other associated assets in order to preserve their information security and assign appropriate ownership. | Maintaining an inventory of information and related assets marks information and related assets to make them traceable to the owner and reduces the ability of the offender to claim ownership. |
73 | #13 Identify Property | Organizational | 5.13 Labelling of information | An appropriate set of procedures for information labelling should be developed and implemented in accordance with the information classification scheme adopted by the organization. The purpose is to facilitate the communication of classification of information and support automation of information processing and management. | Labelling information marks and identifies the information so that it can be more traceable to the owner and reduce the ability of the offender to claim ownership. |
SCP ‘#14 Disrupt Markets’ aims to make it difficult for offenders to transfer their criminal proceeds to others [31]. | |||||
74 | #14 Disrupt Markets | Organizational | 5.05 Contact with authorities | The organization should establish and maintain contact with relevant authorities. The purpose is to ensure appropriate flow of information takes place with respect to information security between the organization and relevant legal, regulatory, and supervisory authorities. | Contacting authorities makes it difficult for offenders (such as hackers) to transfer their proceeds (such as data) to others. |
75 | #14 Disrupt Markets | Organizational | 5.14 Information transfer | Information transfer rules, procedures, or agreements should be in place for all types of transfer facilities within the organization and between the organization and other parties. The purpose is to maintain the security of information transferred within an organization and with any external interested party. | Having information transfer rules can make it difficult for offenders to transfer the proceeds of their crimes (such as data) to others. |
76 | #14 Disrupt Markets | Organizational | 5.26 Response to information security incidents | Information security incidents should be responded to in accordance with the documented procedures. The purpose is to ensure efficient and effective response to information security incidents. | Responding to information security incidents in a timely manner can make it difficult for the offender to transfer the proceeds of crime (such as data) to others. |
SCP ‘#15 Deny Benefits’ aims to make it difficult for offenders to use their criminal targets for their intended purposes [31]. | |||||
77 | #15 Deny Benefits | Organizational | 5.30 ICT readiness for business continuity | ICT readiness should be planned, implemented, maintained, and tested based on business continuity objectives and ICT continuity requirements. The purpose is to ensure the availability of the organization’s information and other associated assets during disruption. | Ensuring that there is ICT readiness and availability in the organization can make it difficult for offenders to use the crime targets (such as data losses) for their intended purposes (such as DDoS and ransomware attacks). |
78 | #15 Deny Benefits | Technological | 8.06 Capacity management | The use of resources should be monitored and adjusted in line with current and expected capacity requirements. The purpose is to ensure the required capacity of information processing facilities, human resources, offices, and other facilities. | Managing resources capacity can make it difficult for offenders to use crime targets (such as information processing facilities) for the intended purpose such as denying the availability of the resources. |
79 | #15 Deny Benefits | Technological | 8.13 Information backup | Backup copies of information, software, and systems should be maintained and regularly tested in accordance with the agreed topic-specific policy on backup. | Backup of information, software, and systems can make it difficult for offenders to use crime targets (such as data losses) for the intended purpose (such as ransomware attacks). |
80 | #15 Deny Benefits | Technological | 8.14 Redundancy of information processing facilities | Information processing facilities should be implemented with redundancy sufficient to meet availability requirements. The purpose is to ensure the continuous operation of information processing facilities. | Redundancy of information processing facilities (such as data centres) can make it difficult for offenders to use crime targets (data centres) for the intended purpose (such as DDoS attacks). |
S5 Remove Excuses that offenders can give by presenting, explaining and reminding them about their responsibility[31]. | |||||
SCP ‘#21 Set Rules’ aims to provide information about unacceptable behaviours in a setting [31]. | |||||
81 | #21 Set Rules | Organizational | 5.01 Policies for information security | 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. The purpose is to ensure continuing suitability, adequacy, effectiveness of management direction, and support for information security in accordance with business requirements, legal, statutory, regulatory, and contractual requirements. | Having policies for information security sets rules on what is unacceptable information security practices in the organization. |
82 | #21 Set Rules | Organizational | 5.10 Acceptable use of information and other associated assets | Rules for the acceptable use and procedures for handling information and other associated assets should be identified, documented, and implemented. The purpose is to ensure information and other associated assets are appropriately protected, used, and handled. | Setting rules for acceptable use and procedures for handling information provide information about unacceptable behaviours on use of information in the organization. |
83 | #21 Set Rules | People | 6.02 Terms and conditions of employment | The employment contractual agreements should state the personnel's and the organization's responsibilities for information security. The purpose is to ensure personnel understand their information security responsibilities for the roles for which they are considered. | Having terms and conditions of employment provide information about employee responsibilities and their behaviours during the employment period in the organization. |
84 | #21 Set Rules | People | 6.04 Disciplinary process | 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. The purpose is to ensure personnel and other relevant interested parties understand the consequences of information security policy violation, to deter and appropriately deal with personnel who committed the violation. | A formalized disciplinary process that is communicated to employees provides information about unacceptable behaviours on committing an information security policy violation in the organization. |
85 | #21 Set Rules | People | 6.05 Responsibilities after termination or change of employment | 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. The purpose is to protect the organiation's interests as part of the process of changing or terminating employment or contracts. | Communicating information security responsibilities and duties that remain valid even after termination provides information about unacceptable behaviours on shirking information security responsibilities in the organization. |
86 | #21 Set Rules | People | 6.06 Confidentiality or non-disclosure agreements | 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. The purpose is to maintain confidentiality of information accessible by personnel or external parties. | Having confidentiality or non-disclosure agreements signed by employees can provide information about unacceptable behaviours on leaking confidential information in the organization. |
SCP ‘#22 Post Instructions’ aims to provide detailed information about how to meet the behavioural requirements in a setting [31]. | |||||
87 | #22 Post Instructions | Organizational | 5.37 Documented operating procedures | Operating procedures for information processing facilities should be documented and made available to personnel who need them. The purpose is to ensure the correct and secure operation of information processing facilities. | Documenting operating procedures for information processing facilities provides detailed information on the expectations of the employees in ensuring the correct and secure operation of the information processing facilities. |
88 | #22 Post Instructions | People | 6.03 Information security awareness, education, and training | Personnel of the organization and relevant interested parties should receive appropriate information security awareness, education and training, and regular updates of the organization’s information security policy, topic-specific policies and procedures, as relevant for their job function. The purpose is to ensure personnel and relevant interested parties are aware of and fulfil their information security responsibilities. | Information security awareness education and training provide detailed instructions about how to meet the behavioural requirements on information security in the organization. |
SCP ‘#24 Assist Compliance’ aims to make it easier to carry out acceptable behaviours in a setting [31]. | |||||
89 | #24 Assist Compliance | Organizational | 5.04 Management responsibilities | Management should require all personnel to apply information security in accordance with the established information security policy, topic-specific policies and procedures of the organization. The purpose is to ensure management understand their role in information security and undertake actions aiming to ensure all personnel are aware of and fulfil their information security responsibilities. | Having management to require personnel to apply information security in accordance with established information security policies and procedures in the organization makes it easier for all personnel in the organization to know and carry out acceptable information security behaviours. |
90 | #24 Assist Compliance | Organizational | 5.31 Legal, statutory, regulatory, and contractual requirements | Legal, statutory, regulatory, and contractual requirements relevant to information security and the organization’s approach to meet these requirements should be identified, documented, and kept up-to-date. | Complying with legal, statutory, regulatory, and contractual requirements can make it easier for employees to meet their information security obligations in the organization. |
91 | #24 Assist Compliance | Organizational | 5.32 Intellectual property rights | The organization should implement appropriate procedures to protect intellectual property rights. The purpose is to ensure compliance with legal, statutory, regulatory, and contractual requirements related to intellectual property rights and use of proprietary products. | Having procedures to protect intellectual property rights can assist in the compliance with legal, statutory, regulatory, and contractual requirements, which in turn can make it easier for the employees to meet their legal obligations in the organization. |
92 | #24 Assist Compliance | Organizational | 5.34 Privacy and protection of PII | The organization should identify and meet the requirements regarding the preservation of privacy and protection of PII according to applicable laws and regulations and contractual requirements. The purpose is to ensure compliance with legal, statutory, regulatory, and contractual requirements related to the information security aspects of the protection of PII. | Meeting PII requirements in compliance with legal, statutory, regulatory, and contractual requirements can make it easier for employees to meet their legal obligations in the organization. |
93 | #24 Assist Compliance | Organizational | 5.36 Conformance with policies, rules, and standards for information security | Compliance with the organization’s information security policy, topic-specific policies, rules, and standards should be regularly reviewed. The purpose is to ensure that information security is implemented and operated in accordance with the organization’s information security policy, topic-specific policies, rules, and standards. | Regularly reviewing the organization’s information security policies and related matters can ensure that the policies are up-to-date, and this can make it easier for employees to carry out their information security obligations in an up-to-date manner. |
No. . | SCP technique . | Clause type . | ISO/IEC control . | ISO/IEC control description and purpose . | Rationale . |
---|---|---|---|---|---|
S1 INCREASE THE EFFORTS aims to block or limit the actions or movements of offenders[31]. | |||||
SCP ‘#01 Harden Targets’ makes it more difficult for offenders to get to or use the target to achieve their criminal purposes [31]. | |||||
1 | #01 Harden Targets | Organizational | 5.08 Information security in project management | Information security should be integrated into project management. The purpose is to ensure information security risks related to projects and deliverables are effectively addressed in project management throughout the project life cycle. | Integrating information security into project management can make the project more secure and therefore more difficult for the offender to get to or use the target to achieve criminal purposes (such as ransomware or DDoS attacks). |
2 | #01 Harden Targets | Organizational | 5.19 Information security in supplier relationships | Processes and procedures should be defined and implemented to manage the information security risks associated with the use of supplier's products or services. The purpose is to maintain an agreed level of information security in supplier relationships. | Managing information security risks about the use of supplier products and services can make it more difficult for the offender to get to or use the target (such as the supplier products and services) to achieve criminal purposes (such as ransomware or DDoS attacks). |
3 | #01 Harden Targets | Organizational | 5.20 Addressing information security within supplier agreements | Relevant information security requirements should be established and agreed with each supplier based on the type of supplier relationship. The purpose is to maintain an agreed level of information security in supplier relationships. | Establishing information security requirements for suppliers can make it more difficult for the offender to get to or use the target (such as the supplier products and services) to achieve criminal purposes (such as ransomware or DDoS attacks). |
4 | #01 Harden Targets | Organizational | 5.21 Managing information security in the ICT supply chain | Processes and procedures should be defined and implemented to manage information security risks associated with the ICT products and services supply chain. The purpose is to maintain an agreed level of information security in supplier relationships. | Managing information security risks about the ICT products and services supply chain can make it more difficult for the offender to get to or use the target (such as ICT supply chain) to achieve criminal purposes (such as ransomware or DDoS attacks). |
5 | #01 Harden Targets | Organizational | 5.23 Information security for use of cloud services | Processes for acquisition, use, management, and exit from cloud services should be established in accordance with the organization's information security requirements. The purpose is to specify and manage information security for the use of cloud services. | Specifying and managing information security for the use of cloud services can make it more difficult for the offender to get to or use the target (such as information systems and data stored in cloud) to achieve criminal purposes. |
6 | #01 Harden Targets | Organizational | 5.27 Learning from information security incidents | Knowledge gained from information security incidents should be used to strengthen and improve the information security controls. The purpose is to reduce the likelihood or consequences of future incidents. | Learning from information security events can reduce the likelihood or consequences of future incidents. This in turn makes it more difficult for the offender to get to or use the target to achieve the criminal purpose (such as ransomware or DDoS attacks). |
7 | #01 Harden Targets | Organizational | 5.29 Information security during disruption | The organization should plan how to maintain information security at an appropriate level during disruption. The purpose is to protect information and other associated assets during disruption. | The ability to maintain information security despite disruption can make it more difficult for the offender to get to or use the target (such as information systems that are affected by disruption) to achieve criminal purposes (such as ransomware or DDoS attacks). |
8 | #01 Harden Targets | Organizational | 5.33 Protection of records | Records should be protected from loss, destruction, falsification, unauthorized access, and unauthorized release. The purpose is to ensure compliance with legal, statutory, regulatory, and contractual requirements, as well as community or societal expectations related to the protection and availability of records. | Ensuring that the records are protected can make it more difficult for offenders to use the crime targets (such as data losses) for their intended purposes (such as DDoS and ransomware attacks). |
9 | #01 Harden Targets | Organizational | 5.35 Independent review of information security | The organization’s approach to managing information security and its implementation, including people, processes, and technologies, should be reviewed independently at planned intervals, or when significant changes occur. The purpose is to ensure the continuing suitability, adequacy, and effectiveness of the organization’s approach to managing information security. | Having an independent review of information security can identify potential weaknesses that can be fixed before they are actually exploited by offenders. This in turn makes it more difficult for the offender to get to or use the target to achieve the criminal purpose (such as ransomware or DDoS attacks). |
10 | #01 Harden Targets | People | 6.07 Remote working | Security measures should be implemented when personnel are working remotely to protect information accessed, processed, or stored outside the organization’s premises. The purpose is to ensure the security of information when personnel are working remotely. | Implementing security measures when personnel are working remotely will make it more difficult for offender to get to or use the target (such as employees working remotely) to achieve the criminal purposes (such as ransomware or DDoS attacks). |
11 | #01 Harden Targets | Physical | 7.03 Securing offices, rooms, and facilities | Physical security for offices, rooms and facilities should be designed and implemented. The purpose is to prevent unauthorized physical access, damage and interference to the organization’s information and other associated assets in offices, rooms and facilities. | Securing offices, rooms, and facilities can make it more difficult for the offender to get to or use the target (such as offices) to achieve criminal purposes (such as ransomware or DDoS attacks). |
12 | #01 Harden Targets | Physical | 7.05 Protecting against physical and environmental threats | Protection against physical and environmental threats, such as natural disasters and other intentional or unintentional physical threats to infrastructure should be designed and implemented. The purpose is to prevent or reduce the consequences of events originating from physical and environmental threats. | Protection against physical and environmental threats can make it more difficult for offenders to make use of these threats to get to or use the target (such as computing infrastructure) to achieve criminal purposes (such as ransomware or DDoS attacks). |
13 | #01 Harden Targets | Physical | 7.06 Working in secure areas | Security measures for working in secure areas should be designed and implemented. The purpose is to protect information and other associated assets in secure areas from damage and unauthorized interference by personnel working in these areas. | Security measures for working in secure areas can make it more difficult for the offender to get to or use the target (such as sensitive office areas) to achieve the criminal purposes (such as ransomware or DDoS attacks). |
14 | #01 Harden Targets | Physical | 7.08 Equipment siting and protection | Equipment should be sited securely and protected. The purpose is to reduce the risks from physical and environmental threats, and from unauthorized access and damage. | Equipment that is sited securely and protected can make it more difficult for the offender to get to or use the target to achieve criminal purposes. |
15 | #01 Harden Targets | Physical | 7.09 Security of assets off-premises | Off-site assets should be protected. The purpose is to prevent loss, damage, theft, or compromise of off-site assets and interruption to the organization’s operations. | Protecting off-site assets can make it more difficult for the offender to get to or use the target (such as assets) to achieve criminal purposes (such as ransomware or DDoS attacks). |
16 | #01 Harden Targets | Physical | 7.10 Storage media | Storage media should be managed through its life cycle of acquisition, use, transportation, and disposal in accordance with the organization’s classification scheme and handling requirements. The purpose is to ensure only authorized disclosure, modification, removal, or destruction of information on storage media. | Managing storage media can make it more difficult for the offender to get to or use the target (such as storage media) to achieve criminal purposes (such as ransomware or DDoS attacks). |
17 | #01 Harden Targets | Physical | 7.11 Supporting utilities | Information processing facilities should be protected from power failures and other disruptions caused by failures in supporting utilities. The purpose is to prevent loss, damage, or compromise of information and other associated assets, or interruption to the organization’s operations due to the failure and disruption of supporting utilities. | Information processing facilities should be protected from power failures and other disruptions caused by failures in supporting utilities. |
18 | #01 Harden Targets | Physical | 7.12 Cabling security | Cables carrying power, data, or supporting information services should be protected from interception, interference, or damage. The purpose is to prevent loss, damage, theft, or compromise of information and other associated assets and interruption to the organization’s operations related to power and communications cabling. | Protecting cables can make it more difficult for the offender to get to or use the target (such as cables) to achieve criminal purposes (such as ransomware or DDoS attacks). |
19 | #01 Harden Targets | Physical | 7.13 Equipment maintenance | Equipment should be maintained correctly to ensure availability, integrity, and confidentiality of information. The purpose is to prevent loss, damage, theft, or compromise of information and other associated assets and interruption to the organization’s operations caused by lack of maintenance. | Maintaining equipment can make it more difficult for the offender to get to or use the target (such as equipment) to achieve criminal purposes (such as ransomware or DDoS attacks). |
20 | #01 Harden Targets | Technological | 8.01 User endpoint devices | Information stored on, processed by, or accessible via user endpoint devices should be protected. The purpose is to protect information against the risks introduced by using user endpoint devices. | Protecting user endpoint devices can make it more difficult for the offender to get to or use the target (such as user endpoint devices) to achieve criminal purposes (such as ransomware or DDoS attacks). |
21 | #01 Harden Targets | Technological | 8.07 Protection against malware | Protection against malware should be implemented and supported by appropriate user awareness. The purpose is to ensure information and other associated assets are protected against malware. | Protection against malware can make it more difficult for the offender to get to or use the target (such as computing devices) to achieve criminal purposes (such as ransomware or DDoS attacks). |
22 | #01 Harden Targets | Technological | 8.08 Management of technical vulnerabilities | 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. The purpose is to prevent exploitation of technical vulnerabilities. | Managing technical vulnerabilities in information systems can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
23 | #01 Harden Targets | Technological | 8.09 Configuration management | Configurations, including security configurations, of hardware, software, services, and networks should be established, documented, implemented, monitored, and reviewed. The purpose is to ensure hardware, software, services, and networks function correctly with required security settings, and configuration is not altered by unauthorized or incorrect changes. | Managing configurations can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
24 | #01 Harden Targets | Technological | 8.23 Web filtering | Access to external websites should be managed to reduce exposure to malicious content. The purpose is to protect systems from being compromised by malware and to prevent access to unauthorized web resources. | Managing access to external websites can make it more difficult for the offender to get to or use the target (such as external websites) to achieve criminal purposes (such as downloading malware for subsequent cyberattacks). |
25 | #01 Harden Targets | Technological | 8.25 Secure development life cycle | Rules for the secure development of software and systems should be established and applied. The purpose is to ensure information security is designed and implemented within the secure development life cycle of software and systems. | Secure development of software can make it more difficult for the offender to get to or use the target (such as software) to achieve criminal purposes (such as ransomware or DDoS attacks). |
26 | #01 Harden Targets | Technological | 8.26 Application security requirements | Information security requirements should be identified, specified, and approved when developing or acquiring applications. The purpose is to ensure all information security requirements are identified and addressed when developing or acquiring applications. | Identifying and addressing application security requirements can make it more difficult for the offender to get to or use the target (such as application) to achieve criminal purposes (such as ransomware or DDoS attacks). |
27 | #01 Harden Targets | Technological | 8.27 Secure system architecture and engineering principles | Principles for engineering secure systems should be established, documented, maintained, and applied to any information system development activities. The purpose is to ensure information systems are securely designed, implemented, and operated within the development life cycle. | Applying secure system architecture and engineering principles can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
28 | #01 Harden Targets | Technological | 8.28 Secure coding | Secure coding principles should be applied to software development. The purpose is to ensure software is written securely, thereby reducing the number of potential information security vulnerabilities in the software. | Applying secure coding principles can make it more difficult for the offender to get to or use the target (such as software) to achieve criminal purposes (such as ransomware or DDoS attacks). |
29 | #01 Harden Targets | Technological | 8.29 Security testing in development and acceptance | Security testing processes should be defined and implemented in the development life cycle. The purpose is to validate if information security requirements are met when applications or code are deployed to the production environment. | Security testing can make it more difficult for the offender to get to or use the target (such as applications and websites) to achieve criminal purposes (such as ransomware or DDoS attacks). |
30 | #01 Harden Targets | Technological | 8.30 Outsourced development | The organization should direct, monitor, and review the activities related to outsourced system development. The purpose is to ensure information security measures required by the organization are implemented in outsourced system development. | Ensuring that information security measures required by the organization are implemented in outsourced system development can make it more difficult for the offender to get to or use the target to achieve criminal purposes. |
31 | #01 Harden Targets | Technological | 8.32 Change management | Changes to information processing facilities and information systems should be subject to change management procedures. The purpose is to preserve information security when executing changes. | Managing change management can make it more difficult for the offender to get to or use the target (such as applications and websites) to achieve criminal purposes (such as ransomware or DDoS attacks). |
32 | #01 Harden Targets | Technological | 8.33 Test information | Test information should be appropriately selected, protected, and managed. The purpose is to ensure relevance of testing and protection of operational information used for testing. | Protecting test information can make it more difficult for the offender to get to or use the target (such as test information) to achieve criminal purposes (such as cyber reconnaissance). |
33 | #01 Harden Targets | Technological | 8.34 Protection of information systems during audit testing | Audit tests and other assurance activities involving assessment of operational systems should be planned and agreed between the tester and appropriate management. The purpose is to minimize the impact of audit and other assurance activities on operational systems and business processes. | Protecting information systems during audit testing can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
SCP ‘#02 Control Access to Facilities’ aims to block offenders access to places where they may carry out a criminal action [31]. | |||||
34 | #05 Control Tools/Weapons | Organizational | 5.15 Access control | Returning the organization’s assets upon the end of the employment, contract, or agreement can prevent and block the ex-employee from using the organization’s assets (such as notebooks, access cards, and keys) to access the organization’s places and assets. | Returning the organization’s assets upon the end of the employment, contract, or agreement can limit offender access to these instruments (such as notebooks, access cards, and keys) associated with particular modus operandi (such as hacking, DDoS, and ransomware attacks). |
35 | #02 Control Access to Facilities | Organizational | 5.15 Access 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. The purpose is to ensure authorized access and to prevent unauthorized access to information and other associated assets. | Controlling physical and logical access to information and related assets can block access to places (such as applications and websites) where a criminal action (such as data breach) may be carried out. |
36 | #02 Control Access to Facilities | Organizational | 5.18 Access rights | Access rights to information and other associated assets should be provisioned, reviewed, modified, and removed in accordance with the organization’s topic-specific policy on and rules for access control. The purpose is to ensure access to information and other associated assets is defined and authorized according to the business requirements. | Controlling the access rights to information and associated assets can block access to places (such as applications and websites) where a criminal action (such as data breach) may be carried out. |
37 | #02 Control Access to Facilities | Physical | 7.01 Physical security perimeters | Security perimeters should be defined and used to protect areas that contain information and other associated assets. | Physical security perimeters can block access to places (such as data centres) where a criminal action (such as hacking) may be carried out. |
38 | #02 Control Access to Facilities | Physical | 7.02 Physical entry | Secure areas should be protected by appropriate entry controls and access points. The purpose is to ensure only authorized physical access to the organization’s information and other associated assets occurs. | Physical entries can block access to places (such as data centres) where a criminal action (such as hacking) may be carried out. |
39 | #02 Control Access to Facilities | Technological | 8.02 Privileged access rights | The allocation and use of privileged access rights should be restricted and managed. The purpose is to ensure only authorized users, software components, and services are provided with privileged access rights. | Controlling privileged access rights can block access to places (such as applications and websites) where criminal action (such as ransomware and hacking) may be carried out. |
40 | #02 Control Access to Facilities | Technological | 8.20 Networks security | Networks and network devices should be secured, managed, and controlled to protect information in systems and applications. The purpose is to protect information in networks and its supporting information processing facilities from compromise via the network. | Protecting networks, which are gateways to places (such as computing devices and websites) can block access to places where criminal actions (such as hacking and data breaches) may be carried out. |
41 | #02 Control Access to Facilities | Technological | 8.21 Security of network services | Security mechanisms, service levels, and service requirements of network services should be identified, implemented, and monitored. The purpose is to ensure security in the use of network services. | Protecting network services, which are gateways to places (such as computing devices and websites) can block access to places where criminal actions (such as hacking and data breaches) may be carried out. |
SCP ‘#03 Screen Exits’ aims to make it more difficult for the offender to leave a place after their criminal action [31]. | |||||
42 | #03 Screen Exits | Technological | 8.12 Data leakage prevention | Data leakage prevention measures should be applied to systems, networks, and any other devices that process, store, or transmit sensitive information. The purpose is to detect and prevent the unauthorized disclosure and extraction of information by individuals or systems. | Data leakage prevention measures can make it more difficult for the offender to leave a place (such as network perimeter) after a criminal action (such as data leakage). |
SCP ‘#04 Deflect offenders’ aims to change the offender’s existing or potential movement patterns [31]. | |||||
43 | #04 Deflect offenders | Technological | 8.22 Segregation of networks | Groups of information services, users, and information systems should be segregated in the organization’s networks. The purpose is to split the network in security boundaries and to control traffic between them based on business needs. | Segregating networks can change existing or potential offender movement patterns (such as hacking patterns). |
44 | #04 Deflect offenders | Technological | 8.31 Separation of development, test and production environments | Development, testing, and production environments should be separated and secured. The purpose is to protect the production environment and data from compromise by development and test activities. | Separating the development, test, and production environments can change existing or potential offender movement patterns (such as hacking patterns). |
SCP ‘#05 Control Tools/Weapons’ aims to limit offender access to or use instruments associated with a criminal modus operandi [31]. | |||||
45 | #05 Control Tools/Weapons | Technological | 8.18 Use of privileged utility programs | The use of utility programs that can be capable of overriding system and application controls should be restricted and tightly controlled. The purpose is to ensure the use of utility programs does not harm system and application controls for information security. | Restricting and controlling privileged utility programs that can be misused can limit offender access to these instruments (such as privileged utility programs) associated with particular modus operandi (such as hacking, DDoS, and ransomware attacks). |
46 | #05 Control Tools/Weapons | Technological | 8.19 Installation of software on operational systems | Procedures and measures should be implemented to securely manage software installation on operational systems. The purpose is to ensure the integrity of operational systems and prevent exploitation of technical vulnerabilities. | Managing installation of software that can be misused (such as rootkits and trojans) can limit offender access to these instruments (such as software on operational systems) associated with particular modus operandi (such as hacking, DDoS, and ransomware attacks). |
S2 Increase the Risks aims to provide more or better guardianship to increase the likelihood of detecting offenders[31]. | |||||
SCP ‘#06 Extend Guardianships’ aims to provide incentives to encourage unofficial guardians to act or be more effective [31]. | |||||
47 | #06 Extend Guardianships | People | 6.08 Information security event reporting | The organization should provide a mechanism for personnel to report observed or suspected information security events through appropriate channels in a timely manner. The purpose is to support timely, consistent, and effective reporting of information security events that can be identified by personnel. | A mechanism for personnel to report information security events will provide incentives to encourage unofficial guardians (such as employees, contractors, and users) to act or be more effective because there is a channel for them to report. |
SCP ‘#07 Assist natural surveillance’ aims to increase the likelihood that potential guardians will see criminal actions happening in places [31]. | |||||
48 | #07 Assist natural surveillance | Organizational | 5.22 Monitoring, review and change management of supplier services | The organization should regularly monitor, review, evaluate, and manage change in supplier information security practices and service delivery. The purpose is to maintain an agreed level of information security and service delivery in line with supplier agreements. | Regularly reviewing supplier information security practices and service delivery can increase the likelihood that guardians (such as owners of supplier services) will see any criminal actions occurring in places belonging to the supplier. |
SCP ‘#08 Reduce Anonymity’ aims to increase the likelihood that potential guardians will identify the features of offenders [31]. | |||||
49 | #08 Reduce Anonymity | Organizational | 5.06 Contact with special interest groups | The organization should establish and maintain contact with special interest groups or other specialist security forums and professional associations. The purpose is to ensure appropriate flow of information takes place with respect to information security. | Contacting special interest groups or other specialist security forums and professional associations to exchange cybersecurity information increases the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of potential offenders (such as hackers). |
50 | #08 Reduce Anonymity | Organizational | 5.16 Identity management | The full life cycle of identities should be managed. The purpose is to allow for the unique identification of individuals and systems accessing the organization’s information and other associated assets and to enable appropriate assignment of access rights. | Identity management increases the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of potential offenders (such as hackers). |
51 | #08 Reduce Anonymity | Organizational | 5.17 Authentication information | Allocation and management of authentication information should be controlled by a management process, including advising personnel of appropriate handling of authentication information. The purpose is to ensure proper entity authentication and prevent failures of authentication processes. | Properly managing authentication information increases the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of potential offenders (such as hackers). |
52 | #08 Reduce Anonymity | People | 6.01 Screening | Background verification checks on all candidates to become personnel should be carried out prior to joining the organization and on an ongoing basis taking into consideration applicable laws, regulations, and ethics, and be proportional to the business requirements, the classification of the information to be accessed, and the perceived risks. The purpose is to ensure all personnel are eligible and suitable for the roles for which they are considered and remain eligible and suitable during their employment. | Background screening can increase the likelihood that potential guardians (such as human resource department) can identify the features of the offenders (such as insiders). |
53 | #08 Reduce Anonymity | Technological | 8.05 Secure authentication | Secure authentication technologies and procedures should be implemented based on information access restrictions and the topic-specific policy on access control. The purpose is to ensure a user, or an entity is securely authenticated, when access to systems, applications, and services is granted. | Secure authentication can increase the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of offenders (such as hackers). |
SCP ‘#09 Utilise Place Managers’ aims to use existing or new employees or managers as potential guardians or to change the settings to limit criminal opportunities [31]. | |||||
54 | #09 Utilise Place Managers | Organizational | 5.02 Information security roles and responsibilities | Information security roles and responsibilities should be defined and allocated according to the organization needs. The purpose is to establish a defined, approved, and understood structure for the implementation, operation, and management of information security within the organization. | Existing or new employees are used as potential guardians (such as cybersecurity professionals and Security Operation Centres) in information security roles. |
SCP ‘#10 Strengthen Formal Surveillance’ aims to provide official or formal guardians or increase their ability to be more effective in dealing with criminal opportunities [31]. | |||||
55 | #10 Strengthen Formal Surveillance | Organizational | 5.03 Segregation of duties | Conflicting duties and areas of responsibility should be segregated. The purpose is to reduce the risk of fraud, error, and bypassing of information security controls. | Segregation of duties increases the official or formal guardians’ ability to supervise activities because the official or formal guardians are checking one another or involved in each other’s activities. |
56 | #10 Strengthen Formal Surveillance | Organizational | 5.07 Threat intelligence | Information relating to information security threats should be collected and analysed to produce threat intelligence. The purpose is to provide awareness of the organization’s threat environment so that the appropriate mitigation actions can be taken. | Collecting threat intelligence information for analysis to provide awareness of the organization’s threat environment can increase the ability of official or formal guardians' (such as cybersecurity professionals and Security Operation Centres) ability to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
57 | #10 Strengthen Formal Surveillance | Organizational | 5.24 Information security incident management planning and preparation | The organization should plan and prepare for managing information security incidents by defining, establishing, and communicating information security incident management processes, roles, and responsibilities. The purpose is to ensure quick, effective, consistent, and orderly response to information security incidents, including communication on information security events. | Quick and orderly response to information security incidents allows organizations to react in a timely manner to such incidents and can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
58 | #10 Strengthen Formal Surveillance | Organizational | 5.25 Assessment and decision on information security events | The organization should assess information security events and decide if they are to be categorized as information security incidents. The purpose is to ensure effective categorization and prioritization of information security events. | Assessing information security events for more effective categorization and prioritization increases the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as ransomware or DDOS attacks). |
59 | #10 Strengthen Formal Surveillance | Organizational | 5.28 Collection of evidence | The organization should establish and implement procedures for the identification, collection, acquisition, and preservation of evidence related to information security events. | Collecting evidence of information security events increases the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as ransomware or DDOS attacks). |
60 | #10 Strengthen Formal Surveillance | Physical | 7.04 Physical security monitoring | Premises should be continuously monitored for unauthorized physical access. | Physical security monitoring can assist official or formal guardians (such as cybersecurity professionals and Security Operation Centres) or increase their ability to be effective in situations with potential crime opportunities (such as thefts). |
61 | #10 Strengthen Formal Surveillance | Technological | 8.15 Logging | Logs that record activities, exceptions, faults, and other relevant events should be produced, stored, protected, and analysed. The purpose is to record events, generate evidence, ensure the integrity of log information, prevent against unauthorized access, identify information security events that can lead to an information security incident, and to support investigations. | Logging provides information on potential information security incidents. which can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
62 | #10 Strengthen Formal Surveillance | Technological | 8.16 Monitoring activities | Networks, systems, and applications should be monitored for anomalous behaviour and appropriate actions taken to evaluate potential information security incidents. The purpose is to detect anomalous behaviour and potential information security incidents. | Monitoring activities can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
63 | #10 Strengthen Formal Surveillance | Technological | 8.17 Clock synchronization | The clocks of information processing systems used by the organization should be synchronized to approved time sources. The purpose is to enable the correlation and analysis of security-related events and other recorded data, and to support investigations into information security incidents. | Clock synchronization of information processing systems can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
S3 Reduce the Rewards aims to limit the value of a target (or victim) for the offender or their ability to find their target or victim[31]. | |||||
SCP ‘#11 Conceal Targets’ aims to limit the offenders’ ability to see targets [31]. | |||||
64 | #11 Conceal Targets | Organizational | 5.12 Classification of information | Information should be classified according to the information security needs of the organization based on confidentiality, integrity, availability, and relevant interested party requirements. The purpose is to ensure identification and understanding of protection needs of information in accordance with its importance to the organization. | Classifying information according to their information security needs can limit the offenders’ ability to see targets (such as information) that are classified more strictly. |
65 | #11 Conceal Targets | People | 7.07 Clear desk and clear screen | Clear desk rules for papers and removable storage media and clear screen rules for information processing facilities should be defined and appropriately enforced. The purpose is to reduce the risks of unauthorized access, loss of, and damage to information on desks, screens, and in other accessible locations during and outside normal working hours. | Clearing desks and screens can limit offenders' ability to see crime targets (such as information on the desk or screen). |
66 | #11 Conceal Targets | Technological | 8.03 Information access restriction | Access to information and other associated assets should be restricted in accordance with the established topic-specific policy on access control. The purpose is to ensure only authorized access and to prevent unauthorized access to information and other associated assets. | Restricting access to information or associated assets can limit the offenders' ability to see these targets (such as information). |
67 | #11 Conceal Targets | Technological | 8.04 Access to source code | Read and write access to source code, development tools, and software libraries should be appropriately managed. The purpose is to prevent the introduction of unauthorized functionality, avoid unintentional or malicious changes, and to maintain the confidentiality of valuable intellectual property. | Restricting access to source codes can limit the offenders' ability to see these targets (such as source codes). |
68 | #11 Conceal Targets | Technological | 8.11 Data masking | Data masking should be used in accordance with the organization’s topic-specific policy on access control and other related topic-specific, and business requirements, taking applicable legislation into consideration. The purpose is to limit the exposure of sensitive data, including personally identifiable information, and to comply with legal, statutory, regulatory, and contractual requirements. | Masking data can limit the offenders’ ability to see these targets (such as data). |
69 | #11 Conceal Targets | Technological | 8.24 Use of cryptography | Rules for the effective use of cryptography, including cryptographic key management, should be defined and implemented. The purpose is to ensure proper and effective use of cryptography to protect the confidentiality, authenticity, or integrity of information according to business and information security requirements, and taking into consideration legal, statutory, regulatory, and contractual requirements related to cryptography. | Using cryptography can limit the offenders’ ability to see crime targets (such as information). |
SCP ‘#12 Remove Targets’ aims to take away potential targets or remove the valuable aspects of them [31]. | |||||
70 | #12 Remove Targets | Physical | 7.14 Secure disposal or re-use of equipment | 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. The purpose is to prevent leakage of information from equipment to be disposed or re-used. | Secure disposal of storage media can remove the valuable aspects of the targets (such as data in the storage media). |
71 | #12 Remove Targets | Technological | 8.10 Information deletion | Information stored in information systems, devices, or in any other storage media should be deleted when no longer required. The purpose is to prevent unnecessary exposure of sensitive information and to conform with legal, statutory, regulatory, and contractual requirements for information deletion. | Deleting information when no longer required can remove the valuable aspects of the targets (such as value of the data itself). |
SCP ‘#13 Identify Property’ aims to mark potential targets to make them traceable to the owner or to reduce the ability of offenders to claim ownerships [31]. | |||||
72 | #13 Identify Property | Organizational | 5.09 Inventory of information and other associated assets | An inventory of information and other associated assets, including owners, should be developed and maintained. The purpose is to identify the organization's information and other associated assets in order to preserve their information security and assign appropriate ownership. | Maintaining an inventory of information and related assets marks information and related assets to make them traceable to the owner and reduces the ability of the offender to claim ownership. |
73 | #13 Identify Property | Organizational | 5.13 Labelling of information | An appropriate set of procedures for information labelling should be developed and implemented in accordance with the information classification scheme adopted by the organization. The purpose is to facilitate the communication of classification of information and support automation of information processing and management. | Labelling information marks and identifies the information so that it can be more traceable to the owner and reduce the ability of the offender to claim ownership. |
SCP ‘#14 Disrupt Markets’ aims to make it difficult for offenders to transfer their criminal proceeds to others [31]. | |||||
74 | #14 Disrupt Markets | Organizational | 5.05 Contact with authorities | The organization should establish and maintain contact with relevant authorities. The purpose is to ensure appropriate flow of information takes place with respect to information security between the organization and relevant legal, regulatory, and supervisory authorities. | Contacting authorities makes it difficult for offenders (such as hackers) to transfer their proceeds (such as data) to others. |
75 | #14 Disrupt Markets | Organizational | 5.14 Information transfer | Information transfer rules, procedures, or agreements should be in place for all types of transfer facilities within the organization and between the organization and other parties. The purpose is to maintain the security of information transferred within an organization and with any external interested party. | Having information transfer rules can make it difficult for offenders to transfer the proceeds of their crimes (such as data) to others. |
76 | #14 Disrupt Markets | Organizational | 5.26 Response to information security incidents | Information security incidents should be responded to in accordance with the documented procedures. The purpose is to ensure efficient and effective response to information security incidents. | Responding to information security incidents in a timely manner can make it difficult for the offender to transfer the proceeds of crime (such as data) to others. |
SCP ‘#15 Deny Benefits’ aims to make it difficult for offenders to use their criminal targets for their intended purposes [31]. | |||||
77 | #15 Deny Benefits | Organizational | 5.30 ICT readiness for business continuity | ICT readiness should be planned, implemented, maintained, and tested based on business continuity objectives and ICT continuity requirements. The purpose is to ensure the availability of the organization’s information and other associated assets during disruption. | Ensuring that there is ICT readiness and availability in the organization can make it difficult for offenders to use the crime targets (such as data losses) for their intended purposes (such as DDoS and ransomware attacks). |
78 | #15 Deny Benefits | Technological | 8.06 Capacity management | The use of resources should be monitored and adjusted in line with current and expected capacity requirements. The purpose is to ensure the required capacity of information processing facilities, human resources, offices, and other facilities. | Managing resources capacity can make it difficult for offenders to use crime targets (such as information processing facilities) for the intended purpose such as denying the availability of the resources. |
79 | #15 Deny Benefits | Technological | 8.13 Information backup | Backup copies of information, software, and systems should be maintained and regularly tested in accordance with the agreed topic-specific policy on backup. | Backup of information, software, and systems can make it difficult for offenders to use crime targets (such as data losses) for the intended purpose (such as ransomware attacks). |
80 | #15 Deny Benefits | Technological | 8.14 Redundancy of information processing facilities | Information processing facilities should be implemented with redundancy sufficient to meet availability requirements. The purpose is to ensure the continuous operation of information processing facilities. | Redundancy of information processing facilities (such as data centres) can make it difficult for offenders to use crime targets (data centres) for the intended purpose (such as DDoS attacks). |
S5 Remove Excuses that offenders can give by presenting, explaining and reminding them about their responsibility[31]. | |||||
SCP ‘#21 Set Rules’ aims to provide information about unacceptable behaviours in a setting [31]. | |||||
81 | #21 Set Rules | Organizational | 5.01 Policies for information security | 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. The purpose is to ensure continuing suitability, adequacy, effectiveness of management direction, and support for information security in accordance with business requirements, legal, statutory, regulatory, and contractual requirements. | Having policies for information security sets rules on what is unacceptable information security practices in the organization. |
82 | #21 Set Rules | Organizational | 5.10 Acceptable use of information and other associated assets | Rules for the acceptable use and procedures for handling information and other associated assets should be identified, documented, and implemented. The purpose is to ensure information and other associated assets are appropriately protected, used, and handled. | Setting rules for acceptable use and procedures for handling information provide information about unacceptable behaviours on use of information in the organization. |
83 | #21 Set Rules | People | 6.02 Terms and conditions of employment | The employment contractual agreements should state the personnel's and the organization's responsibilities for information security. The purpose is to ensure personnel understand their information security responsibilities for the roles for which they are considered. | Having terms and conditions of employment provide information about employee responsibilities and their behaviours during the employment period in the organization. |
84 | #21 Set Rules | People | 6.04 Disciplinary process | 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. The purpose is to ensure personnel and other relevant interested parties understand the consequences of information security policy violation, to deter and appropriately deal with personnel who committed the violation. | A formalized disciplinary process that is communicated to employees provides information about unacceptable behaviours on committing an information security policy violation in the organization. |
85 | #21 Set Rules | People | 6.05 Responsibilities after termination or change of employment | 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. The purpose is to protect the organiation's interests as part of the process of changing or terminating employment or contracts. | Communicating information security responsibilities and duties that remain valid even after termination provides information about unacceptable behaviours on shirking information security responsibilities in the organization. |
86 | #21 Set Rules | People | 6.06 Confidentiality or non-disclosure agreements | 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. The purpose is to maintain confidentiality of information accessible by personnel or external parties. | Having confidentiality or non-disclosure agreements signed by employees can provide information about unacceptable behaviours on leaking confidential information in the organization. |
SCP ‘#22 Post Instructions’ aims to provide detailed information about how to meet the behavioural requirements in a setting [31]. | |||||
87 | #22 Post Instructions | Organizational | 5.37 Documented operating procedures | Operating procedures for information processing facilities should be documented and made available to personnel who need them. The purpose is to ensure the correct and secure operation of information processing facilities. | Documenting operating procedures for information processing facilities provides detailed information on the expectations of the employees in ensuring the correct and secure operation of the information processing facilities. |
88 | #22 Post Instructions | People | 6.03 Information security awareness, education, and training | Personnel of the organization and relevant interested parties should receive appropriate information security awareness, education and training, and regular updates of the organization’s information security policy, topic-specific policies and procedures, as relevant for their job function. The purpose is to ensure personnel and relevant interested parties are aware of and fulfil their information security responsibilities. | Information security awareness education and training provide detailed instructions about how to meet the behavioural requirements on information security in the organization. |
SCP ‘#24 Assist Compliance’ aims to make it easier to carry out acceptable behaviours in a setting [31]. | |||||
89 | #24 Assist Compliance | Organizational | 5.04 Management responsibilities | Management should require all personnel to apply information security in accordance with the established information security policy, topic-specific policies and procedures of the organization. The purpose is to ensure management understand their role in information security and undertake actions aiming to ensure all personnel are aware of and fulfil their information security responsibilities. | Having management to require personnel to apply information security in accordance with established information security policies and procedures in the organization makes it easier for all personnel in the organization to know and carry out acceptable information security behaviours. |
90 | #24 Assist Compliance | Organizational | 5.31 Legal, statutory, regulatory, and contractual requirements | Legal, statutory, regulatory, and contractual requirements relevant to information security and the organization’s approach to meet these requirements should be identified, documented, and kept up-to-date. | Complying with legal, statutory, regulatory, and contractual requirements can make it easier for employees to meet their information security obligations in the organization. |
91 | #24 Assist Compliance | Organizational | 5.32 Intellectual property rights | The organization should implement appropriate procedures to protect intellectual property rights. The purpose is to ensure compliance with legal, statutory, regulatory, and contractual requirements related to intellectual property rights and use of proprietary products. | Having procedures to protect intellectual property rights can assist in the compliance with legal, statutory, regulatory, and contractual requirements, which in turn can make it easier for the employees to meet their legal obligations in the organization. |
92 | #24 Assist Compliance | Organizational | 5.34 Privacy and protection of PII | The organization should identify and meet the requirements regarding the preservation of privacy and protection of PII according to applicable laws and regulations and contractual requirements. The purpose is to ensure compliance with legal, statutory, regulatory, and contractual requirements related to the information security aspects of the protection of PII. | Meeting PII requirements in compliance with legal, statutory, regulatory, and contractual requirements can make it easier for employees to meet their legal obligations in the organization. |
93 | #24 Assist Compliance | Organizational | 5.36 Conformance with policies, rules, and standards for information security | Compliance with the organization’s information security policy, topic-specific policies, rules, and standards should be regularly reviewed. The purpose is to ensure that information security is implemented and operated in accordance with the organization’s information security policy, topic-specific policies, rules, and standards. | Regularly reviewing the organization’s information security policies and related matters can ensure that the policies are up-to-date, and this can make it easier for employees to carry out their information security obligations in an up-to-date manner. |
No. . | SCP technique . | Clause type . | ISO/IEC control . | ISO/IEC control description and purpose . | Rationale . |
---|---|---|---|---|---|
S1 INCREASE THE EFFORTS aims to block or limit the actions or movements of offenders[31]. | |||||
SCP ‘#01 Harden Targets’ makes it more difficult for offenders to get to or use the target to achieve their criminal purposes [31]. | |||||
1 | #01 Harden Targets | Organizational | 5.08 Information security in project management | Information security should be integrated into project management. The purpose is to ensure information security risks related to projects and deliverables are effectively addressed in project management throughout the project life cycle. | Integrating information security into project management can make the project more secure and therefore more difficult for the offender to get to or use the target to achieve criminal purposes (such as ransomware or DDoS attacks). |
2 | #01 Harden Targets | Organizational | 5.19 Information security in supplier relationships | Processes and procedures should be defined and implemented to manage the information security risks associated with the use of supplier's products or services. The purpose is to maintain an agreed level of information security in supplier relationships. | Managing information security risks about the use of supplier products and services can make it more difficult for the offender to get to or use the target (such as the supplier products and services) to achieve criminal purposes (such as ransomware or DDoS attacks). |
3 | #01 Harden Targets | Organizational | 5.20 Addressing information security within supplier agreements | Relevant information security requirements should be established and agreed with each supplier based on the type of supplier relationship. The purpose is to maintain an agreed level of information security in supplier relationships. | Establishing information security requirements for suppliers can make it more difficult for the offender to get to or use the target (such as the supplier products and services) to achieve criminal purposes (such as ransomware or DDoS attacks). |
4 | #01 Harden Targets | Organizational | 5.21 Managing information security in the ICT supply chain | Processes and procedures should be defined and implemented to manage information security risks associated with the ICT products and services supply chain. The purpose is to maintain an agreed level of information security in supplier relationships. | Managing information security risks about the ICT products and services supply chain can make it more difficult for the offender to get to or use the target (such as ICT supply chain) to achieve criminal purposes (such as ransomware or DDoS attacks). |
5 | #01 Harden Targets | Organizational | 5.23 Information security for use of cloud services | Processes for acquisition, use, management, and exit from cloud services should be established in accordance with the organization's information security requirements. The purpose is to specify and manage information security for the use of cloud services. | Specifying and managing information security for the use of cloud services can make it more difficult for the offender to get to or use the target (such as information systems and data stored in cloud) to achieve criminal purposes. |
6 | #01 Harden Targets | Organizational | 5.27 Learning from information security incidents | Knowledge gained from information security incidents should be used to strengthen and improve the information security controls. The purpose is to reduce the likelihood or consequences of future incidents. | Learning from information security events can reduce the likelihood or consequences of future incidents. This in turn makes it more difficult for the offender to get to or use the target to achieve the criminal purpose (such as ransomware or DDoS attacks). |
7 | #01 Harden Targets | Organizational | 5.29 Information security during disruption | The organization should plan how to maintain information security at an appropriate level during disruption. The purpose is to protect information and other associated assets during disruption. | The ability to maintain information security despite disruption can make it more difficult for the offender to get to or use the target (such as information systems that are affected by disruption) to achieve criminal purposes (such as ransomware or DDoS attacks). |
8 | #01 Harden Targets | Organizational | 5.33 Protection of records | Records should be protected from loss, destruction, falsification, unauthorized access, and unauthorized release. The purpose is to ensure compliance with legal, statutory, regulatory, and contractual requirements, as well as community or societal expectations related to the protection and availability of records. | Ensuring that the records are protected can make it more difficult for offenders to use the crime targets (such as data losses) for their intended purposes (such as DDoS and ransomware attacks). |
9 | #01 Harden Targets | Organizational | 5.35 Independent review of information security | The organization’s approach to managing information security and its implementation, including people, processes, and technologies, should be reviewed independently at planned intervals, or when significant changes occur. The purpose is to ensure the continuing suitability, adequacy, and effectiveness of the organization’s approach to managing information security. | Having an independent review of information security can identify potential weaknesses that can be fixed before they are actually exploited by offenders. This in turn makes it more difficult for the offender to get to or use the target to achieve the criminal purpose (such as ransomware or DDoS attacks). |
10 | #01 Harden Targets | People | 6.07 Remote working | Security measures should be implemented when personnel are working remotely to protect information accessed, processed, or stored outside the organization’s premises. The purpose is to ensure the security of information when personnel are working remotely. | Implementing security measures when personnel are working remotely will make it more difficult for offender to get to or use the target (such as employees working remotely) to achieve the criminal purposes (such as ransomware or DDoS attacks). |
11 | #01 Harden Targets | Physical | 7.03 Securing offices, rooms, and facilities | Physical security for offices, rooms and facilities should be designed and implemented. The purpose is to prevent unauthorized physical access, damage and interference to the organization’s information and other associated assets in offices, rooms and facilities. | Securing offices, rooms, and facilities can make it more difficult for the offender to get to or use the target (such as offices) to achieve criminal purposes (such as ransomware or DDoS attacks). |
12 | #01 Harden Targets | Physical | 7.05 Protecting against physical and environmental threats | Protection against physical and environmental threats, such as natural disasters and other intentional or unintentional physical threats to infrastructure should be designed and implemented. The purpose is to prevent or reduce the consequences of events originating from physical and environmental threats. | Protection against physical and environmental threats can make it more difficult for offenders to make use of these threats to get to or use the target (such as computing infrastructure) to achieve criminal purposes (such as ransomware or DDoS attacks). |
13 | #01 Harden Targets | Physical | 7.06 Working in secure areas | Security measures for working in secure areas should be designed and implemented. The purpose is to protect information and other associated assets in secure areas from damage and unauthorized interference by personnel working in these areas. | Security measures for working in secure areas can make it more difficult for the offender to get to or use the target (such as sensitive office areas) to achieve the criminal purposes (such as ransomware or DDoS attacks). |
14 | #01 Harden Targets | Physical | 7.08 Equipment siting and protection | Equipment should be sited securely and protected. The purpose is to reduce the risks from physical and environmental threats, and from unauthorized access and damage. | Equipment that is sited securely and protected can make it more difficult for the offender to get to or use the target to achieve criminal purposes. |
15 | #01 Harden Targets | Physical | 7.09 Security of assets off-premises | Off-site assets should be protected. The purpose is to prevent loss, damage, theft, or compromise of off-site assets and interruption to the organization’s operations. | Protecting off-site assets can make it more difficult for the offender to get to or use the target (such as assets) to achieve criminal purposes (such as ransomware or DDoS attacks). |
16 | #01 Harden Targets | Physical | 7.10 Storage media | Storage media should be managed through its life cycle of acquisition, use, transportation, and disposal in accordance with the organization’s classification scheme and handling requirements. The purpose is to ensure only authorized disclosure, modification, removal, or destruction of information on storage media. | Managing storage media can make it more difficult for the offender to get to or use the target (such as storage media) to achieve criminal purposes (such as ransomware or DDoS attacks). |
17 | #01 Harden Targets | Physical | 7.11 Supporting utilities | Information processing facilities should be protected from power failures and other disruptions caused by failures in supporting utilities. The purpose is to prevent loss, damage, or compromise of information and other associated assets, or interruption to the organization’s operations due to the failure and disruption of supporting utilities. | Information processing facilities should be protected from power failures and other disruptions caused by failures in supporting utilities. |
18 | #01 Harden Targets | Physical | 7.12 Cabling security | Cables carrying power, data, or supporting information services should be protected from interception, interference, or damage. The purpose is to prevent loss, damage, theft, or compromise of information and other associated assets and interruption to the organization’s operations related to power and communications cabling. | Protecting cables can make it more difficult for the offender to get to or use the target (such as cables) to achieve criminal purposes (such as ransomware or DDoS attacks). |
19 | #01 Harden Targets | Physical | 7.13 Equipment maintenance | Equipment should be maintained correctly to ensure availability, integrity, and confidentiality of information. The purpose is to prevent loss, damage, theft, or compromise of information and other associated assets and interruption to the organization’s operations caused by lack of maintenance. | Maintaining equipment can make it more difficult for the offender to get to or use the target (such as equipment) to achieve criminal purposes (such as ransomware or DDoS attacks). |
20 | #01 Harden Targets | Technological | 8.01 User endpoint devices | Information stored on, processed by, or accessible via user endpoint devices should be protected. The purpose is to protect information against the risks introduced by using user endpoint devices. | Protecting user endpoint devices can make it more difficult for the offender to get to or use the target (such as user endpoint devices) to achieve criminal purposes (such as ransomware or DDoS attacks). |
21 | #01 Harden Targets | Technological | 8.07 Protection against malware | Protection against malware should be implemented and supported by appropriate user awareness. The purpose is to ensure information and other associated assets are protected against malware. | Protection against malware can make it more difficult for the offender to get to or use the target (such as computing devices) to achieve criminal purposes (such as ransomware or DDoS attacks). |
22 | #01 Harden Targets | Technological | 8.08 Management of technical vulnerabilities | 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. The purpose is to prevent exploitation of technical vulnerabilities. | Managing technical vulnerabilities in information systems can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
23 | #01 Harden Targets | Technological | 8.09 Configuration management | Configurations, including security configurations, of hardware, software, services, and networks should be established, documented, implemented, monitored, and reviewed. The purpose is to ensure hardware, software, services, and networks function correctly with required security settings, and configuration is not altered by unauthorized or incorrect changes. | Managing configurations can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
24 | #01 Harden Targets | Technological | 8.23 Web filtering | Access to external websites should be managed to reduce exposure to malicious content. The purpose is to protect systems from being compromised by malware and to prevent access to unauthorized web resources. | Managing access to external websites can make it more difficult for the offender to get to or use the target (such as external websites) to achieve criminal purposes (such as downloading malware for subsequent cyberattacks). |
25 | #01 Harden Targets | Technological | 8.25 Secure development life cycle | Rules for the secure development of software and systems should be established and applied. The purpose is to ensure information security is designed and implemented within the secure development life cycle of software and systems. | Secure development of software can make it more difficult for the offender to get to or use the target (such as software) to achieve criminal purposes (such as ransomware or DDoS attacks). |
26 | #01 Harden Targets | Technological | 8.26 Application security requirements | Information security requirements should be identified, specified, and approved when developing or acquiring applications. The purpose is to ensure all information security requirements are identified and addressed when developing or acquiring applications. | Identifying and addressing application security requirements can make it more difficult for the offender to get to or use the target (such as application) to achieve criminal purposes (such as ransomware or DDoS attacks). |
27 | #01 Harden Targets | Technological | 8.27 Secure system architecture and engineering principles | Principles for engineering secure systems should be established, documented, maintained, and applied to any information system development activities. The purpose is to ensure information systems are securely designed, implemented, and operated within the development life cycle. | Applying secure system architecture and engineering principles can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
28 | #01 Harden Targets | Technological | 8.28 Secure coding | Secure coding principles should be applied to software development. The purpose is to ensure software is written securely, thereby reducing the number of potential information security vulnerabilities in the software. | Applying secure coding principles can make it more difficult for the offender to get to or use the target (such as software) to achieve criminal purposes (such as ransomware or DDoS attacks). |
29 | #01 Harden Targets | Technological | 8.29 Security testing in development and acceptance | Security testing processes should be defined and implemented in the development life cycle. The purpose is to validate if information security requirements are met when applications or code are deployed to the production environment. | Security testing can make it more difficult for the offender to get to or use the target (such as applications and websites) to achieve criminal purposes (such as ransomware or DDoS attacks). |
30 | #01 Harden Targets | Technological | 8.30 Outsourced development | The organization should direct, monitor, and review the activities related to outsourced system development. The purpose is to ensure information security measures required by the organization are implemented in outsourced system development. | Ensuring that information security measures required by the organization are implemented in outsourced system development can make it more difficult for the offender to get to or use the target to achieve criminal purposes. |
31 | #01 Harden Targets | Technological | 8.32 Change management | Changes to information processing facilities and information systems should be subject to change management procedures. The purpose is to preserve information security when executing changes. | Managing change management can make it more difficult for the offender to get to or use the target (such as applications and websites) to achieve criminal purposes (such as ransomware or DDoS attacks). |
32 | #01 Harden Targets | Technological | 8.33 Test information | Test information should be appropriately selected, protected, and managed. The purpose is to ensure relevance of testing and protection of operational information used for testing. | Protecting test information can make it more difficult for the offender to get to or use the target (such as test information) to achieve criminal purposes (such as cyber reconnaissance). |
33 | #01 Harden Targets | Technological | 8.34 Protection of information systems during audit testing | Audit tests and other assurance activities involving assessment of operational systems should be planned and agreed between the tester and appropriate management. The purpose is to minimize the impact of audit and other assurance activities on operational systems and business processes. | Protecting information systems during audit testing can make it more difficult for the offender to get to or use the target (such as information systems) to achieve criminal purposes (such as ransomware or DDoS attacks). |
SCP ‘#02 Control Access to Facilities’ aims to block offenders access to places where they may carry out a criminal action [31]. | |||||
34 | #05 Control Tools/Weapons | Organizational | 5.15 Access control | Returning the organization’s assets upon the end of the employment, contract, or agreement can prevent and block the ex-employee from using the organization’s assets (such as notebooks, access cards, and keys) to access the organization’s places and assets. | Returning the organization’s assets upon the end of the employment, contract, or agreement can limit offender access to these instruments (such as notebooks, access cards, and keys) associated with particular modus operandi (such as hacking, DDoS, and ransomware attacks). |
35 | #02 Control Access to Facilities | Organizational | 5.15 Access 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. The purpose is to ensure authorized access and to prevent unauthorized access to information and other associated assets. | Controlling physical and logical access to information and related assets can block access to places (such as applications and websites) where a criminal action (such as data breach) may be carried out. |
36 | #02 Control Access to Facilities | Organizational | 5.18 Access rights | Access rights to information and other associated assets should be provisioned, reviewed, modified, and removed in accordance with the organization’s topic-specific policy on and rules for access control. The purpose is to ensure access to information and other associated assets is defined and authorized according to the business requirements. | Controlling the access rights to information and associated assets can block access to places (such as applications and websites) where a criminal action (such as data breach) may be carried out. |
37 | #02 Control Access to Facilities | Physical | 7.01 Physical security perimeters | Security perimeters should be defined and used to protect areas that contain information and other associated assets. | Physical security perimeters can block access to places (such as data centres) where a criminal action (such as hacking) may be carried out. |
38 | #02 Control Access to Facilities | Physical | 7.02 Physical entry | Secure areas should be protected by appropriate entry controls and access points. The purpose is to ensure only authorized physical access to the organization’s information and other associated assets occurs. | Physical entries can block access to places (such as data centres) where a criminal action (such as hacking) may be carried out. |
39 | #02 Control Access to Facilities | Technological | 8.02 Privileged access rights | The allocation and use of privileged access rights should be restricted and managed. The purpose is to ensure only authorized users, software components, and services are provided with privileged access rights. | Controlling privileged access rights can block access to places (such as applications and websites) where criminal action (such as ransomware and hacking) may be carried out. |
40 | #02 Control Access to Facilities | Technological | 8.20 Networks security | Networks and network devices should be secured, managed, and controlled to protect information in systems and applications. The purpose is to protect information in networks and its supporting information processing facilities from compromise via the network. | Protecting networks, which are gateways to places (such as computing devices and websites) can block access to places where criminal actions (such as hacking and data breaches) may be carried out. |
41 | #02 Control Access to Facilities | Technological | 8.21 Security of network services | Security mechanisms, service levels, and service requirements of network services should be identified, implemented, and monitored. The purpose is to ensure security in the use of network services. | Protecting network services, which are gateways to places (such as computing devices and websites) can block access to places where criminal actions (such as hacking and data breaches) may be carried out. |
SCP ‘#03 Screen Exits’ aims to make it more difficult for the offender to leave a place after their criminal action [31]. | |||||
42 | #03 Screen Exits | Technological | 8.12 Data leakage prevention | Data leakage prevention measures should be applied to systems, networks, and any other devices that process, store, or transmit sensitive information. The purpose is to detect and prevent the unauthorized disclosure and extraction of information by individuals or systems. | Data leakage prevention measures can make it more difficult for the offender to leave a place (such as network perimeter) after a criminal action (such as data leakage). |
SCP ‘#04 Deflect offenders’ aims to change the offender’s existing or potential movement patterns [31]. | |||||
43 | #04 Deflect offenders | Technological | 8.22 Segregation of networks | Groups of information services, users, and information systems should be segregated in the organization’s networks. The purpose is to split the network in security boundaries and to control traffic between them based on business needs. | Segregating networks can change existing or potential offender movement patterns (such as hacking patterns). |
44 | #04 Deflect offenders | Technological | 8.31 Separation of development, test and production environments | Development, testing, and production environments should be separated and secured. The purpose is to protect the production environment and data from compromise by development and test activities. | Separating the development, test, and production environments can change existing or potential offender movement patterns (such as hacking patterns). |
SCP ‘#05 Control Tools/Weapons’ aims to limit offender access to or use instruments associated with a criminal modus operandi [31]. | |||||
45 | #05 Control Tools/Weapons | Technological | 8.18 Use of privileged utility programs | The use of utility programs that can be capable of overriding system and application controls should be restricted and tightly controlled. The purpose is to ensure the use of utility programs does not harm system and application controls for information security. | Restricting and controlling privileged utility programs that can be misused can limit offender access to these instruments (such as privileged utility programs) associated with particular modus operandi (such as hacking, DDoS, and ransomware attacks). |
46 | #05 Control Tools/Weapons | Technological | 8.19 Installation of software on operational systems | Procedures and measures should be implemented to securely manage software installation on operational systems. The purpose is to ensure the integrity of operational systems and prevent exploitation of technical vulnerabilities. | Managing installation of software that can be misused (such as rootkits and trojans) can limit offender access to these instruments (such as software on operational systems) associated with particular modus operandi (such as hacking, DDoS, and ransomware attacks). |
S2 Increase the Risks aims to provide more or better guardianship to increase the likelihood of detecting offenders[31]. | |||||
SCP ‘#06 Extend Guardianships’ aims to provide incentives to encourage unofficial guardians to act or be more effective [31]. | |||||
47 | #06 Extend Guardianships | People | 6.08 Information security event reporting | The organization should provide a mechanism for personnel to report observed or suspected information security events through appropriate channels in a timely manner. The purpose is to support timely, consistent, and effective reporting of information security events that can be identified by personnel. | A mechanism for personnel to report information security events will provide incentives to encourage unofficial guardians (such as employees, contractors, and users) to act or be more effective because there is a channel for them to report. |
SCP ‘#07 Assist natural surveillance’ aims to increase the likelihood that potential guardians will see criminal actions happening in places [31]. | |||||
48 | #07 Assist natural surveillance | Organizational | 5.22 Monitoring, review and change management of supplier services | The organization should regularly monitor, review, evaluate, and manage change in supplier information security practices and service delivery. The purpose is to maintain an agreed level of information security and service delivery in line with supplier agreements. | Regularly reviewing supplier information security practices and service delivery can increase the likelihood that guardians (such as owners of supplier services) will see any criminal actions occurring in places belonging to the supplier. |
SCP ‘#08 Reduce Anonymity’ aims to increase the likelihood that potential guardians will identify the features of offenders [31]. | |||||
49 | #08 Reduce Anonymity | Organizational | 5.06 Contact with special interest groups | The organization should establish and maintain contact with special interest groups or other specialist security forums and professional associations. The purpose is to ensure appropriate flow of information takes place with respect to information security. | Contacting special interest groups or other specialist security forums and professional associations to exchange cybersecurity information increases the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of potential offenders (such as hackers). |
50 | #08 Reduce Anonymity | Organizational | 5.16 Identity management | The full life cycle of identities should be managed. The purpose is to allow for the unique identification of individuals and systems accessing the organization’s information and other associated assets and to enable appropriate assignment of access rights. | Identity management increases the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of potential offenders (such as hackers). |
51 | #08 Reduce Anonymity | Organizational | 5.17 Authentication information | Allocation and management of authentication information should be controlled by a management process, including advising personnel of appropriate handling of authentication information. The purpose is to ensure proper entity authentication and prevent failures of authentication processes. | Properly managing authentication information increases the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of potential offenders (such as hackers). |
52 | #08 Reduce Anonymity | People | 6.01 Screening | Background verification checks on all candidates to become personnel should be carried out prior to joining the organization and on an ongoing basis taking into consideration applicable laws, regulations, and ethics, and be proportional to the business requirements, the classification of the information to be accessed, and the perceived risks. The purpose is to ensure all personnel are eligible and suitable for the roles for which they are considered and remain eligible and suitable during their employment. | Background screening can increase the likelihood that potential guardians (such as human resource department) can identify the features of the offenders (such as insiders). |
53 | #08 Reduce Anonymity | Technological | 8.05 Secure authentication | Secure authentication technologies and procedures should be implemented based on information access restrictions and the topic-specific policy on access control. The purpose is to ensure a user, or an entity is securely authenticated, when access to systems, applications, and services is granted. | Secure authentication can increase the likelihood that potential guardians (such as cybersecurity professionals and Security Operation Centres) will identify features of offenders (such as hackers). |
SCP ‘#09 Utilise Place Managers’ aims to use existing or new employees or managers as potential guardians or to change the settings to limit criminal opportunities [31]. | |||||
54 | #09 Utilise Place Managers | Organizational | 5.02 Information security roles and responsibilities | Information security roles and responsibilities should be defined and allocated according to the organization needs. The purpose is to establish a defined, approved, and understood structure for the implementation, operation, and management of information security within the organization. | Existing or new employees are used as potential guardians (such as cybersecurity professionals and Security Operation Centres) in information security roles. |
SCP ‘#10 Strengthen Formal Surveillance’ aims to provide official or formal guardians or increase their ability to be more effective in dealing with criminal opportunities [31]. | |||||
55 | #10 Strengthen Formal Surveillance | Organizational | 5.03 Segregation of duties | Conflicting duties and areas of responsibility should be segregated. The purpose is to reduce the risk of fraud, error, and bypassing of information security controls. | Segregation of duties increases the official or formal guardians’ ability to supervise activities because the official or formal guardians are checking one another or involved in each other’s activities. |
56 | #10 Strengthen Formal Surveillance | Organizational | 5.07 Threat intelligence | Information relating to information security threats should be collected and analysed to produce threat intelligence. The purpose is to provide awareness of the organization’s threat environment so that the appropriate mitigation actions can be taken. | Collecting threat intelligence information for analysis to provide awareness of the organization’s threat environment can increase the ability of official or formal guardians' (such as cybersecurity professionals and Security Operation Centres) ability to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
57 | #10 Strengthen Formal Surveillance | Organizational | 5.24 Information security incident management planning and preparation | The organization should plan and prepare for managing information security incidents by defining, establishing, and communicating information security incident management processes, roles, and responsibilities. The purpose is to ensure quick, effective, consistent, and orderly response to information security incidents, including communication on information security events. | Quick and orderly response to information security incidents allows organizations to react in a timely manner to such incidents and can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
58 | #10 Strengthen Formal Surveillance | Organizational | 5.25 Assessment and decision on information security events | The organization should assess information security events and decide if they are to be categorized as information security incidents. The purpose is to ensure effective categorization and prioritization of information security events. | Assessing information security events for more effective categorization and prioritization increases the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as ransomware or DDOS attacks). |
59 | #10 Strengthen Formal Surveillance | Organizational | 5.28 Collection of evidence | The organization should establish and implement procedures for the identification, collection, acquisition, and preservation of evidence related to information security events. | Collecting evidence of information security events increases the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as ransomware or DDOS attacks). |
60 | #10 Strengthen Formal Surveillance | Physical | 7.04 Physical security monitoring | Premises should be continuously monitored for unauthorized physical access. | Physical security monitoring can assist official or formal guardians (such as cybersecurity professionals and Security Operation Centres) or increase their ability to be effective in situations with potential crime opportunities (such as thefts). |
61 | #10 Strengthen Formal Surveillance | Technological | 8.15 Logging | Logs that record activities, exceptions, faults, and other relevant events should be produced, stored, protected, and analysed. The purpose is to record events, generate evidence, ensure the integrity of log information, prevent against unauthorized access, identify information security events that can lead to an information security incident, and to support investigations. | Logging provides information on potential information security incidents. which can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
62 | #10 Strengthen Formal Surveillance | Technological | 8.16 Monitoring activities | Networks, systems, and applications should be monitored for anomalous behaviour and appropriate actions taken to evaluate potential information security incidents. The purpose is to detect anomalous behaviour and potential information security incidents. | Monitoring activities can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
63 | #10 Strengthen Formal Surveillance | Technological | 8.17 Clock synchronization | The clocks of information processing systems used by the organization should be synchronized to approved time sources. The purpose is to enable the correlation and analysis of security-related events and other recorded data, and to support investigations into information security incidents. | Clock synchronization of information processing systems can increase the ability of official or formal guardians (such as cybersecurity professionals and Security Operation Centres) to be effective in situations with potential crime opportunities (such as hacking and ransomware attacks). |
S3 Reduce the Rewards aims to limit the value of a target (or victim) for the offender or their ability to find their target or victim[31]. | |||||
SCP ‘#11 Conceal Targets’ aims to limit the offenders’ ability to see targets [31]. | |||||
64 | #11 Conceal Targets | Organizational | 5.12 Classification of information | Information should be classified according to the information security needs of the organization based on confidentiality, integrity, availability, and relevant interested party requirements. The purpose is to ensure identification and understanding of protection needs of information in accordance with its importance to the organization. | Classifying information according to their information security needs can limit the offenders’ ability to see targets (such as information) that are classified more strictly. |
65 | #11 Conceal Targets | People | 7.07 Clear desk and clear screen | Clear desk rules for papers and removable storage media and clear screen rules for information processing facilities should be defined and appropriately enforced. The purpose is to reduce the risks of unauthorized access, loss of, and damage to information on desks, screens, and in other accessible locations during and outside normal working hours. | Clearing desks and screens can limit offenders' ability to see crime targets (such as information on the desk or screen). |
66 | #11 Conceal Targets | Technological | 8.03 Information access restriction | Access to information and other associated assets should be restricted in accordance with the established topic-specific policy on access control. The purpose is to ensure only authorized access and to prevent unauthorized access to information and other associated assets. | Restricting access to information or associated assets can limit the offenders' ability to see these targets (such as information). |
67 | #11 Conceal Targets | Technological | 8.04 Access to source code | Read and write access to source code, development tools, and software libraries should be appropriately managed. The purpose is to prevent the introduction of unauthorized functionality, avoid unintentional or malicious changes, and to maintain the confidentiality of valuable intellectual property. | Restricting access to source codes can limit the offenders' ability to see these targets (such as source codes). |
68 | #11 Conceal Targets | Technological | 8.11 Data masking | Data masking should be used in accordance with the organization’s topic-specific policy on access control and other related topic-specific, and business requirements, taking applicable legislation into consideration. The purpose is to limit the exposure of sensitive data, including personally identifiable information, and to comply with legal, statutory, regulatory, and contractual requirements. | Masking data can limit the offenders’ ability to see these targets (such as data). |
69 | #11 Conceal Targets | Technological | 8.24 Use of cryptography | Rules for the effective use of cryptography, including cryptographic key management, should be defined and implemented. The purpose is to ensure proper and effective use of cryptography to protect the confidentiality, authenticity, or integrity of information according to business and information security requirements, and taking into consideration legal, statutory, regulatory, and contractual requirements related to cryptography. | Using cryptography can limit the offenders’ ability to see crime targets (such as information). |
SCP ‘#12 Remove Targets’ aims to take away potential targets or remove the valuable aspects of them [31]. | |||||
70 | #12 Remove Targets | Physical | 7.14 Secure disposal or re-use of equipment | 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. The purpose is to prevent leakage of information from equipment to be disposed or re-used. | Secure disposal of storage media can remove the valuable aspects of the targets (such as data in the storage media). |
71 | #12 Remove Targets | Technological | 8.10 Information deletion | Information stored in information systems, devices, or in any other storage media should be deleted when no longer required. The purpose is to prevent unnecessary exposure of sensitive information and to conform with legal, statutory, regulatory, and contractual requirements for information deletion. | Deleting information when no longer required can remove the valuable aspects of the targets (such as value of the data itself). |
SCP ‘#13 Identify Property’ aims to mark potential targets to make them traceable to the owner or to reduce the ability of offenders to claim ownerships [31]. | |||||
72 | #13 Identify Property | Organizational | 5.09 Inventory of information and other associated assets | An inventory of information and other associated assets, including owners, should be developed and maintained. The purpose is to identify the organization's information and other associated assets in order to preserve their information security and assign appropriate ownership. | Maintaining an inventory of information and related assets marks information and related assets to make them traceable to the owner and reduces the ability of the offender to claim ownership. |
73 | #13 Identify Property | Organizational | 5.13 Labelling of information | An appropriate set of procedures for information labelling should be developed and implemented in accordance with the information classification scheme adopted by the organization. The purpose is to facilitate the communication of classification of information and support automation of information processing and management. | Labelling information marks and identifies the information so that it can be more traceable to the owner and reduce the ability of the offender to claim ownership. |
SCP ‘#14 Disrupt Markets’ aims to make it difficult for offenders to transfer their criminal proceeds to others [31]. | |||||
74 | #14 Disrupt Markets | Organizational | 5.05 Contact with authorities | The organization should establish and maintain contact with relevant authorities. The purpose is to ensure appropriate flow of information takes place with respect to information security between the organization and relevant legal, regulatory, and supervisory authorities. | Contacting authorities makes it difficult for offenders (such as hackers) to transfer their proceeds (such as data) to others. |
75 | #14 Disrupt Markets | Organizational | 5.14 Information transfer | Information transfer rules, procedures, or agreements should be in place for all types of transfer facilities within the organization and between the organization and other parties. The purpose is to maintain the security of information transferred within an organization and with any external interested party. | Having information transfer rules can make it difficult for offenders to transfer the proceeds of their crimes (such as data) to others. |
76 | #14 Disrupt Markets | Organizational | 5.26 Response to information security incidents | Information security incidents should be responded to in accordance with the documented procedures. The purpose is to ensure efficient and effective response to information security incidents. | Responding to information security incidents in a timely manner can make it difficult for the offender to transfer the proceeds of crime (such as data) to others. |
SCP ‘#15 Deny Benefits’ aims to make it difficult for offenders to use their criminal targets for their intended purposes [31]. | |||||
77 | #15 Deny Benefits | Organizational | 5.30 ICT readiness for business continuity | ICT readiness should be planned, implemented, maintained, and tested based on business continuity objectives and ICT continuity requirements. The purpose is to ensure the availability of the organization’s information and other associated assets during disruption. | Ensuring that there is ICT readiness and availability in the organization can make it difficult for offenders to use the crime targets (such as data losses) for their intended purposes (such as DDoS and ransomware attacks). |
78 | #15 Deny Benefits | Technological | 8.06 Capacity management | The use of resources should be monitored and adjusted in line with current and expected capacity requirements. The purpose is to ensure the required capacity of information processing facilities, human resources, offices, and other facilities. | Managing resources capacity can make it difficult for offenders to use crime targets (such as information processing facilities) for the intended purpose such as denying the availability of the resources. |
79 | #15 Deny Benefits | Technological | 8.13 Information backup | Backup copies of information, software, and systems should be maintained and regularly tested in accordance with the agreed topic-specific policy on backup. | Backup of information, software, and systems can make it difficult for offenders to use crime targets (such as data losses) for the intended purpose (such as ransomware attacks). |
80 | #15 Deny Benefits | Technological | 8.14 Redundancy of information processing facilities | Information processing facilities should be implemented with redundancy sufficient to meet availability requirements. The purpose is to ensure the continuous operation of information processing facilities. | Redundancy of information processing facilities (such as data centres) can make it difficult for offenders to use crime targets (data centres) for the intended purpose (such as DDoS attacks). |
S5 Remove Excuses that offenders can give by presenting, explaining and reminding them about their responsibility[31]. | |||||
SCP ‘#21 Set Rules’ aims to provide information about unacceptable behaviours in a setting [31]. | |||||
81 | #21 Set Rules | Organizational | 5.01 Policies for information security | 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. The purpose is to ensure continuing suitability, adequacy, effectiveness of management direction, and support for information security in accordance with business requirements, legal, statutory, regulatory, and contractual requirements. | Having policies for information security sets rules on what is unacceptable information security practices in the organization. |
82 | #21 Set Rules | Organizational | 5.10 Acceptable use of information and other associated assets | Rules for the acceptable use and procedures for handling information and other associated assets should be identified, documented, and implemented. The purpose is to ensure information and other associated assets are appropriately protected, used, and handled. | Setting rules for acceptable use and procedures for handling information provide information about unacceptable behaviours on use of information in the organization. |
83 | #21 Set Rules | People | 6.02 Terms and conditions of employment | The employment contractual agreements should state the personnel's and the organization's responsibilities for information security. The purpose is to ensure personnel understand their information security responsibilities for the roles for which they are considered. | Having terms and conditions of employment provide information about employee responsibilities and their behaviours during the employment period in the organization. |
84 | #21 Set Rules | People | 6.04 Disciplinary process | 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. The purpose is to ensure personnel and other relevant interested parties understand the consequences of information security policy violation, to deter and appropriately deal with personnel who committed the violation. | A formalized disciplinary process that is communicated to employees provides information about unacceptable behaviours on committing an information security policy violation in the organization. |
85 | #21 Set Rules | People | 6.05 Responsibilities after termination or change of employment | 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. The purpose is to protect the organiation's interests as part of the process of changing or terminating employment or contracts. | Communicating information security responsibilities and duties that remain valid even after termination provides information about unacceptable behaviours on shirking information security responsibilities in the organization. |
86 | #21 Set Rules | People | 6.06 Confidentiality or non-disclosure agreements | 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. The purpose is to maintain confidentiality of information accessible by personnel or external parties. | Having confidentiality or non-disclosure agreements signed by employees can provide information about unacceptable behaviours on leaking confidential information in the organization. |
SCP ‘#22 Post Instructions’ aims to provide detailed information about how to meet the behavioural requirements in a setting [31]. | |||||
87 | #22 Post Instructions | Organizational | 5.37 Documented operating procedures | Operating procedures for information processing facilities should be documented and made available to personnel who need them. The purpose is to ensure the correct and secure operation of information processing facilities. | Documenting operating procedures for information processing facilities provides detailed information on the expectations of the employees in ensuring the correct and secure operation of the information processing facilities. |
88 | #22 Post Instructions | People | 6.03 Information security awareness, education, and training | Personnel of the organization and relevant interested parties should receive appropriate information security awareness, education and training, and regular updates of the organization’s information security policy, topic-specific policies and procedures, as relevant for their job function. The purpose is to ensure personnel and relevant interested parties are aware of and fulfil their information security responsibilities. | Information security awareness education and training provide detailed instructions about how to meet the behavioural requirements on information security in the organization. |
SCP ‘#24 Assist Compliance’ aims to make it easier to carry out acceptable behaviours in a setting [31]. | |||||
89 | #24 Assist Compliance | Organizational | 5.04 Management responsibilities | Management should require all personnel to apply information security in accordance with the established information security policy, topic-specific policies and procedures of the organization. The purpose is to ensure management understand their role in information security and undertake actions aiming to ensure all personnel are aware of and fulfil their information security responsibilities. | Having management to require personnel to apply information security in accordance with established information security policies and procedures in the organization makes it easier for all personnel in the organization to know and carry out acceptable information security behaviours. |
90 | #24 Assist Compliance | Organizational | 5.31 Legal, statutory, regulatory, and contractual requirements | Legal, statutory, regulatory, and contractual requirements relevant to information security and the organization’s approach to meet these requirements should be identified, documented, and kept up-to-date. | Complying with legal, statutory, regulatory, and contractual requirements can make it easier for employees to meet their information security obligations in the organization. |
91 | #24 Assist Compliance | Organizational | 5.32 Intellectual property rights | The organization should implement appropriate procedures to protect intellectual property rights. The purpose is to ensure compliance with legal, statutory, regulatory, and contractual requirements related to intellectual property rights and use of proprietary products. | Having procedures to protect intellectual property rights can assist in the compliance with legal, statutory, regulatory, and contractual requirements, which in turn can make it easier for the employees to meet their legal obligations in the organization. |
92 | #24 Assist Compliance | Organizational | 5.34 Privacy and protection of PII | The organization should identify and meet the requirements regarding the preservation of privacy and protection of PII according to applicable laws and regulations and contractual requirements. The purpose is to ensure compliance with legal, statutory, regulatory, and contractual requirements related to the information security aspects of the protection of PII. | Meeting PII requirements in compliance with legal, statutory, regulatory, and contractual requirements can make it easier for employees to meet their legal obligations in the organization. |
93 | #24 Assist Compliance | Organizational | 5.36 Conformance with policies, rules, and standards for information security | Compliance with the organization’s information security policy, topic-specific policies, rules, and standards should be regularly reviewed. The purpose is to ensure that information security is implemented and operated in accordance with the organization’s information security policy, topic-specific policies, rules, and standards. | Regularly reviewing the organization’s information security policies and related matters can ensure that the policies are up-to-date, and this can make it easier for employees to carry out their information security obligations in an up-to-date manner. |