Home Tree Overview of Taxonomy

Operational Taxonomy

This taxonomy looks at the operational aspects of cybersecurity. The operational cybersecurity taxonomy was taken from:
Actions of People
Super categories -> Operational Taxonomy
Action, or lack of action, taken by people either deliberately or accidentally that impact cyber security
External Resources:
  • Insiders Behaving Badly: Addressing Bad Actors and Their Actions
    Shari Lawrence Pfleeger, Joel B. Predd, Jeffrey Hunker, Carla Bulford; IEEE Transactions on information forensics and security; no. 1 vol. 5; 2010.
  • TitleInsiders Behaving Badly: Addressing Bad Actors and Their Actions
    AuthorShari Lawrence Pfleeger, Joel B. Predd, Jeffrey Hunker, and Carla Bulford
    Year2009
    KeywordCyber crime, cyber security, insider threat.
    AbstractWe present a framework for describing insiders and their actions based on the organization, the environment, the system, and the individual. Using several real examples of unwelcome insider action (hard drive removal, stolen intellectual property, tax fraud, and proliferation of e-mail responses), we show how the taxonomy helps in understanding how each situation arose and could have been addressed. The differentiation among types of threats suggests how effective responses to insider threats might be shaped, what choices exist for each type of threat, and the implications of each. Future work will consider appropriate strategies to address each type of insider threat in terms of detection, prevention, mitigation, remediation, and punishment.
  • Mixed-Initiative Cyber Security: Putting humans in the right loop
    Jereme N. Haack, Glenn A. Fink, Wendy M. Maiden, David McKinnon, Errin W. Fulp; Proceedings AAMAS; 2009.
  • Title
    AuthorJereme N. Haack, Glenn A. Fink, Wendy M. Maiden, David McKinnon,
    Year
    Keywordagents; security; mixed-initiative
    AbstractOrganizations and their computer infrastructures have grown intertwined in complex relationships through mergers, acquisitions, reorganizations, and cooperative service delivery. Consequently, defensive actions and policy changes by one organization may have far-reaching negative consequences on the partner organizations. Human-centric and machine-centric approaches are insufficient for defending the security of today's increasingly complex computer infrastructures. The former are slow but highly adaptive, while the latter are fast but highly specialized. We believe the solution lies in mixed-initiative defenses combining the complementary qualities of both human- and machine-based approaches. We describe the Cooperative Infrastructure Defense (CID), a new cyberdefense paradigm designed to unify complex-adaptive swarm intelligence, logical rational agents, and human insight. CID will enable cooperative defense of infrastructure through situational awareness using visualization, security policy dialogue between humans and agents, shared initiative in solving cyber problems, and a foundation for building trust between humans and agents within and between organizations.
Inadvertent
Super categories -> Actions of People -> Operational Taxonomy
Refers to unintentional actions taken without malicious or harmful intent
External Resources:
Mistakes
Super categories -> Inadvertent -> Actions of People -> Operational Taxonomy
Individual with knowledge of the correct procedure accidentally taking incorrect action
External Resources:
Errors
Super categories -> Inadvertent -> Actions of People -> Operational Taxonomy
Individual without knowledge of the correct procedure taking incorrect action
External Resources:
Omissions
Super categories -> Inadvertent -> Actions of People -> Operational Taxonomy
Individual not taking a known correct action often due to hasty performance of a procedure
External Resources:
Deliberate
Super categories -> Actions of People -> Operational Taxonomy
Describes actions taken intentionally and with intent to do harm. Malware is one example of deliberate damage.
External Resources:
Fraud
Super categories -> Deliberate -> Actions of People -> Operational Taxonomy
A deliberate action taken to benefit oneself or a collaborator at the expense of the organization
External Resources:
  • Insiders Behaving Badly: Addressing Bad Actors and Their Actions
    Shari Lawrence Pfleeger, Joel B. Predd, Jeffrey Hunker, Carla Bulford; IEEE Transactions on information forensics and security; no. 1 vol. 5; 2010.
  • TitleInsiders Behaving Badly: Addressing Bad Actors and Their Actions
    AuthorShari Lawrence Pfleeger, Joel B. Predd, Jeffrey Hunker, and Carla Bulford
    Year2009
    KeywordCyber crime, cyber security, insider threat.
    AbstractWe present a framework for describing insiders and their actions based on the organization, the environment, the system, and the individual. Using several real examples of unwelcome insider action (hard drive removal, stolen intellectual property, tax fraud, and proliferation of e-mail responses), we show how the taxonomy helps in understanding how each situation arose and could have been addressed. The differentiation among types of threats suggests how effective responses to insider threats might be shaped, what choices exist for each type of threat, and the implications of each. Future work will consider appropriate strategies to address each type of insider threat in terms of detection, prevention, mitigation, remediation, and punishment.
