Extend a Theory in Cloud Computing: Protection Motivation Theory and Customer-Side Misconfiguration
Extend a Theory in Cybersecurity and Cloud Computing: Protection Motivation Theory and Cloud Misconfiguration (GRC Proposal)
Review a single practical topic requiring improvement in cloud computing practice based on an existing theory or limited adjustment to a theory, using peer-reviewed articles and dissertations from the last five years, and formulate an improvement strategy based on cybersecurity governance, policy, risk and compliance concepts. Include:
- A narrow problem within cloud computing and a related theory that can be made useful or improved.
- The cloud computing issues involved, matched to the potential practical contribution of an existing theory.
- The proposed adjustments and how one could confirm whether they (a) could contribute to improvement and (b) could be tested for value.
Length: 11 pages excluding title page and references; course sources plus two additional scholarly articles from the NU library.
Customer-side misconfiguration
Protection Motivation Theory
Responsibility clarity
Automation efficacy
Survey, SEM, field quasi-experiment
Download the APA paper (.docx)
Model paper
Original example for study purposes (about 2,580 words). About 2,600 words (roughly 11 pages double-spaced). Duzenci et al. (2023) and Alshammari et al. (2024) serve as the two recent peer-reviewed sources; confirm access through the NU library and add your course readings.
Introduction
Cloud computing has shifted where security failures occur. Public cloud providers secure the physical infrastructure, hypervisors and core services, but customers remain responsible for how they configure identities, storage, networks and workloads. Industry analysts predicted that through 2025, 99% of cloud security failures would be the customer’s fault, primarily through misconfiguration (Gartner, 2019). Misconfigured storage buckets, overly permissive identity policies and exposed management interfaces continue to cause data breaches despite mature provider security. This is a practical problem rooted less in technology than in human and organizational behavior: engineers know that secure configuration matters, yet insecure settings persist.
This paper proposes a limited extension of Protection Motivation Theory (PMT), one of the most widely used theories in information security behavior research, to explain and reduce customer-side cloud misconfiguration. The proposal places the problem in the context of an organization’s governance, risk management, policy and compliance (GRC) program. It identifies the narrow problem, explains how PMT can contribute, details two proposed adjustments to the theory and describes how the adjustments could be evaluated and tested. [Integrate required course readings throughout and confirm that all sources are available through the NU library.]
The Narrow Problem: Customer-Side Misconfiguration Under the Shared Responsibility Model
The National Institute of Standards and Technology (NIST) defines cloud computing by its essential characteristics, including on-demand self-service and rapid elasticity, and by its service models, infrastructure, platform and software as a service (Mell & Grance, 2011). These characteristics are what make the cloud valuable, but they also allow any engineer with appropriate permissions to create and change resources in seconds. Under the shared responsibility model, the division of security duties between provider and customer varies by service model: in infrastructure as a service, customers manage operating systems, network rules, identities and data protection, while in software as a service, they still manage identities, access and data. When responsibilities are unclear, configuration tasks fall into gaps between teams.
The narrow problem this paper addresses is persistent customer-side misconfiguration of identity and storage controls in infrastructure-as-a-service environments, caused by engineers’ and teams’ failure to adopt available protective practices. Organizations typically have policies requiring encryption, least privilege and private storage, and cloud providers offer tools to enforce them. The gap is between policy and practice. Understanding why practitioners do or do not take protective actions requires a behavioral theory, and PMT is a natural candidate.
The Existing Theory: Protection Motivation Theory
Rogers (1975) developed PMT to explain how fear appeals influence health behavior. The revised theory proposes that protection motivation results from two cognitive processes (Maddux & Rogers, 1983). In threat appraisal, people assess the perceived severity of a threat and their perceived vulnerability to it, weighed against the rewards of maladaptive behavior. In coping appraisal, they assess response efficacy (whether the recommended action works), self-efficacy (whether they can perform it) and response costs (the effort, time or money required). High threat appraisal and high coping appraisal together produce protection motivation, which predicts protective behavior.
Information systems researchers have applied PMT extensively to security policy compliance. Herath and Rao (2009) combined PMT with deterrence and organizational factors and found that employees’ security policy compliance intentions were shaped by threat perceptions, response efficacy, self-efficacy and organizational commitment. Boss et al. (2015) showed that fear appeals that included the full PMT nomology, including fear, more effectively motivated protective security behaviors. More recent work continues to refine the theory. In a survey of 668 public- and private-sector employees, Duzenci et al. (2023) found that perceived severity, perceived vulnerability, self-efficacy, response efficacy and security awareness were positively related to cybersecurity compliance behavior, while the influence of several PMT factors varied by decision-making style. Alshammari et al. (2024) proposed integrating PMT with Broaden-and-Build Theory, arguing that employees’ positive and negative emotions shape protection motivation through self-efficacy, with cybersecurity awareness as a moderator.
Matching the Theory to the Cloud Problem
PMT offers a practical contribution to the misconfiguration problem because each of its constructs maps to a recognizable barrier in cloud engineering practice:
- Perceived severity: engineers may underestimate the consequences of a misconfigured resource, especially in development or test environments that later hold real data.
- Perceived vulnerability: teams may assume the provider’s security protects them, underestimating their own exposure.
- Response efficacy: practitioners may doubt that configuration controls, such as private endpoints or least-privilege roles, actually prevent breaches.
- Self-efficacy: the complexity of identity policies and the frequent release of new services make engineers less confident they can configure services securely.
- Response costs: secure configuration takes time and may slow delivery, especially under pressure to release features.
However, PMT was developed for individuals making personal protective decisions, and most research applies it to end users complying with general security policies, such as password or email rules. Cloud configuration differs in two important ways. First, responsibility is distributed among the provider and multiple internal teams, so individuals may not believe the threat is theirs to manage. Second, protection increasingly depends on automation, such as infrastructure as code, policy as code and cloud security posture management tools, rather than on individual manual actions. Standard PMT does not capture either feature. These gaps justify a limited adjustment rather than a new theory.
Proposed Adjustments to the Theory
Adjustment 1: Responsibility Clarity as an Antecedent of Threat Appraisal
The first adjustment adds responsibility clarity, defined as the degree to which practitioners accurately understand which security controls are their responsibility under the shared responsibility model and their organization’s internal division of duties. The proposition is that responsibility clarity strengthens perceived vulnerability, because people only feel vulnerable to threats they believe they must manage. A developer who believes the provider secures storage by default will perceive little vulnerability, regardless of the actual risk. Responsibility clarity therefore acts as an antecedent of threat appraisal and as a moderator that strengthens the relationship between threat appraisal and protection motivation.
This construct connects directly to governance. The NIST Cybersecurity Framework 2.0 added Govern as a core function, which includes establishing and communicating cybersecurity roles, responsibilities and authorities and managing supply chain risk, including risk from technology providers (National Institute of Standards and Technology [NIST], 2024). Responsibility clarity is the behavioral outcome that effective governance should produce. In GRC terms, organizations can increase it through a documented responsibility matrix, such as a RACI chart, that maps each cloud control to accountable teams, and by aligning that matrix with control frameworks such as the Cloud Security Alliance’s Cloud Controls Matrix.
Adjustment 2: Automation Efficacy as a Component of Coping Appraisal
The second adjustment adds automation efficacy, defined as the perceived ability of organizational tools and automated guardrails to reliably apply and maintain secure configurations. In traditional PMT, coping appraisal focuses on the individual’s ability to perform a response. In cloud engineering, the most effective responses are often embedded in pipelines: templates that deploy secure defaults, policies that block noncompliant resources and posture management tools that detect drift. The proposition is that automation efficacy increases protection motivation by raising response efficacy and lowering response costs, because secure behavior becomes the easiest path rather than extra work. It may also partially substitute for individual self-efficacy, which is especially valuable given the complexity of cloud services.
This construct connects to risk management and compliance. Policy-as-code converts written policies into enforceable rules, providing continuous compliance evidence and reducing reliance on periodic audits. It also supports zero trust principles, which require dynamic, policy-based access decisions and continuous monitoring of resource posture (Rose et al., 2020).
The Extended Model
The resulting model, which can be called Cloud Protection Motivation Theory, retains PMT’s core relationships and adds two constructs and four testable propositions:
- P1: Responsibility clarity is positively associated with perceived vulnerability.
- P2: Responsibility clarity strengthens the positive relationship between threat appraisal and protection motivation.
- P3: Automation efficacy is positively associated with response efficacy and negatively associated with perceived response costs.
- P4: Protection motivation is positively associated with secure configuration behavior, measured by objective misconfiguration rates.
Strategic and GRC Context
The adjustments matter because they translate into organizational strategy. At the governance level, leadership must assign and communicate cloud security responsibilities and fund the tools that enable automation. At the risk level, misconfiguration should appear in the enterprise risk register with defined risk owners, appetite and metrics. At the policy level, cloud security standards should specify secure baselines for each service and require infrastructure-as-code deployment for production resources. At the compliance level, posture management tools can continuously evaluate configurations against frameworks such as the NIST CSF 2.0 and generate audit evidence. The extended theory explains why these interventions should work: governance builds responsibility clarity, and automation builds automation efficacy, both of which strengthen protection motivation.
Why PMT Rather Than Alternative Theories
Several other theories could be applied to cloud misconfiguration, and comparing them clarifies why PMT is the most useful starting point. General deterrence theory holds that the certainty and severity of sanctions discourage undesirable behavior. Deterrence explains intentional policy violations, but most misconfigurations are unintentional; engineers rarely choose insecure settings to break rules. Herath and Rao (2009) found that deterrence factors added explanatory power to PMT for policy compliance, but they did not replace threat and coping appraisals. The theory of planned behavior emphasizes attitudes, subjective norms and perceived behavioral control. It captures social influences well, and perceived behavioral control overlaps with self-efficacy, but it does not explicitly model threat perceptions, which are central to security decisions. Organizational adoption frameworks, such as the technology-organization-environment framework, explain whether organizations adopt cloud or security technologies but not why individual practitioners use those technologies securely once adopted.
PMT combines the threat perception that security requires with the coping perceptions that determine whether people act, and it has a large body of validated measures in information systems research (Boss et al., 2015). Its limitation, an individual focus that does not reflect shared responsibility and automation, is precisely what the proposed adjustments address. Extending a well-established theory is also more efficient than building a new one, because researchers can reuse validated instruments and compare results with prior studies.
Illustrative Application in an Organization
Consider a mid-sized financial services firm that runs customer applications on a public cloud. Its security policy requires that storage containing customer data be private and encrypted, and that administrative roles follow least privilege. Nevertheless, its posture management tool reports dozens of high-severity findings each month, most involving publicly accessible storage in development accounts and identity roles with broad wildcard permissions. Interviews reveal two patterns. Developers believe the cloud provider “handles security,” and they are unsure whether development accounts are covered by the policy, indicating low responsibility clarity. They also report that secure configurations require manual steps that slow releases, and that existing templates are outdated, indicating low automation efficacy and high response costs.
Guided by the extended model, the firm’s GRC program would take targeted actions. Governance leaders would publish a shared responsibility matrix covering every account type and assign named owners for each control. The risk team would add misconfiguration to the risk register with metrics reported to leadership. The cloud platform team would update infrastructure-as-code templates with secure defaults and implement policy-as-code rules that block public storage and wildcard permissions in all accounts, with an exception process for justified cases. The compliance team would use continuous posture data as audit evidence. The model predicts that these changes would raise perceived vulnerability and response efficacy and lower response costs, increasing protection motivation and reducing misconfigurations. Measuring both the constructs and the objective findings would show whether the predicted mechanism, not just the outcome, occurred.
Confirming Whether the Adjustments Could Contribute to Improvement
Before investing in empirical testing, the proposal should be evaluated for conceptual contribution. Three criteria apply. First, theoretical consistency: the new constructs should fit PMT’s logic. Responsibility clarity extends threat appraisal by specifying when threats are personally relevant, and automation efficacy extends coping appraisal to organizational resources, consistent with prior work that combined PMT with organizational factors (Herath & Rao, 2009). Second, practical relevance: interviews or focus groups with cloud engineers, security architects and compliance managers can confirm whether responsibility confusion and tool support are perceived as real drivers of misconfiguration. Third, expert review: a panel of practitioners and academics can review construct definitions and measurement items for content validity, for example using a content validity index.
Testing Whether the Proposal Is Valuable
Phase 1: Instrument Development
Existing validated PMT scales for perceived severity, vulnerability, response efficacy, self-efficacy and response cost would be adapted to the cloud context. New items would be developed for responsibility clarity, such as “I know which configuration settings for our cloud storage are my team’s responsibility,” and automation efficacy, such as “Our deployment pipeline reliably prevents insecure configurations.” A pilot study would test reliability using Cronbach’s alpha and composite reliability.
Phase 2: Cross-Sectional Survey and Structural Equation Modeling
A survey of cloud practitioners across several organizations would measure the constructs, and the extended model would be tested with structural equation modeling, such as partial least squares SEM. To reduce common method bias and the limitations of self-report noted in prior PMT research (Duzenci et al., 2023), behavioral outcomes would be linked, with organizational permission and anonymization, to objective data: the number of high-severity misconfiguration findings per team reported by cloud security posture management tools. The analysis would compare the extended model with standard PMT to determine whether the new constructs explain significantly more variance in protection motivation and behavior.
Phase 3: Field Quasi-Experiment
To test causal value, a quasi-experiment could compare teams within an organization. Intervention teams would receive a responsibility matrix and training to increase responsibility clarity and policy-as-code guardrails to increase automation efficacy; comparison teams would continue with existing practices. Misconfiguration rates would be measured before and after implementation, ideally using an interrupted time series or difference-in-differences design. A meaningful reduction in high-severity findings in intervention teams, accompanied by increases in the two constructs, would support the practical value of the extended theory.
Ethical and Practical Considerations
Research involving employees requires institutional review board approval, informed consent and protections against using results for individual performance evaluation. Configuration data must be anonymized and stored securely, and organizations must agree on what data can be shared. Results should be reported in aggregate to protect both participants and the security of participating organizations.
Limitations and Future Research
The extended model focuses on identity and storage misconfiguration in infrastructure as a service and may not generalize to other cloud risks, such as supply chain compromise. Organizational culture, team structure and regulatory environment may moderate the relationships, and future research could examine these factors. Emotional influences on protection motivation, as proposed by Alshammari et al. (2024), and decision-making styles, as studied by Duzenci et al. (2023), could also be integrated to explain individual differences within teams.
Conclusion
Customer-side misconfiguration remains one of the most significant risks in cloud computing, and it persists because of human and organizational behavior rather than technical limitations. Protection Motivation Theory explains much of this behavior, but it does not account for the shared responsibility model or the role of automation. Adding responsibility clarity and automation efficacy creates a limited, testable extension that links behavioral theory to governance, risk management, policy and compliance. If confirmed through instrument development, structural equation modeling and field experimentation, the extended theory would give organizations a clear rationale for investing in responsibility mapping and policy-as-code, and it would give researchers a more accurate model of security behavior in cloud environments.
References
Alshammari, A., Benson, V., & Batista, L. (2024). The influences of employees’ emotions on their cyber security protection motivation behaviour: A theoretical framework. In Proceedings of the 26th International Conference on Enterprise Information Systems (ICEIS 2024) (Vol. 2, pp. 524–531). SCITEPRESS. https://doi.org/10.5220/0012681600003690
Boss, S. R., Galletta, D. F., Lowry, P. B., Moody, G. D., & Polak, P. (2015). What do systems users have to fear? Using fear appeals to engender threats and fear that motivate protective security behaviors. MIS Quarterly, 39(4), 837–864. https://doi.org/10.25300/MISQ/2015/39.4.5
Duzenci, A., Kitapci, H., & Gok, M. S. (2023). The role of decision-making styles in shaping cybersecurity compliance behavior. Applied Sciences, 13(15), Article 8731. https://doi.org/10.3390/app13158731
Gartner. (2019, October 10). Is the cloud secure? https://www.gartner.com/smarterwithgartner/is-the-cloud-secure
Herath, T., & Rao, H. R. (2009). Protection motivation and deterrence: A framework for security policy compliance in organisations. European Journal of Information Systems, 18(2), 106–125. https://doi.org/10.1057/ejis.2009.6
Maddux, J. E., & Rogers, R. W. (1983). Protection motivation and self-efficacy: A revised theory of fear appeals and attitude change. Journal of Experimental Social Psychology, 19(5), 469–479. https://doi.org/10.1016/0022-1031(83)90023-9
Mell, P., & Grance, T. (2011). The NIST definition of cloud computing (NIST Special Publication 800-145). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-145
National Institute of Standards and Technology. (2024). The NIST cybersecurity framework (CSF) 2.0 (NIST CSWP 29). https://doi.org/10.6028/NIST.CSWP.29
Rogers, R. W. (1975). A protection motivation theory of fear appeals and attitude change. The Journal of Psychology, 91(1), 93–114. https://doi.org/10.1080/00223980.1975.9915803
Rose, S., Borchert, O., Mitchell, S., & Connelly, S. (2020). Zero trust architecture (NIST Special Publication 800-207). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-207
Tip: keep the problem narrow: one type of misconfiguration in one service model makes the theory extension and the test design far more convincing.
Frequently asked questions
What is Protection Motivation Theory?
A theory proposing that protective behavior depends on threat appraisal (severity and vulnerability) and coping appraisal (response efficacy, self-efficacy and response costs).
How is this connected to GRC?
Governance builds responsibility clarity, risk management tracks misconfiguration, policy defines secure baselines and compliance uses automated evidence.
More model assignments posted today
- CS Enterprises cloud board presentation
- Argument flaws critique
- PADM 710 AI in the public sector paper
- Site plan vision statement
- Sensitivity analysis training slides
- Michael Phelps exercise motivation case