Shadow IT - Revision history

User at 22:23, 7 December 2022

2022-12-07T22:23:25Z

User at 22:22, 7 December 2022

2022-12-07T22:22:29Z

Show changes

User: /* See Also */

2021-07-15T01:53:05Z

User at 18:36, 23 March 2021

2021-03-23T18:36:46Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T18:19:42Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

Show changes

User at 22:36, 29 January 2021

2021-01-29T22:36:57Z

User at 21:00, 27 August 2019

2019-08-27T21:00:51Z

User at 20:59, 27 August 2019

2019-08-27T20:59:52Z

User at 20:54, 27 August 2019

2019-08-27T20:54:45Z

User at 20:41, 27 August 2019

2019-08-27T20:41:04Z

@@ Line 72: / Line 72: @@
 *[[IT Operations Management (ITOM)]]
 *[[IT Optimization]]
 *[[Compliance]]
 *[[Risk Management]]

@@ Line 67: / Line 67: @@
 == See Also ==
-[[Information Technology (IT)]]<br />
+*[[Information Technology (IT)]]
-[[IT Operations (Information Technology Operations)]]<br />
+*[[IT Operations (Information Technology Operations)]]
-[[IT Operations Management (ITOM)]]<br />
+*[[IT Operations Management (ITOM)]]
-[[IT Optimization]]<br />
+*[[IT Optimization]]
-[[Security Policy]]<br />
+*[[Security Policy]]
-[[Compliance]]<br />
+*[[Compliance]]
-[[Risk Management]]<br />
+*[[Risk Management]]
-[[Enterprise Risk Management (ERM)]]<br />
+*[[Enterprise Risk Management (ERM)]]
-[[Enterprise Resource Planning (ERP)]]<br />
+*[[Enterprise Resource Planning (ERP)]]
-[[Data Center]]<br />
+*[[Data Center]]
-[[Data Management]]<br />
+*[[Data Management]]
-[[Enterprise Integration]]
+*[[Enterprise Integration]]
+*[[IT Governance]]
 == References ==

@@ Line 43: / Line 43: @@
 *Compliance: Unauthorized applications once discovered can mandate a complete audit of the infrastructure to ensure you are compliant. Organizations who do not take this seriously risk hefty fines from non-compliance.
 *Testing: IT infrastructures are complex organisms that require management. Introducing new applications without proper testing can compromise the entire infrastructure. Shadow IT also adds more complexity to the entire testing process by having to involve a third party.
-*Configuration management: Creating a configuration management database (CMDB) and defining relationships between different systems is labor-intensive. When other employees use shadow IT, those systems are not included and can have compatibility issues as a result.
+*Configuration management: Creating a [[Configuration Management Database (CMDB)|configuration management database (CMDB)]] and defining relationships between different systems is labor-intensive. When other employees use shadow IT, those systems are not included and can have compatibility issues as a result.