Sabotage
Super categories -> Deliberate -> Actions of People -> Operational Taxonomy
A deliberate action taken to cause a failure in an organizational asset or process, generally carried out against targeted key assets by someone possessing or with access to inside knowledge
External Resources:
Theft
Super categories -> Deliberate -> Actions of People -> Operational Taxonomy
The intentional, unauthorized taking of organizational assets, in particular information assets
External Resources:
  • Towards Mechanisms for Detection and Prevention of Data Exfiltration by Insiders
    Elisa Bertino, Gabriel Ghinita; Proceedings ASIACCS; 2011.
  • TitleTowards Mechanisms for Detection and Prevention of Data Exfiltration by Insiders
    AuthorKeynote Talk Paper Elisa Bertino Gabriel Ghinita
    Year2011
    KeywordInsider Threat, Data Exfiltration.
    AbstractData represent an extremely important asset for any organization. Confidential data such as military secrets or intellectual property must never be disclosed outside the organization. Therefore, one of the most severe threats in the case of cyber-insider attacks is the loss of confidential data due to exfiltration. A malicious insider who has the proper credentials to access the organization databases may, over time, send data outside the organization network through a variety of channels, such as email, crafted HTTP requests that encapsulate data, etc. Existing security tools for detection of cyber-attacks focus on protecting the boundary between the organization and the outside world. Numerous network-level intrusion detection systems (IDS) exist, which monitor the traffic pattern and attempt to infer anomalous behavior. While such tools may be effective in protecting against external attacks, they are less suitable when the data exfiltration is performed by an insider who has the proper credentials and authorization to access resources within the organization. In this paper, we argue that DBMS-layer detection and prevention systems are the best alternative to defend against data exfiltration because: (1) DBMS access is performed through a standard, unique language (SQL) with well-understood semantics; (2) monitoring the potential disclosure of confidential data is more effective if done as close as possible to the data source; and (3) the DBMS layer already has in place a thorough mechanism for enforcing access control based on subject credentials. By analyzing the pattern of interaction between subjects and the DBMS, it is possible to detect anomalous activity that is indicative of early signs of exfiltration. In the paper, we outline a taxonomy of cyber-insider dimensions of activities that are indicative of data exfiltration, and we discuss a high-level architecture and mechanisms for early detection of exfiltration by insiders. We also outline a virtualization-based mechanism that prevents insiders from exfiltrating data, even in the case when they manage to gain control over the network. The protection mechanism relies on explicit authorization of data transfers that cross the organizational boundary.
Vandalism
Super categories -> Deliberate -> Actions of People -> Operational Taxonomy
The deliberate damaging of organizational assets, often at random
External Resources:
  • Cybercrime: Vandalizing the Information Society
    Steven Furnell; Proceedings ICWE; 2003.
  • TitleCybercrime: Vandalizing the Information Society
    AuthorSteven Furnell
    Year2003
    Keyword
    AbstractCybercrime has received significant coverage in recent years, with the media, law enforcers, and governments all working to bring the issue to our attention. This paper begins by presenting an overview of the problem, considering the scope and scale of reported incidents. From this, a series of common attack types are considered (focusing upon website defacement, denial of service and malware), with specific emphasis upon the potential for these to be automated and mounted by novices. Leading on from this, the problem of policing cybercrime is considered, with attention to the need for suitable legislation, and appropriate resourcing of law enforcers. It is concluded that that cybercrime is an inevitable downside of the information society, and that organizations and individuals consequently have a stake in ensuring their own protection.
