Lisa Nelander edited untitled.html  almost 8 years ago

Commit id: 8e89e592ab4724de1c624a9523c7496d23706f45

deletions | additions      

       

author = {Nina Lissen and Christian BrĂ¼nger and Stephan Damhorst},  title = {Risiken beim Cloud-Computing},  booktitle = {{IT}-Services in der Cloud und {ISAE} 3402}  }" data-bib-key="Lissen_2014" contenteditable="false">Lissen 2014
2014

A  suggestion to prevent this dependence is to always have an exit strategy before entering a contract with a cloud provider.




Risks
  • dependent on the provider
    • provider could go broke
    • service could be bad
    • always affected when provider has to shut down due to e.g. an update 
    • long-term access to important data is reliant on the provider
  • safety and data protection 
    • is the cloud save?
    • who has access?
    • where are the interfaces
    • risk of loosing corporate secrets 
    • abuse of personal data
  • risk of renouncing own IT competence
  • reliability of the cloud
    • risk of loosing important corporate data
  • a working internet connection is crutial
    • reliability of the connection
    • not enough bandwidth at own or servers' location
  • potential need to adapt to the providers software if own software is not offered
  • data protection regulations can be violated
    • problematic when saving personal data in a location abroad (when it's a German company) 
    • risk of fees due to compliance violations

Potentials
  • scalable
  • dynamic load distribution - on demand
    • not all IT resources have to be bought, only those that are needed
    • 10% -50% of the IT hardware is only used in load peaks
    • quick renting of additional capacity i needed (e.g. due to business growth)
  •  lower costs
    • no investment in own assets
    • providers have IT for many companies -> due to amount of resources individual services are cheaper than buying the IT on their own
  • no investment risks (for small companies)
    • business models can be testes and quickly enter and exit the market - short time to market
    • IT resources can just be cancelled and do not have to be sold again
  • easy: management of the servers is outsourced
    • no need of in-house experts (expensive)
    • not dependand on own IT employees
  • Green IT
    • servers are only utilized when needed -> the power consumption is lower 
  • no long-term capital tie-up
    • needed service and hardware are rented as needed
  • risk transfer to provider through defining a SLA (Service Level Agreement)
  • technology is up to date
    • minimizing the risk of default
    • faster and more save
  • using regional locations that are cheaper than storing the IT in the location of the own company