1 / 1

Data Stewardship: Defining Attribute Release Policy Tying Data management to business strategy

Data Stewardship: Defining Attribute Release Policy Tying Data management to business strategy Marjorie Campbell ; EA, Mgr Integration Services Kathy Wright; CRLT, IT Architect. BACKGROUND. THE PATH TO IMPLEMENTATION. USER AUTHENTICATION.

aretha
Download Presentation

Data Stewardship: Defining Attribute Release Policy Tying Data management to business strategy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Stewardship: Defining Attribute Release Policy Tying Data management to business strategy Marjorie Campbell; EA, Mgr Integration Services Kathy Wright; CRLT, IT Architect BACKGROUND THE PATH TO IMPLEMENTATION USER AUTHENTICATION • Strategic planning and management for establishing policies, procedures, and guidelines for management of institutional data across Clemson University for: • Secure & Access Provisioning • Education & Awareness • Policy • Retentions & Preservation • It is incumbent upon IT management to establish a high level of trust & communication between IT and University record’s administrators through support engagement with Data Stewardship Committee. • Phase I: Populate CUVault in Parallel with Existing Systems • Connect to authoritative sources for employee/student info • Develop rules to resolve identities across sources • Identify additional authoritative sources and connect to them • May be able to connect to CUID for secure attribute access • Prototype web applications • Phase II: • Change Business Rules so CUVault is Auth Source for Identity • Deploy identity management applications (self and proxy) • Connect CUVault to CLEMSONU, CUID, and the mainframe • Change HR/Registrar processes such that ID is created or associated at application • Phase III: • Connect additional applications to CUVault • Identify applications that need data stored in CUVault • Design Connectors and Business Rules for each application Challenges? • Clemson University call unique person “University records” • IT call unique person “identity attributes” ATTRIBUTE TRANSFER CLEMSON’S UNIQUE PERSON (CU Vault) WHAT IS AN ATTRIBUTE? A single piece of information associated with an electronic identity database record. Example: Unique ID Roles – employee, student, HHS Relationships – groups, classes, entitlements KEY CONCEPTS • Customer service •  Unique person • Dynamic identification • Trust, role-based directories • Secure access CUVAULT GOALS: • Goals: • Single view of person • Secure access for applications to identity data • Stream line process – time and money savings • Identity access audit • Historical identity (cradle to grave) • Improved customer experience CHALLENGES / ISSUES • Technology change: Easy • Policy change: Not so much • Start policy talks early.

More Related