Inaction
Super categories -> Actions of People -> Operational Taxonomy
Describes a lack of action or failure to act upon a given situation
External Resources:
Skills
Super categories -> Inaction -> Actions of People -> Operational Taxonomy
An individual’s lack of ability to undertake the necessary action
External Resources:
Knowledge
Super categories -> Inaction -> Actions of People -> Operational Taxonomy
An individual’s ignorance of the need to take action
External Resources:
Guidance
Super categories -> Inaction -> Actions of People -> Operational Taxonomy
A knowledgeable individual lacking the proper guidance or direction to act
External Resources:
Availability
Super categories -> Inaction -> Actions of People -> Operational Taxonomy
The unavailability or nonexistence of the appropriate resource needed to carry out the action
External Resources:
Systems and Technology Failures
Super categories -> Operational Taxonomy
Failure of hardware, software, and information systems
External Resources:
Hardware
Super categories -> Systems and Technology Failures -> Operational Taxonomy
Addresses risks traceable to failures in physical equipment due to capacity, performance, maintenance, and obsolescence
External Resources:
  • Research Trend on Secure SCADA Network Technology and Methods
    Farkhod Alsiherov, Taihoon Kim; WSEAS Transactions on systems and control; no. 8 vol. 5; 2010.
  • Title
    AuthorFarkhod Alsiherov, Taihoon Kim Dept. Multimedia Engineering Hannam University Daejeon, South Korea
    Year2010
    Keyword
    AbstractThe overall security concern facing the designers and operators of SCADA and, more generally, of industrial control systems typically originates either from malicious threat agents attempting to disrupt the control system operation, e.g. to create a power outage, or it originates from inadvertent actions, equipment failure, or similar. Electric utilities require secure network and control system. This paper illustrates solutions for control networks and equipment, SCADA data and communications.
Capacity
Super categories -> Hardware -> Systems and Technology Failures -> Operational Taxonomy
Inability to handle a given load or volume of information
External Resources:
  • SaaS performance and scalability evaluation in clouds
    SaaS Performance and Scalability Evaluation in Clouds; Proceedings SOSE; 2011.
  • TitleSaaS Performance and Scalability Evaluation in Clouds
    AuthorSan Jose State University, USA ®Tsinghua University, China Xiaoying Bai w. T. Tsai
    Year2011
    Keyword
    AbstractCloud computing not only changes today's computing infrastructure, but also alters the way of obtaining computing resources, managing and delivering software and services. Meanwhile, cloud computing brings new issues, challenges, and needs in performance testing, evaluation and scalability measurement due to the special features of cloud computing, such as elasticity and scalability. This paper focuses on performance evaluation and scalability measurement issue for Software as a Service (SaaS) in clouds. It proposes new formal graphic models and metrics to evaluate SaaS performance and analyze system scalability in clouds. In addition, the paper reports an evaluation approach based on Amazon's EC2 cloud technology and detailed case study results using the proposed models and metrics.
