Identity and Access Mgmt - Gartner Symposium

IAM is at the heart of every business
Helps manage risk through accountability and transparency
- intelligence = audit and analytics
- administration
- access

Value changes with maturity
1) security efficiency; IAM for the sake of IT; save time and money
2) security effectiveness; compliant with policy and regulation
3) business enablement; this is where most of the value is
Look at all three; value metrics

Business process improvements
Risk management
Fine grained controls

Trend - people are bailing on the Admin projects because it doesn't provide value that was expected; instead people are moving to intelligence; failing to deliver compliance; maybe there is a different way; end game is intelligence; provisioning by itself is not enough

Intelligence focuses on auditing, monitoring and manual remediation, and analytics

Provisioning still needs to happen; admin is becoming more out of the box; what are the most important systems to protect?

Primary functional capability across intelligence, admin, authentication, authorization
No one vendor provides it all and you don't need it all

Intelligence
- web fraud detection
- ERP SOD

Check out Hype Cycle for IAM, 2010
Leverage the Gartner Maturity Model

Entitlement Lifecycle Mgmt
- role lifecycle mgmt; role based access control RBAC is part of this
- entitlement mgmt

Shifting towards Identity and Access Intelligence

Why IAM projects fail
1) focusing on tools instead of process and value; destined to fail

Establish an IAM governance model; plan, implement, manage, monitor
Align IAM with Business Intelligence; people, process, products

Be aware of the cloud based solutions; most cloud decisions are two to three years out in this space; most people want to wait to see how this plays out; looks promising but still bleeding edge

Customers are disillusioned by the IAM suite; people more comfortable with best of breed; moving to atomic IAM services

Comments

Post a Comment

Popular posts from this blog

Enterprise Architecture Inside Salesforce

Image
  Enterprise  Architecture Inside Salesforce Enterprise Architecture — How We Do It Internally The two words, “Enterprise Architecture”, elicit various reactions — everything from “ we tried that and it doesn’t work ” to “ we need that! ” to “ we have an effective EA practice ”. Unfortunately it is possible (even easy) to do Enterprise Architecture  incorrectly , with an approach that is lethargic, technology-first and theoretical — the classic ivory tower. (In Salesforce, the internal IT group reporting into our CIO is called “Business Technology” so you’ll see me use BT to refer to Salesforce IT) I lead the Salesforce Enterprise Architecture team within Business Technology and I’m often asked the following questions: how does Salesforce do Enterprise Architecture? why do you need Enterprise Architecture? how do you shift the conversation to business capabilities? Illuminate — The “How” of Salesforce Enterprise Architecture Let me start with the “HOW” first. Within Sales...
Read more

Illuminate - Business Model Exploration

Image
  Illuminate — Business Model Exploration One of our world-class Salesforce Enterprise Architects, Jonathan Laudicina ( https://www.linkedin.com/in/jonathan-laudicina/  ) has done amazing work on Business Model Exploration. I want to highlight some of his work and I think you’ll find it useful. As a reminder, Illuminate is the Enterprise Architecture Methodology that we use inside Salesforce as well as with our customers. The overall Illuminate methodology is depicted below. You will notice that Business Model Exploration is the first step in Illuminate. Business Model Exploration is the methodology we use with customers to articulate: External Forces pushing on the business Internal Forces pushing on the business Customer specific Business Model Canvas At the heart of Business Model Exploration is the Business Model Canvas. It is the place in which you capture key factors about a company’s specific value proposition, partners, customer segments, cost structure and revenue str...
Read more

5 Key Components of a Successful Enterprise Architecture Function

  5 Key Components of a Successful Enterprise Architecture Function 5 Key Components of a Successful Enterprise Architecture Function Creating and managing a successful Enterprise Architecture function requires a variety of different hard and soft skills. In addition, each company is different and the Enterprise Architecture function needs to calibrate and align itself to the specific company. However, there are five common features of a successful Enterprise Architecture function that are applicable to all companies. 1. Governance Enterprise Architecture (EA) requires governance, however not in the form of complex documents, forms or processes.  Definitely avoid EA being seen as the policy-enforcement team — people will avoid EA if the perception is that EA is a blocker.  The best governance starts with a simple, recurring dialogue across multiple functions facilitated by EA. I am always amazed at how valuable it is just to get cross-functional teams to  talk . Pick...
Read more