@@ Line 1: / Line 1: @@
 == Definition - What is Shadow IT<ref>Defining Shadow IT [https://en.wikipedia.org/wiki/Shadow_IT Wikipedia]</ref> ==
-Shadow IT is a term often used to describe information-technology systems and solutions built and used inside organizations without explicit organizational approval. It is also used, along with the term "Stealth IT", to describe solutions specified and deployed by departments other than the IT department. Shadow IT is considered by many an important source for innovation and such systems may turn out to be prototypes for future approved IT solutions. On the other hand, shadow IT solutions are not often in line with the organization's requirements for control, documentation, security, reliability, etc., although these issues can apply equally to authorized IT solutions.
+'''Shadow IT''' is a term often used to describe information-technology systems and solutions built and used inside organizations without explicit organizational approval. It is also used, along with the term "Stealth IT", to describe solutions specified and deployed by departments other than the IT department. Shadow IT is considered by many an important source for innovation and such systems may turn out to be prototypes for future approved IT solutions. On the other hand, shadow IT solutions are not often in line with the organization's requirements for control, documentation, security, reliability, etc., although these issues can apply equally to authorized IT solutions.
 The consequence of stealth IT is that it opens up both security and legal risks for the company. Unfortunately, IT doesn’t discover many of the stealth IT incidences until they have caused significant damage. By then it is a much bigger problem to fix. The IT department loses control on activities and services in the organization and often Sys Admins find themselves solving issues that they originally had nothing to do with.
 While the IT department may not handle the physical infrastructure or management of Shadow IT applications and services, IT does carry the burden of ensuring security and compliance for the corporate data that employees create and transmit through Shadow IT sources. This creates mixed feelings toward Shadow IT, as some enterprises are willing to embrace the innovation and increased productivity it can deliver, while others aren't as willing to look past the increased risk of security and compliance complications of Shadow IT.<ref>Shadow IT's Effect on IT Departments [https://www.webopedia.com/TERM/S/shadow-it.html Webopedia]</ref>

@@ Line 50: / Line 50: @@
 *Creates inefficiencies, as the business needs to support more than one service, which can lead to duplicate support and system integration costs.
 *Increases security risks, as data held in shadow IT services may not be managed, maintained and secured in the same way corporate data is.
-Constitutes a barrier to enhancing IT services, as end users, satisfied by shadow IT, may not feel the need to push for better services from the IT department.
+*Constitutes a barrier to enhancing IT services, as end users, satisfied by shadow IT, may not feel the need to push for better services from the IT department.

← Older revision		Revision as of 20:59, 27 August 2019
Line 65:		Line 65:

	== See Also ==		== See Also ==
		+	[[Information Technology (IT)]]<br />
		+	[[IT Operations (Information Technology Operations)]]<br />
		+	[[IT Operations Management (ITOM)]]<br />
		+	[[IT Optimization]]<br />
		+	[[Security Policy]]<br />
		+	[[Compliance]]<br />
		+	[[Risk Management]]<br />
		+	[[Enterprise Risk Management (ERM)]]<br />
		+	[[Enterprise Resource Planning (ERP)]]<br />
		+	[[Data Center]]<br />
		+	[[Data Management]]<br />
		+	[[Enterprise Integration]]

← Older revision		Revision as of 20:54, 27 August 2019
Line 26:		Line 26:
	*Is a collaborator entitled to use any tools that he/she may find suitable to boost his/her productivity if they pose no risk for the corporation? If so what is the registry/ \approval process that needs to be followed?		*Is a collaborator entitled to use any tools that he/she may find suitable to boost his/her productivity if they pose no risk for the corporation? If so what is the registry/ \approval process that needs to be followed?
	*What shall be the impact and compliance probability from the collaborators towards prohibitions? Meaning it is pointless to have someone spending hours trying to find a way to break a prohibition in place instead of doing their work.		*What shall be the impact and compliance probability from the collaborators towards prohibitions? Meaning it is pointless to have someone spending hours trying to find a way to break a prohibition in place instead of doing their work.
		+
		+
		+	== Managing Shadow IT<ref>How to Successfully Manage the Shadow IT [https://www.gb-advisors.com/shadow-it-2/ GB Advisors]</ref> ==
		+	While the effects of Rogue IT can be challenging for organizations, it is also true that through good management you can use this phenomenon to turn it into a business advantage. Let’s see some recommendations to successfully manage the Shadow IT:
		+	*Locate the Shadow IT: According to a survey by the Frost and Sullivan Institute, sponsored by McAfee; 80% of employees agree that they have incurred in this practice. This means that there is a high probability that this trend may be taking place in your organization. Therefore, the best thing to do is to carry out an in-depth analysis that allows you to filter the exchange of information with external elements. From there, it will be easier for you to identify processes involving unauthorized solutions.
		+	*Find the reason why: There are several reasons why an employee may be motivated to practice Shadow IT, such as the fact that this phenomenon allows users in the organization to use the latest applications without waiting for IT to verify or approve them. Carry out an evaluation to determine the main reasons for the appearance of the Invisible IT. As a result, you will be able to obtain valuable information that will enable CIOs to take more effective measures to meet the user’s needs, related to the use of effective tools.
		+	*Minimize the risks: Instead of banning the use of Shadow IT applications, seek to implement security solutions to control their use. Invest in a tool that allows you to protect your systems in a comprehensive way, by protecting the organization’s sensitive data both in the internal flow and in interactions in the cloud. Such solutions should give you full visibility into your assets to help you locate any potential source of threats faster.
		+	*Build up confidence: Finally, encourage open communication between users and CIOs; and also raise awareness of the benefits of using controlled applications within the enterprise. Most importantly, do not hold back innovation. Whether employees develop applications or use tools in an unauthorized manner, these practices can be the perfect opportunity to find new ways to solve problems, increase workflow efficiency and improve business competitiveness through new tools. So look for a strategy that rather than prohibiting certain applications, allows you to support users in the use of innovative solutions.

@@ Line 4: / Line 4: @@
 The consequence of stealth IT is that it opens up both security and legal risks for the company. Unfortunately, IT doesn’t discover many of the stealth IT incidences until they have caused significant damage. By then it is a much bigger problem to fix. The IT department loses control on activities and services in the organization and often Sys Admins find themselves solving issues that they originally had nothing to do with.
@@ Line 65: / Line 67: @@
 *Shadow IT Assessment: Methods for identifying business-managed IT [https://bitco3.com/en/news/2018/01/11/shadow-it-assessment-methods/ BITCO3]
 *How to deal with “Shadow IT” [https://www.mrc-productivity.com/blog/2019/07/how-to-deal-with-shadow-it-2/ Joe Stangarone]