Performance
Super categories -> Hardware -> Systems and Technology Failures -> Operational Taxonomy
Inability to complete instructions or process information within acceptable parameters (speed, power consumption, heat load, etc.)
External Resources:
  • SaaS performance and scalability evaluation in clouds
    SaaS Performance and Scalability Evaluation in Clouds; Proceedings SOSE; 2011.
  • TitleSaaS Performance and Scalability Evaluation in Clouds
    AuthorSan Jose State University, USA ®Tsinghua University, China Xiaoying Bai w. T. Tsai
    Year2011
    Keyword
    AbstractCloud computing not only changes today's computing infrastructure, but also alters the way of obtaining computing resources, managing and delivering software and services. Meanwhile, cloud computing brings new issues, challenges, and needs in performance testing, evaluation and scalability measurement due to the special features of cloud computing, such as elasticity and scalability. This paper focuses on performance evaluation and scalability measurement issue for Software as a Service (SaaS) in clouds. It proposes new formal graphic models and metrics to evaluate SaaS performance and analyze system scalability in clouds. In addition, the paper reports an evaluation approach based on Amazon's EC2 cloud technology and detailed case study results using the proposed models and metrics.
Maintenance
Super categories -> Hardware -> Systems and Technology Failures -> Operational Taxonomy
Failure to perform required or recommended upkeep of the equipment
External Resources:
Obsolescence
Super categories -> Hardware -> Systems and Technology Failures -> Operational Taxonomy
Operation of the equipment beyond its supported service life
External Resources:
Software
Super categories -> Systems and Technology Failures -> Operational Taxonomy
Addresses risks stemming from software assets of all types, including programs, applications, and operating systems
External Resources:
Compatibility
Super categories -> Software -> Systems and Technology Failures -> Operational Taxonomy
Inability of two or more pieces of software to work together as expected
External Resources:
Configuration management
Super categories -> Software -> Systems and Technology Failures -> Operational Taxonomy
Improper application and management of the appropriate settings and parameters for the intended use
External Resources:
Change control
Super categories -> Software -> Systems and Technology Failures -> Operational Taxonomy
Changes made to the application or its configuration by a process lacking appropriate authorization, review, and rigor
External Resources:
Security settings
Super categories -> Software -> Systems and Technology Failures -> Operational Taxonomy
Improper application of security settings, either too relaxed or too restrictive, within the program or application
External Resources:
  • Application Stress Testing: Achieving Cyber Security by Testing Cyber Attacks
    Al Underbrink, Andrew Potter, Holger Jaenisch, Donald J. Reifer; Proceedings HST; 2012.
  • TitleApplication Stress Testing
    AuthorAchieving Cyber Security by Testing Cyber Attacks Al Underbrink, Andrew Potter, PhD, and Holger Jaenisch, PhD Donald J. Reifer
    Year2012
    Keywordpenetration testing; application testing; attack; software assurance; softwaer quality
    AbstractApplication stress testing applies the concept of computer network penetration testing to software applications. Since software applications may be attacked – from inside or outside a protected network boundary – they are threatened by actions and conditions which cause delays, disruptions, or failures. Stress testing exposes software systems to simulated cyber attacks, revealing potential weaknesses and vulnerabilities in their implementation. By using such testing, these internal weaknesses and vulnerabilities can be discovered earlier in the software development life cycle, corrected prior to deployment, and lead to improved software quality. Application stress testing is a process and software prototype for verifying the quality of software applications under severe operating conditions. Since stress testing is rarely – if at all – performed today, the possibility of deploying critical software systems that have been stress tested provides a much stronger indication of their ability to withstand cyber attacks. Many possible attack vectors against critical software can be verified as true threats and mitigated prior to deployment. This improves software quality and serves as a tremendous risk reduction for critical software systems used in government and commercial enterprises. The software prototype models and verifies failure conditions of a system under test (SUT). The SUT is first executed in a virtual environment and its normal operational modes are observed. A normal behavior model is generated in order to predict failure conditions based on attack models and external SUT interfaces. Using off-the-shelf software tools, the predictions are verified in the virtual environment by stressing the executing SUT with attacks against the SUT. Results are presented to testers and system developers for dispensation or mitigation.
