• No results found

Identity Lifecycle Management. Lessons Learned

N/A
N/A
Protected

Academic year: 2021

Share "Identity Lifecycle Management. Lessons Learned"

Copied!
18
0
0

Loading.... (view fulltext now)

Full text

(1)
(2)

#RSAsummit

Who is Advancive

Pasadena, CA

Bangalore, India

Established in May 2009

Headquartered in Southern California, with additional delivery center in

Bangalore and serving clients globally Consulting and systems integration firm with core competency in Identity &

Access Management Solutions Design & Implementation

Serving clients in several key verticals, such as Financial, Healthcare, Telecom, High-Tech and Manufacturing

(3)

Enterprise Identity Life Cycle Management Defined

Hire Onboard Transfer Terminate

ILM Stages

Request & Approval

Fulfillment

Enforcement

Review & Certification

Accounts Entitlements

Resources Special Permissions

Privileged Rights The process of requesting and

approving access (new, transfer, termination) to a target system, application, or resource for a user (person, system or applications)

Request & Approval

The process of identifying the

Review & Certification

The process of granting or removing access on a target system or application to a user (person, service, or application).

Fulfillment

The process of enforcing coarse and fine-grained access decisions

Enforcement Joiners

Movers Leavers

(4)

#RSAsummit

Enterprise Identity Life Cycle Management Defined

• People, processes and technology required to manage digital identities and their access to enterprise resources

• Typically covers an entire spectrum of identities within

organization: employees, contractors, customers, partners, etc

• Manages identities throughout the entire relationship with the organization: acquisition, modification, termination

(5)

Case Study: Multinational Banking Institution

• Over 15,000 users worldwide

• Major branches in North America, Europe and Asia

• Highly manual, complex ILM processes that differ from region to region

• Some level of automation via several in-house built tools

(6)

#RSAsummit

Analysis: Organizational Readiness

• We bought the tool, now what do we do?

• Enterprise security (project owner) fully onboard

– However clear lack of communication or buy-in from other major

stakeholders, especially HR and application owners

• Requirements were poorly defined, the team had trouble articulating AS-IS and TO-BE system requirements

– Significant portion of project budget was spent on helping the client

(7)

Analysis: Organizational Readiness

• The client was not prepared to streamline or adjust existing business processes with expectation that the tool will be able to solve existing problems

(8)

#RSAsummit

Analysis: Project Execution

• Scope creep. As the project progressed, new requirements were constantly added without much thought given to

criticality or prioritization

• Best practices and recommendations were frequently discarded, because “that’s not going to work for us”

(9)

Analysis: Project Execution

• Client’s original intent to avoid any customization was quickly abandoned in order to implement “complex requirement X”

• Inadequate skillset of resources assigned by client to the

project, as well as poor understanding of product capabilities and limitations

(10)

#RSAsummit

Analysis: Identity Lifecycle Process

• No good idea of where user identities were coming from or who was

responsible for managing them

– Especially true for non-employee identities, such as contractors and temp workers

• No standards governing quality of identity data

• Lack of global unique identifier across different types of users

– Some contingent workers did not have unique identifier at all. Those that did would sometimes conflict with employee IDs

• Mainly manual user onboarding and access request process that differs

(11)

Analysis: Identity Lifecycle Process

• Review and removal of access for people changing job functions or

business units (transfers) has not been performed

• Removal of access for terminated people was ad-hoc and inconsistent

• No clear understanding or process definition for terminating or extending

access for contingent workers

• No standard account naming convention across applications and lack of

(12)

#RSAsummit

Lessons Learned: Governance & Delivery

• Ensure strong executive project sponsorship with authority to affect change

• Communication, communication, communication

• Engage IT AND business stakeholders early in the process

• Do your homework BEFORE jumping on product implementation

– Define existing state, future state and a clear roadmap

(13)

Lessons Learned: Governance & Delivery

• Build IAM architecture

– IAM Governance (oversight, policies and procedures, processes and compliance)

– Identity Architecture

– Access Architecture

– Authoritative Sources

• Business process reengineering is as much part of the process. Not all

manual processes can be effectively automated NOR SHOULD THEY BE

(14)

#RSAsummit

Lessons Learned: Governance & Delivery

• Follow best practices, even if it means changing certain business processes. It may cause some pain now, but will make life easier down the road

• Take the IAM project as an opportunity to streamline and simplify processes and technology architecture

(15)

Lessons Learned: Identity Lifecycle Management

• Establish an authoritative source of identity data for ALL in-scope users

• Establish identity data governance framework. Understand user

on-boarding and off-on-boarding processes and establish data and process ownership

• Standardize identity lifecycle and access provisioning/de-provisioning

process across different locations and business units

• Focus on lifecycle process automation using authoritative source

(16)

#RSAsummit

Lessons Learned: Identity Lifecycle Management

• Create globally unique identifiers for ALL classes of users

• Provisioned accounts follow standard naming conventions and maintain account correlation attributes

(17)

Key Contacts

Advancive Technology Solutions Headquarters

201 South Lake Avenue | Suite 703 | Pasadena, CA 91101 |

www.advancivetech.com

Art Poghosyan, Managing Director

E: [email protected] T: 213.915.4142

Alex Gudanis, CTO

E: [email protected] T: 714.388.5565

(18)

References

Related documents

The “To Upgrade or Not To Upgrade” application will be a scan utility for end-users to acknowledge their device's hardware components and show what upgradability options are

The designations TM and SM are often used for trade- marks and service marks that are not registered, and serve as informal notices to the public that a word, logo, slogan,

2007-present Judge Pro Tempore- King County District Court; Seattle Municipal Court?. 2008 Judge Pro Tempore- Lake Forest Park

Severity of harm Curable injury with- out incapa- city to work (reversible) Curable injury with incapacity to work (reversible) Slight, permanent injury to health

(Eds.), The Measurement of Productive Efficiency, Second Edition, Oxford University Press. Detecting outliers in deterministic nonparametric frontier models with multiple

The applicant shall be notified that in the event verification of eligibility should reveal the applicant does not fall within the requirements, the applicant shall be required to

Period If your claim for LTD benefits is approved by The Standard, benefits become payable after the benefit waiting period. This is a specified number of days during which you

Provides a lower monthly benefit than the Basic Allowance, but guarantees that after your death one half of the monthly benefit paid to you will be paid to your surviving