DOCSLIB.ORG

Cloud Specific Issues and Vulnerabilities Solutions Author 4: B.Suresh Kumar (M.Tech), Author 1: C.Kishor Kumar Reddy (M.Tech), Dept

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cloud Specific Issues and Vulnerabilities Solutions Author 4: B.Suresh Kumar (M.Tech), Author 1: C.Kishor Kumar Reddy (M.Tech), Dept International Journal of Scientific & Engineering Research Volume 3, Issue 7, July-2012 1 ISSN 2229-5518 Cloud Specific Issues and Vulnerabilities solutions Author 4: B.Suresh Kumar (M.Tech), Author 1: C.Kishor Kumar Reddy (M.Tech), Dept. of C.S.E, VCE, Dept. of C.S.E, VCE, Samshabad, R.R (Dist), A.P, India. Samshabad, R.R (Dist), A.P, India. [email protected], [email protected], Ph: +91 9533444094. Ph: +91 9493024236. Author 2: SK. Lokesh Naik (Assistant Professor), Dept. of C.S.E, VCE, Samshabad, R.R (Dist), A.P, India. [email protected], Ph: +91 9885601370 Abstract: The current discourse about cloud computing security issues makes a well-founded assessment of cloud computing's security impact difficult for two primary reasons. First, as is true for many discussions about risk, basic vocabulary such as "risk," "threat," and "vulnerability" are often used as if they were interchangeable, without regard to their respective definitions. Second, not every issue that's raised is really specific to cloud computing. We can achieve an accurate understanding of the security issue "delta" that cloud computing really adds by analyzing how cloud computing influences each risk factor. One important factor concerns vulnerabilities: cloud computing makes certain well-understood vulnerabilities more significant and adds new vulnerabilities. Here, we define four Figure 1: Factors contributing to risk according to the indicators of cloud-specific vulnerabilities, introduce security- open Group’s risk taxonomy. specific cloud reference architecture, and provide examples of cloud- specific vulnerabilities for each architectural component. This paper This second factor brings us toward a useful definition of highlights and categorizes many of security issues introduced by the vulnerability. "cloud"; surveys the risks, threats and vulnerabilities, and makes the Defining Vulnerability: necessary recommendations that can help promote the benefits and According to the Open Group’s risk taxonomy, mitigate the risks associated with Cloud Computing. Vulnerability is the probability that an asset will be unable to resist the actions of a threat agent. Vulnerability exists when Index-Terms: cloud-specific vulnerabilities, risk, threat, delta. there is a difference between the force being applied by the threat agent, and an object’s ability to resist that force. So, Vulnerability: An Overview vulnerability must always be described in terms of resistance Vulnerability is a prominent factor of risk ISO 27005 defines to a certain type of attack. risk as ―the potential that a given threat will exploit Vulnerabilities and Cloud Risk Vulnerability of an asset or group of assets and thereby cause We’ll now examine how cloud computing influences harm to the organization,‖ measuring it in terms of both the the risk factors in Figure 1, starting with the right-hand side of likelihood of an event and its con- sequence. The Open Group’s the risk factor tree. From a cloud customer perspective, the risk taxonomy offers a useful overview of risk factors (see Figure right-hand side dealing with probable magnitude of future loss 1). isn’t changed at all by cloud computing: the consequences and • The frequency with which threat agents try to exploit ultimate cost of, say, a confidentiality breach, is exactly the vulnerability. This frequency is determined by both the agents’ same regardless of whether the data breach occurred within a motivation (What can they gain with an attack? How much cloud or a conventional IT infrastructure. For a cloud service effort does it take? What is the risk for the attackers?) and how provider, things look somewhat different: because cloud com- much access (―contact‖) the agents have to the attack targets. puting systems were previously separated on the same • The difference between the threat agents’ attack infrastructure, a loss event could entail a considerably larger capabilities and the system’s strength to resist the attack impact. But this fact is easily grasped and incorporated into a risk assessment: no conceptual work for adapting impact analysis to cloud computing seems necessary. So, we must Author 3:S.K.Prasanth (Associate Professor), search for changes on Figure 1’s left-hand side—the loss event Dept. of C.S.E, VCE, frequency. Cloud computing could change the probability of a Samshabad, R.R (Dist), A.P, India. harmful event’s occurrence. As we show later, cloud [email protected], computing causes significant changes in the vulnerability Ph: +91 9908965812. factor. Of course, moving to a cloud infrastructure might IJSER © 2012 http://www.ijser.org International Journal of Scientific & Engineering Research Volume 3, Issue 7, July-2012 2 ISSN 2229-5518 change the attackers’ access level and motivation, as well as Using the cloud reference architecture’s structure, we can now the effort and risk—a fact that must be considered as future run through the architecture’s components and give examples work. But, for supporting a cloud-specific risk assessment, it of each component’s cloud-specific vulnerabilities. seems most profitable to start by examining the exact nature of CloudSoftwareInfrastructure and Environment: cloud-specific vulnerabilities. The cloud software infrastructure layer provides an Architectural Components of could computing abstraction level for basic IT resources that are offered as ser- vices to higher layers: computational resources (usually VMEs), storage, and (network) communication. These services can be used individually, as is typically the case with storage services, but they’re often bundled such that servers are delivered with certain network connectivity and (often) access to storage. This bundle, with or without storage, is usually referred to as IaaS. Computational Resources: A highly relevant set of computational resource vulnerabilities concerns how virtual machine images are han- dled: the only feasible way of providing nearly identical server images—thus providing on-demand service for virtual servers—is by cloning template images. Because cryptography is frequently used to overcome storage-related vulnerabilities, this core technology’s vulnerabilities—insecure or obsolete cryptography and poor key management—play a special role for cloud storage. Communication: The most prominent example of a cloud communi- cations service is the networking provided for VMEs in an IaaS environment. Because of resource pooling, several Figure 2: The cloud reference architecture. customers are likely to share certain network infrastructure components: vulnerabilities of shared network infrastructure Architectural Components and Vulnerabilities: components, such as vulnerabilities in a DNS server, Cloud service models are commonly divided into Dynamic Host Configuration Protocol, and IP protocol SaaS, PaaS, and IaaS, and each model influences the vulner- vulnerabilities, might enable network-based cross-tenant abilities exhibited by a given cloud infrastructure. It’s helpful attacks in an IaaS infrastructure. to add more structure to the service model stacks: Figure 2 Cloud Web Applications: shows a cloud reference architecture that makes the most A Web application uses browser technology as the important security-relevant cloud components explicit and front end for user interaction. With the increased uptake of provides an abstract overview of cloud computing for security browser-based computing technologies such as JavaScript, issue analysis. Java, Flash, and Silverlight, a Web cloud application falls into In addition to the original model, we’ve identified two parts: supporting functions relevant to services in several layers and • An application component operated somewhere in the cloud, added them to the model as vertical spans over several and horizontal layers. • A browser component running within the user’s browser. Our cloud reference architecture has three main parts: Identity, Authentication, Authorization, and Supporting (IT) infrastructure. These are facilities and Auditing Mechanisms: services common to any IT service, cloud or otherwise. We Most vulnerability associated with the IAAA include them in the architecture because we want to provide component must be regarded as cloud-specific because they’re the complete picture; a full treatment of IT security must prevalent in state-of-the-art cloud offerings. Earlier, we gave account for a cloud service’s non-cloud-specific components. the example of weak user authentication mechanisms; other Cloud-specific infrastructure. These components constitute examples include the heart of a cloud service; cloud-specific vulnerabilities and • Denial of service by account lockout. One often-used corresponding controls are typically mapped to these security control—especially for authentication with username components. and password—is to lock out accounts that have received Cloud service consumer. Again, we include the cloud service several unsuccessful authentication attempts in quick customer in the reference architecture because it’s relevant to succession. Attackers can use such attempts to launch DoS an all-encompassing security treatment. attacks against a user. • Weak credential-reset mechanisms. When cloud computing providers manage user credentials themselves rather than IJSER © 2012 http://www.ijser.org International Journal of Scientific & Engineering Research Volume 3, Issue 7, July-2012 3 ISSN 2229-5518 using federated authentication, they must provide a these service models. In the future, we expect virtualization to mechanism
Load more