Coding practices
Super categories -> Software -> Systems and Technology Failures -> Operational Taxonomy
Failures due to programming errors, including syntax and logic problems and failure to follow secure coding practices
External Resources:
Testing
Super categories -> Software -> Systems and Technology Failures -> Operational Taxonomy
Inadequate or atypical testing of the software application or configuration
External Resources:
  • Application Stress Testing: Achieving Cyber Security by Testing Cyber Attacks
    Al Underbrink, Andrew Potter, Holger Jaenisch, Donald J. Reifer; Proceedings HST; 2012.
  • TitleApplication Stress Testing
    AuthorAchieving Cyber Security by Testing Cyber Attacks Al Underbrink, Andrew Potter, PhD, and Holger Jaenisch, PhD Donald J. Reifer
    Year2012
    Keywordpenetration testing; application testing; attack; software assurance; softwaer quality
    AbstractApplication stress testing applies the concept of computer network penetration testing to software applications. Since software applications may be attacked – from inside or outside a protected network boundary – they are threatened by actions and conditions which cause delays, disruptions, or failures. Stress testing exposes software systems to simulated cyber attacks, revealing potential weaknesses and vulnerabilities in their implementation. By using such testing, these internal weaknesses and vulnerabilities can be discovered earlier in the software development life cycle, corrected prior to deployment, and lead to improved software quality. Application stress testing is a process and software prototype for verifying the quality of software applications under severe operating conditions. Since stress testing is rarely – if at all – performed today, the possibility of deploying critical software systems that have been stress tested provides a much stronger indication of their ability to withstand cyber attacks. Many possible attack vectors against critical software can be verified as true threats and mitigated prior to deployment. This improves software quality and serves as a tremendous risk reduction for critical software systems used in government and commercial enterprises. The software prototype models and verifies failure conditions of a system under test (SUT). The SUT is first executed in a virtual environment and its normal operational modes are observed. A normal behavior model is generated in order to predict failure conditions based on attack models and external SUT interfaces. Using off-the-shelf software tools, the predictions are verified in the virtual environment by stressing the executing SUT with attacks against the SUT. Results are presented to testers and system developers for dispensation or mitigation.
Systems
Super categories -> Systems and Technology Failures -> Operational Taxonomy
Deals with failures of integrated systems to perform as expected. Systems failures are described by the elements design, specifications, integration, and complexity
External Resources:
Design
Super categories -> Systems -> Systems and Technology Failures -> Operational Taxonomy
Improper fitness of the system for the intended application or use
External Resources:
  • Security Requirements Analysis, Specification, Prioritization and Policy Development in Cyber-Physical Systems
    Kenneth Kofi Fletcher, Xiaoqing F. Liu; Proceedings SSIRI-C; 2011.
  • TitlePrioritization and Policy Development in CyberSecurity Requirements Analysis, Specification, Physical Systems
    Author
    Year2011
    Keywordcyber-physical systems (CPS); CPS security requirements; high order object oriented modeling technique; CPS security requirements prioritization;.hardware-software interaction.
    AbstractIn recent past, the security of cyber-physical systems (CPSs) has been the subject of major concern. One of the reasons is that, CPSs are often applied to mission-critical processes. Also, the automation CPSs bring in managing physical processes, and the detail of information available to them for carrying out their tasks, make securing them a prime importance. Securing CPSs is a difficult task as systems are interconnected. In order to achieve a continuous secured CPS environment, there is the need for an integrated methodology to analyze, specify and prioritize security requirements and also to develop policies to meet them. First, CPS assets are represented using high-order object models. Second, swimlane diagrams are extended to include malactivities and prevention or mitigation options to decompose use cases. We analyze security threats pertaining to the hardware components, software components and the hardware-software interaction. Security requirements are then specified, and an analytical prioritization approach, based on relative priority analysis is employed to prioritize them. Finally, security policies are then developed to meet the requirements. To demonstrate its effectiveness and evaluate its application, the proposed methodology is applied in a structured approach to a testbed – Ayushman, a Pervasive Health Monitoring System (PHMS).
