Skip to main content

Need for IT governance

Need for Cloud Governance

Ever since cloud technology has turned into a mainstream IT resource, security and compliance have been its major issues. Not every cloud deployment sees success, and not every cloud project yields the desired results for its organisation. However, most IT decision makers have come to terms with the fact that when coupled with the right tools and strategies, cloud usage can surpass the security offered by in-house legacy applications and emerge as a true game changer. Cloud governance plays a vital role in this capability. By implementing cloud governance, organisations can avoid the following issues:
• Security and privacy risks: Which may arise due to unauthorised downloads/ installation of software, storage of illegal data and access to restricted sites by users.
• Vendor lock-in: Many vendors opt for this, as this clause causes organisations to depend on the cloud service provider (or vendor) for products and services. The clause is usually made part of the agreement, and as a result, it does not the organisations to bring in another vendor to work on different modules for a specific period of time. This can be avoided by making changes to the SLA suitably and reduce dependencies on a single vendor, thus ensuring freedom to the organisation.
• Cloud Sprawl: Happens when employees of different departments use different programs and cloud infrastructure from third party providers without involving the IT department and getting necessary approvals. Employees usually utilise free cloud services like Google Drive, Dropbox etc. for many of their official work as it is free and there are not much of approvals required. If not detected and restricted, crowd sprawl may lead to fragmented, redundant, inefficient and unmanaged cloud programs sitting on the enterprise cloud and unnecessarily creating trouble.
• Shadow IT and unwarranted usage of cloud resources: Happens when employees in various departments do not follow the rules and regulations as imposed by the IT department on cloud usage resulting in security breach and fragmented control throughout the organisation. This leads to not getting sufficient results from the cloud in the long run.
• Lack of data portability and interoperability: Happens when the cloud service provider or the inbuilt cloud infrastructure is incapable of connecting well with other Introduction to software and products outside the organisation. This may also lead to modules not compatible with each other and hence chaos in the cloud due to inefficient system.

Comments

Post a Comment

thank you for visiting :)

Popular posts from this blog

The Seven-Step Model of Migration

Irrespective of the migration approach adopted, the Seven-step Model of Cloud Migration creates a more rational point of view towards the migration process and offers the ability to imbibe several best practices throughout the journey Step 1: Assess Cloud migration assessments are conducted to understand the complexities in the migration process at the code, design and architectural levels. The investment and the recurring costs are also evaluated along with gauging the tools, test cases, functionalities and other features related to the configuration. Step 2: Isolate The applications to be migrated to the cloud from the internal data center are freed of dependencies pertaining to the environment and the existing system. This step cuts a clearer picture about the complexity of the migration process. Step 3: Map Most organisations hold a detailed mapping of their environment with all the systems and applications. This information can be used to distinguish between the ...
Post a Comment
Read more

Special Permissions in linux

The setuid permission on an executable file means that the command will run as the user owning the file, not as the user that ran the command. One example is the passwd command: [student@desktopX ~]$ ls -l /usr/bin/passwd -rw s r-xr-x. 1 root root 35504 Jul 16 2010 /usr/bin/passwd In a long listing, you can spot the setuid permissions by a lowercase s where you would normally expect the x (owner execute permissions) to be. If the owner does not have execute permissions, this will be replaced by an uppercase S . The special permission setgid on a directory means that files created in the directory will inherit their group ownership from the directory, rather than inheriting it from the creating user. This is commonly used on group collaborative directories to automatically change a file from the default private group to the shared group, or if files in a directory should be...
Post a Comment
Read more

RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version

import tweepy /usr/lib/python2.7/dist-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version!   RequestsDependencyWarning) Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/usr/local/lib/python2.7/dist-packages/tweepy/__init__.py", line 14, in <module>     from tweepy.api import API   File "/usr/local/lib/python2.7/dist-packages/tweepy/api.py", line 12, in <module>     from tweepy.binder import bind_api   File "/usr/local/lib/python2.7/dist-packages/tweepy/binder.py", line 11, in <module>     import requests   File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 97, in <module>     from . import utils   File "/usr/lib/python2.7/dist-packages/requests/utils.py", line 26, in <module>     from ._internal_utils import to...
Post a Comment
Read more

tag