Recommended publications
  • Seven Steps to a Forever Safe Cipher
    International Journal on Advances in Security, vol 11 no 1 & 2, year 2018, http://www.iariajournals.org/security/ 91 RMDM – Further Verification of the Conceptual ICT Risk-Meta-Data-Model Verified with the underlying Risk Models of COBIT for Risk and COSO ERM 2017 Martin Latzenhofer 1 2 Gerald Quirchmayr 2 1 Center for Digital Safety & Security 2 Multimedia Information Systems Research Group Austrian Institute of Technology Faculty of Computer Science, University of Vienna Vienna, Austria Vienna, Austria email: [email protected] email: [email protected] Abstract— The aim of this article is to introduce an approach to initialize and re-establish the risk management that integrates the different models and methods currently frameworks and related processes each time. It is evident that applied for risk management in information and these parameters result in a smaller degree of reusability of a communication technologies (ICT). These different risk given risk management process and less comparability of the management approaches are usually bound to the organization information obtained from it. where they are applied, thus staying quite specific for a given When interpreting this problem as a pure ICT issue, an setting. Consequently, there is no possibility to compare or explicit ICT solution is required. This leads to the main reuse risk management structures because they are individual research question of this paper, i.e., whether it is possible to solutions. In order to establish a common basis for working develop a common risk management model, which is with different underlying risk models, a metamodeling approach from the area of disaster recovery is used.
    [Show full text]
  • Redefining & Strengthening IT Governance Through Three Lines Of
    Redefining & Strengthening IT Governance through Three Lines of Defense Presented by Ronke Oyemade, CISA, CRISC, PMP CEO, Principal Consultant, Strategic Global Consulting L.L.C Introduction • Brief Introduction of the Presenter. • Session Presentation: ‘Redefining & Strengthening IT Governance through Three Lines of Defense” This session takes a different and practical approach to strengthening IT Governance by applying the three lines of defense model. This approach adopts the use of Risk IT and Cobit as frameworks through which the three lines of defense model is implemented. The session gives an overview of the three lines of defense model, Risk IT and Cobit frameworks and provides practical application of them to the IT environment of a fictitious enterprise. • Benefits obtained from this session. Agenda 1. Use of IT and IT Risk 2. IT Governance: Overview and Importance 3. Overview of Three Lines of Defense, Risk IT and Cobit Framework 4. Three Lines of Defense Model 5. What is the relationship between Risk IT Framework and Cobit Framework 6. How do the Risk IT Framework and Cobit fit into the Three Lines of Defense Model 7. First Line of Defense 8. Second Line of Defense 9. Three Line of Defense Use of IT and IT risk • What is the importance of IT? • Why is IT Risk? What is IT risk? • IT risk is business risk and a component of overall risk universe of the enterprise. • IT-related risk is a component of other business risks IT risk as Business Risk Enterprise Risk StrategicStrategic RiskRisk EnvironmentalEnvironmental MarketMarket
    [Show full text]
  • IS.010-Sdr-Information Security Risk Management
    Commonwealth of Massachusetts Executive Office of Technology Services and Security (EOTSS) Enterprise Security Office Information Security Risk Management Standard Document Name: Information Security Risk Effective Date: October 15th, 2018 Management Last Revised Date: July 15th, 2020 Document ID: IS.010 Table of contents 1. Purpose ..................................................................................................................... 2 2. Authority .................................................................................................................... 2 3. Scope ........................................................................................................................ 2 4. Responsibility ............................................................................................................ 2 5. Compliance ................................................................................................................ 2 6. Standard Statements ................................................................................................. 3 6.1. Information Security Risk Management .............................................................. 3 6.2 Information Security Training and Awareness .................................................... 8 7. Control Mapping ........................................................................................................ 9 8. Document Change Control ........................................................................................ 9 Information
    [Show full text]
  • Cyber Risk in Advanced Manufacturing Cyber Risk in Advanced Manufacturing
    Cyber risk in advanced manufacturing Cyber risk in advanced manufacturing 1 2 3 4 5 6 7 8 9 10 11 Contents 1 Executive summary 3 2 Executive and board-level engagement 14 3 Talent and human capital 22 4 Protecting intellectual property 30 5 Inherent risks in industrial control systems 34 6 Implications of rapidly evolving connected products 40 7 Cyber risk in the industrial ecosystem 44 8 The changing nature of the cyberthreat landscape 46 9 Conclusion 50 10 Endnotes 51 11 Authors and acknowledgements 52 2 Cyber risk in advanced manufacturing Executive summary 1 2 3 4 5 6 7 8 9 10 11 Technologies utilized to drive the business are likely • Emerging risks likely to materialize as a result of rapid Manufacturers drive to include complex global networks, a myriad of back technology change office business applications, generations of different • An assessment of leading strategies manufacturers are extensive innovation in industrial control systems (ICS) controlling high-risk employing to address these types of cyber risks products, manufacturing manufacturing processes, and a variety of technologies directly embedded into current and emerging products. To that end, Deloitte and MAPI launched the Cyber Risk process, and industrial Further, manufacturers continue to drive extensive in Advanced Manufacturing study to assess these trends. innovation in products, manufacturing process, and We conducted more than 35 live executive and industry ecosystem relationships industrial ecosystem relationships in order to compete organization interviews, and in collaboration with Forbes in a changing global marketplace.1 As a result, the Insights, we collected 225 responses to an online survey in order to compete manufacturing industry is likely to see an acceleration in exploring cyber risk in advanced manufacturing trends.
    [Show full text]
  • The Anatomy of Cyber Risk*
    The Anatomy of Cyber Risk* Rustam Jamilov Hélène Rey Ahmed Tahoun London Business School London Business School London Business School September 2020 PRELIMINARY AND INCOMPLETE. Abstract Despite continuous interest from both industry participants and policy makers, empirical research on the economics of cyber security is still lacking. This paper fills the gap by constructing comprehensive text-based measures of firm-level exposure to cyber risk by leveraging machine learning tools developed in Hassan et al.(2019). Our indices capture such textual bigrams as "cyber attack", "ransomware", and "data loss", span 20 years of data, and are available for over 80 counties. We validate our measures by cross-referencing with well-known reported cyber incidents such as the Equifax data breach and the “NotPetya” global ransomware attack. We begin by document- ing a steady and significant rise in aggregate cyber risk exposure and uncertainty across the Globe, with a noticeable deterioration in sentiment. The fraction of most- affected firms is gradually shifting from the US towards Europe and the UK. From virtually zero exposure, the financial sector has grown to become one of the most af- fected sectors in under ten years. We continue by studying asset pricing implications of firm-level cyber risk. First, in windows surrounding conference call announce- ments, we find direct effects of cyber risk exposure on stock returns. Furthermore, we also find significant within-country-industry-week peer effects on non-affected firms. Second, we document strong factor structure in our firm-level measures of exposure and sentiment and show that shocks to the common factors in cyber risk exposure (CyberE) and sentiment (CyberS) are priced with an opposite sign.
    [Show full text]
  • Managing Cybersecurity Risk in Government: an Implementation Model
    IBM Center for The Business of Government Managing Cybersecurity Risk in Government: An Implementation Model Rajni Goel James Haddow Anupam Kumar Howard University Howard University Howard University Managing Cybersecurity Risk in Government: An Implementation Model Rajni Goel Howard University James Haddow Howard University Anupam Kumar Howard University MANAGING CYBERSECURITY RISK IN GOVERNMENT: AN IMPLEMENTATION MODEL www.businessofgovernment.org TABLE OF CONTENTS Foreword . 4 Introduction . 5 Enterprise and Cybersecurity Risk Management . 7 Nature of Cybersecurity Threats . 10 Frameworks to Manage Cybersecurity Risk . 13 Cyber Risk in the Federal Sector . 16 Gaps in Managing Cyber Risk in the Federal Sector . 18 Elements Necessary in a Cyber Risk Framework: A Meta-Analysis . 21 Decision Framework for Cybersecurity Risk Assessment: The PRISM Approach . 24 Implementing the PRISM Decision Model . 27 Summary . 35 Appendices . 36 About the Author . 49 Key Contact Information . 51 Reports from the IBM Center for The Business of Government . 52 3 MANAGING CYBERSECURITY RISK IN GOVERNMENT: AN IMPLEMENTATION MODEL IBM Center for The Business of Government FOREWORD On behalf of the IBM Center for The Business of Government, we are pleased to present this report, Managing Cyber Risk in Government: An Implementation Model, by Rajni Goel, James Haddow, and Anupam Kumar of Howard University. The increased use of technologies such as social media, the Internet of Things, mobility, and cloud computing by government agencies has extended the sources of potential cyber risk faced by those agencies . As a result, cyber is increasingly being viewed as a key component in enterprise risk management (ERM) frame- works . At the same time, agency managers encounter the challenge of imple- menting cyber risk management by selecting from a complex array of security controls that reflect a variety of technical, operational, and managerial perspectives .
    [Show full text]
  • Industrial Iot, Cyber Threats, and Standards Landscape: Evaluation and Roadmap
    sensors Review Industrial IoT, Cyber Threats, and Standards Landscape: Evaluation and Roadmap Lubna Luxmi Dhirani 1,2,*, Eddie Armstrong 3 and Thomas Newe 1,2 1 Confirm Smart Manufacturing Research Centre, V94 C928 Limerick, Ireland; [email protected] 2 Department of Electronic and Computer Engineering, University of Limerick, V94 T9PX Limerick, Ireland 3 Johnson & Johnson, Advanced Technology Centre, University of Limerick, V94 YHY9 Limerick, Ireland; [email protected] * Correspondence: [email protected] Abstract: Industrial IoT (IIoT) is a novel concept of a fully connected, transparent, automated, and intelligent factory setup improving manufacturing processes and efficiency. To achieve this, existing hierarchical models must transition to a fully connected vertical model. Since IIoT is a novel approach, the environment is susceptible to cyber threat vectors, standardization, and interoperability issues, bridging the gaps at the IT/OT ICS (industrial control systems) level. IIoT M2M communication relies on new communication models (5G, TSN ethernet, self-driving networks, etc.) and technologies which require challenging approaches to achieve the desired levels of data security. Currently there are no methods to assess the vulnerabilities/risk impact which may be exploited by malicious actors through system gaps left due to improper implementation of security standards. The authors are currently working on an Industry 4.0 cybersecurity project and the insights provided in this paper are derived from the project. This research enables an understanding of converged/hybrid cybersecurity standards, reviews the best practices, and provides a roadmap for identifying, aligning, mapping, converging, and implementing the right cybersecurity standards and strategies for securing M2M Citation: Dhirani, L.L.; Armstrong, communications in the IIoT.
    [Show full text]
  • Implementation Guideline ISO/IEC 27001:2013
    A publication of the ISACA Germany Chapter e.V. Information Security Expert Group Implementation Guideline ISO/IEC 27001:2013 A practical guideline for implementing an ISMS in accordance with the international standard ISO/IEC 27001:2013 Publisher: ISACA Germany Chapter e.V. Oberwallstr. 24 10117 Berlin, Germany www.isaca.de The content of this guideline was developed by members of the [email protected] ISACA Germany Chapter e.V. and was thoroughly researched. Due care has been exercised in the creation of this publication; however, this publication is not comprehensive. It reflects the Team of Authors: views of the ISACA Germany Chapter. ISACA Germany Chapter e.V. • Gerhard Funk (CISA, CISM), independent consultant accepts no liability for the content. • Julia Hermann (CISSP, CISM), Giesecke & Devrient GmbH • Angelika Holl (CISA, CISM), Unicredit Bank AG The latest version of the guideline can be obtained free of • Nikolay Jeliazkov (CISA, CISM), Union Investment charge at www.isaca.de. All rights, including the right to • Oliver Knörle (CISA, CISM) reproduce excerpts of the content, are held by the ISACA • Boban Krsic (CISA, CISM, CISSP, CRISC), DENIC eG Germany Chapter e.V. • Nico Müller, BridgingIT GmbH • Jan Oetting (CISA, CISSP), Consileon Business Consultancy GmbH This guideline was translated from the German original version • Jan Rozek »Implementierungsleitfaden ISO/IEC 27001:2013« published in • Andrea Rupprich (CISA, CISM), usd AG June 2016. • Dr. Tim Sattler (CISA, CISM, CRISC, CGEIT, CISSP), Jungheinrich AG • Michael Schmid (CISM),
    [Show full text]
  • COBIT® 5: Enabling Processes (The ‘Work’), Primarily As an Educational Resource for Governance of Enterprise IT (GEIT), Assurance, Risk and Security Professionals
    Enabling Processes Personal Copy of: Dr. David Lanter : Enabling Processes ISACA® With 95,000 constituents in 160 countries, ISACA (www.isaca.org) is a leading global provider of knowledge, certifications, community, advocacy and education on information systems (IS) assurance and security, enterprise governance and management of IT, and IT-related risk and compliance. Founded in 1969, the non-profit, independent ISACA hosts international conferences, publishes the ISACA® Journal, and develops international IS auditing and control standards, which help its constituents ensure trust in, and value from, information systems. It also advances and attests IT skills and knowledge through the globally respected Certified Information Systems Auditor® (CISA®), Certified Information Security Manager® (CISM®), Certified in the Governance of Enterprise IT® (CGEIT®) and Certified in Risk and Information Systems ControlTM (CRISCTM) designations. ISACA continually updates COBIT®, which helps IT professionals and enterprise leaders fulfil their IT governance and management responsibilities, particularly in the areas of assurance, security, risk and control, and deliver value to the business. Disclaimer ISACA has designed this publication, COBIT® 5: Enabling Processes (the ‘Work’), primarily as an educational resource for governance of enterprise IT (GEIT), assurance, risk and security professionals. ISACA makes no claim that use of any of the Work will assure a successful outcome. The Work should not be considered inclusive of all proper information, procedures and tests or exclusive of other information, procedures and tests that are reasonably directed to obtaining the same results. In determining the propriety of any specific information, procedure or test, readers should apply their own professional judgement to the specific GEIT, assurance, risk and security circumstances presented by the particular systems or information technology environment.
    [Show full text]
  • Examining Cybersecurity Risk Reporting on US SEC Form 10-K
    FEATURE Examining Cybersecurity Risk Reporting on US SEC Form 10-K On 27 June 2017, A.P. Moller-Maersk, Merck & Co., Statistics from 2016 show:6 Inc., TNT, WPP, DLA Piper, Rosneft, the Ukrainian • One in 131 email messages contained malware. state postal service and Princeton Community Hospital in West Virginia, USA, were among the • 15 cyberbreaches exposed more than 10 million numerous organizations that were affected by a identities in each breach. cybersecurity attack that held information systems • 1.1 billion identities were exposed due to hostage in exchange for ransom payments (i.e., cyberincidents. ransomware attack).1, 2 This attack occurred the month after the major ransomware attack WannaCry • On average, it took two minutes for an Internet of was reported on 12 May 2017. Things (IoT) device to be attacked. • Close to 230,000 web attacks occurred each day. One day later, BBC America host Katty Kay asked Michael Chertoff, executive chairman of • 357 million variants of malware were detected. The Chertoff Group and former head of the US Department of Homeland Security, to comment Clearly, organizations face the danger of significant on the chance that state-sponsored or nonstate- losses from cybersecurity incidents and breaches. sponsored terrorist groups will initiate a material The 2011 recommendations for voluntary cyberattack. Chertoff responded that this is “the cybersecurity risk disclosure guidance from the US most serious threat we currently face.”3 Cybersecurity incidents and breaches cause significant losses to affected
    [Show full text]
  • A Scenario-Based Methodology for Cloud Computing Security Risk
    A Scenario-Based Methodology for Cloud Computing Security Risk Assessment Prof. Hany Ammar;Ishraga Mohamed Ahmed Khogali Abstract Cloud computing has been one of the major emerging technologies in recent years. However, for cloud computing, the risk assessment become more complex since there are several issues that likely emerged [1]. In this paper we survey the existing work on assessing security risks in cloud computing applications. Existing work does not address the dynamic nature of cloud applications and there is need for methods that calculate the security risk factor dynamically. In this paper we use the National Institute of Standards and Technology (NIST) Risk Management Framework and present a dynamic scenario-based methodology for risk assessment. The methodology is based using Bayesian networks to estimate likelihood of cloud application security failure which enable us to compute the probability distribution of failures over variables of interest given the evidence. We illustrate the methodology using two case studies and highlight the significant risk factors. We also show the effect of using security controls in reducing the risk factors. Keyword: Cloud Computing Published Date: 12/31/2017 Page.126-155 Vol 5 No 12 2017 Link: http://ijier.net/ijier/article/view/875 International Journal for Innovation Education and Research www.ijier.net Vol:-5 No-12, 2017 A Scenario-Based Methodology for Cloud Computing Security Risk Assessment Prof. Hany Ammar, Ishraga Mohamed Ahmed Khogali Abstract Cloud computing has been one of the major emerging technologies in recent years. However, for cloud computing, the risk assessment become more complex since there are several issues that likely emerged [1].
    [Show full text]
  • A Methodology for Measuring and Monitoring IT Risk
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by South East Academic Libraries System (SEALS) A Methodology for Measuring and Monitoring IT Risk by Natalie Tansley Submitted to define the research area for part fulfilment of the degree Master Technologiae in Business Information Systems in the Faculty of Engineering, The Built Environment and Information Technology of the Nelson Mandela Metropolitan University Supervisor: Helen van de Haar December 2007 Acknowledgements Stephen Flowerday, for his guidance and assistance as promoter for this paper during the initial research period. Helen van der Haar for her guidance and thoroughness as promoter for this paper A Methodology for Measuring and Monitoring IT Risk Table of Contents Chapter 1 : A Methodology for Measuring and Monitoring IT Risk 1.1 Introduction .............................................................................................................................. 4 1.2 Description of Problem Area ..................................................................................................... 6 1.2.1 Problem Statement .................................................................................................................... 7 1.3 Research Objectives .................................................................................................................. 8 1.3.1 Research Methodology .............................................................................................................. 8 1.4 Layout
    [Show full text]