Specifications
Super categories -> Systems -> Systems and Technology Failures -> Operational Taxonomy
Improper or inadequate definition of requirements or failure to adhere to the requirements during system construction
External Resources:
  • Security Requirements Analysis, Specification, Prioritization and Policy Development in Cyber-Physical Systems
    Kenneth Kofi Fletcher, Xiaoqing F. Liu; Proceedings SSIRI-C; 2011.
  • TitlePrioritization and Policy Development in CyberSecurity Requirements Analysis, Specification, Physical Systems
    Author
    Year2011
    Keywordcyber-physical systems (CPS); CPS security requirements; high order object oriented modeling technique; CPS security requirements prioritization;.hardware-software interaction.
    AbstractIn recent past, the security of cyber-physical systems (CPSs) has been the subject of major concern. One of the reasons is that, CPSs are often applied to mission-critical processes. Also, the automation CPSs bring in managing physical processes, and the detail of information available to them for carrying out their tasks, make securing them a prime importance. Securing CPSs is a difficult task as systems are interconnected. In order to achieve a continuous secured CPS environment, there is the need for an integrated methodology to analyze, specify and prioritize security requirements and also to develop policies to meet them. First, CPS assets are represented using high-order object models. Second, swimlane diagrams are extended to include malactivities and prevention or mitigation options to decompose use cases. We analyze security threats pertaining to the hardware components, software components and the hardware-software interaction. Security requirements are then specified, and an analytical prioritization approach, based on relative priority analysis is employed to prioritize them. Finally, security policies are then developed to meet the requirements. To demonstrate its effectiveness and evaluate its application, the proposed methodology is applied in a structured approach to a testbed – Ayushman, a Pervasive Health Monitoring System (PHMS).
Integration
Super categories -> Systems -> Systems and Technology Failures -> Operational Taxonomy
Failure of various components of the system to function together or interface correctly; also includes inadequate testing of the system
External Resources:
  • Security Requirements Analysis, Specification, Prioritization and Policy Development in Cyber-Physical Systems
    Kenneth Kofi Fletcher, Xiaoqing F. Liu; Proceedings SSIRI-C; 2011.
  • TitlePrioritization and Policy Development in CyberSecurity Requirements Analysis, Specification, Physical Systems
    Author
    Year2011
    Keywordcyber-physical systems (CPS); CPS security requirements; high order object oriented modeling technique; CPS security requirements prioritization;.hardware-software interaction.
    AbstractIn recent past, the security of cyber-physical systems (CPSs) has been the subject of major concern. One of the reasons is that, CPSs are often applied to mission-critical processes. Also, the automation CPSs bring in managing physical processes, and the detail of information available to them for carrying out their tasks, make securing them a prime importance. Securing CPSs is a difficult task as systems are interconnected. In order to achieve a continuous secured CPS environment, there is the need for an integrated methodology to analyze, specify and prioritize security requirements and also to develop policies to meet them. First, CPS assets are represented using high-order object models. Second, swimlane diagrams are extended to include malactivities and prevention or mitigation options to decompose use cases. We analyze security threats pertaining to the hardware components, software components and the hardware-software interaction. Security requirements are then specified, and an analytical prioritization approach, based on relative priority analysis is employed to prioritize them. Finally, security policies are then developed to meet the requirements. To demonstrate its effectiveness and evaluate its application, the proposed methodology is applied in a structured approach to a testbed – Ayushman, a Pervasive Health Monitoring System (PHMS).
Complexity
Super categories -> Systems -> Systems and Technology Failures -> Operational Taxonomy
System intricacy or a large number or interrelationships between components
External Resources:
  • Monitoring and Management Approach for Cyber Security Events over Complex Systems
    Paul C. Hershey, Charles B. Silio Jr.; Proceedings SysCon; 2011.
  • TitleMonitoring and Management Approach for Cyber Security Events over Complex Systems
    AuthorPaul C. Hershey, Ph.D. and Charles B. Silio, Jr., Ph.D.
    Year2011
    KeywordComplex Systems, Cyber Security, Information Assurance, Enterprise Systems, Network Centric, Communications Systems, Monitoring and Response, Network Management
    AbstractDoD, agency and commercial operations centers that manage complex enterprise systems face the problem of protecting both the systems and the data they carry against cyber attacks while, at the same time, providing high quality end-to-end services that meet service level agreements and help ensure mission success. Presently there exists no comprehensive tool suite that encompasses the procedures, methods, and policies to provide an effective enterprise cyber security monitoring and management solution. This paper provides a basis from which to fill that void by introducing a new framework for monitoring and managing cyber security events in complex systems. We demonstrate application of this framework using several realistic scenarios.
Failed Internal Processes
Super categories -> Operational Taxonomy
Problems in the internal business processes that impact the ability to implement, manage, and sustain cyber security, such as process design, execution, and control. Failed internal processes particularly increase the risk of insider threats.
External Resources:
Process design or execution
Super categories -> Failed Internal Processes -> Operational Taxonomy
Deals with failures of processes to achieve their desired outcomes due to process design that is improper for the task or due to poor execution of a properly designed process
External Resources:
Process flow
Super categories -> Process design or execution -> Failed Internal Processes -> Operational Taxonomy
Poor design of the movement of process outputs to their intended consumers
External Resources:
Process documentation
Super categories -> Process design or execution -> Failed Internal Processes -> Operational Taxonomy
Inadequate documentation of the process inputs, outputs, flow, and stakeholders
External Resources:
Roles and responsibilities
Super categories -> Process design or execution -> Failed Internal Processes -> Operational Taxonomy
Insufficient definition and understanding of process stakeholder roles and responsibilities
External Resources:
Notifications and alerts
Super categories -> Process design or execution -> Failed Internal Processes -> Operational Taxonomy
Inadequate notification regarding a potential process problem or issue
External Resources:
Information flow
Super categories -> Process design or execution -> Failed Internal Processes -> Operational Taxonomy
Poor design of the movement of process information to interested parties and stakeholders
External Resources:
Escalation of issues
Super categories -> Process design or execution -> Failed Internal Processes -> Operational Taxonomy
The inadequate or nonexistent ability to escalate abnormal or unexpected conditions for action by appropriate personnel
External Resources:
Service level agreements
Super categories -> Process design or execution -> Failed Internal Processes -> Operational Taxonomy
The lack of agreement among process stakeholders on service expectations that causes a failure to complete expected actions
External Resources:
Task hand-off
Super categories -> Process design or execution -> Failed Internal Processes -> Operational Taxonomy
“Dropping the ball” due to the inefficient handing off of a task in progress from one responsible party to another
External Resources:
Process controls
Super categories -> Failed Internal Processes -> Operational Taxonomy
Addresses process failures due to inadequate controls on the operation of the process.
External Resources:
Status monitoring
Super categories -> Process controls -> Failed Internal Processes -> Operational Taxonomy
Failure to review and respond to routine information about the operation of a process
External Resources:
Metrics
Super categories -> Process controls -> Failed Internal Processes -> Operational Taxonomy
Failure to review process measurements over time for the purpose of determining performance trends
External Resources:
Periodic review
Super categories -> Process controls -> Failed Internal Processes -> Operational Taxonomy
Failure to review the end-to-end operation of the process on a periodic basis and make any needed changes
External Resources:
Process ownership
Super categories -> Process controls -> Failed Internal Processes -> Operational Taxonomy
Failure of a process to deliver the expected outcome because of poor definition of its ownership or poor governance practices
External Resources:
Supporting processes
Super categories -> Failed Internal Processes -> Operational Taxonomy
Deals with operational risks introduced due to failure of organizational supporting processes to deliver the appropriate resources
External Resources:
Staffing
Super categories -> Supporting processes -> Failed Internal Processes -> Operational Taxonomy
Failure to provide appropriate human resources to support its operations
External Resources:
Funding
Super categories -> Supporting processes -> Failed Internal Processes -> Operational Taxonomy
Failure to provide appropriate financial resources to support its operations
External Resources:
Training and development
Super categories -> Supporting processes -> Failed Internal Processes -> Operational Taxonomy
Failure to maintain the appropriate skills within the workforce
External Resources:
Procurement
Super categories -> Supporting processes -> Failed Internal Processes -> Operational Taxonomy
Failure to provide the proper purchased service and goods necessary to support operations
External Resources:
External Events
Super categories -> Operational Taxonomy
Issues often outside the control of the organization, such as disasters, legal issues, business issues, and service provider dependencies
External Resources:
Disasters
Super categories -> External Events -> Operational Taxonomy
Deals with risks owing to events, both natural and of human origin, over which the organization has no control and that can occur without notice
External Resources:
Weather event
Super categories -> Disasters -> External Events -> Operational Taxonomy
Adverse weather situations such as rain, snow, tornado, or hurricane
External Resources:
Fire
Super categories -> Disasters -> External Events -> Operational Taxonomy
Fire within a facility or disruption caused by a fire external to a facility
External Resources:
Flood
Super categories -> Disasters -> External Events -> Operational Taxonomy
Flooding within a facility or disruption caused by a flood external to a facility
External Resources:
Earthquake
Super categories -> Disasters -> External Events -> Operational Taxonomy
Disruption of organizational operations due to an earthquake
External Resources:
Unrest
Super categories -> Disasters -> External Events -> Operational Taxonomy
Disruption of operations due to civil disorder, riot, or terrorist acts
External Resources:
Pandemic
Super categories -> Disasters -> External Events -> Operational Taxonomy
Widespread medical conditions that disrupt organizational operations
External Resources:
Legal issues
Super categories -> External Events -> Operational Taxonomy
Deals with risks potentially impacting the organization due to the elements regulatory compliance, legislation, and litigation
External Resources:
Regulatory compliance
Super categories -> Legal issues -> External Events -> Operational Taxonomy
New governmental regulation or failure to comply with existing regulation
External Resources:
Legislation
Super categories -> Legal issues -> External Events -> Operational Taxonomy
New legislation that impacts the organization
External Resources:
Litigation
Super categories -> Legal issues -> External Events -> Operational Taxonomy
Legal action taken against the organization by any stakeholder, including employees and customers
External Resources:
Business issues
Super categories -> External Events -> Operational Taxonomy
Described by the elements of supplier failure, market conditions, and economic conditions, deals with operational risks arising from changes in the business environment of the organization
External Resources:
Supplier failure
Super categories -> Business issues -> External Events -> Operational Taxonomy
The temporary or permanent inability of a supplier to deliver needed products or services to the organization
External Resources:
Market conditions
Super categories -> Business issues -> External Events -> Operational Taxonomy
The diminished ability of the organization to sell its products and services in the market
External Resources:
Economic conditions
Super categories -> Business issues -> External Events -> Operational Taxonomy
The inability of the organization to obtain needed funding for its operations
External Resources:
Service dependencies
Super categories -> External Events -> Operational Taxonomy
Deals with risks arising from the organization's dependence on external parties to continue operations. The subclass is associated with the elements of utilities, emergency services, fuel, and transportation
External Resources:
Utilities
Super categories -> Service dependencies -> External Events -> Operational Taxonomy
Failure of the organization’s electric power supply, water supply, or telecommunications services
External Resources:
Emergency services
Super categories -> Service dependencies -> External Events -> Operational Taxonomy
Dependencies on public response services such as fire, police, and emergency medical services
External Resources:
Fuel
Super categories -> Service dependencies -> External Events -> Operational Taxonomy
Failure of external fuel supplies, for example to power a backup generator
External Resources:
Transportation
Super categories -> Service dependencies -> External Events -> Operational Taxonomy
Failures in external transportation systems, for example, inability of employees to report to work and inability to make and receive deliveries
External Resources: