We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byEmily Hyson
Modified about 1 year ago
Confidential. This presentation is provided for the recipient only and cannot be reproduced or shared without Fair Isaac Corporation's express consent. © 2011 Fair Isaac Corporation. 1 Insurance Fraud Manager User Group February 8-9, 2011 San Diego, CA Best Practices Security, Roles and Permissions Andrea Allmon Product Management-Sr Director Health Care and Insurance Kevin Harrison Product Management-Sr Director FICO Platform February 2010
© 2011 Fair Isaac Corporation. Confidential. 2 © 2010 Fair Isaac Corporation. Confidential. 2 Agenda »FICO Platform Architecture »Security(LDAP)/SSO (shared portal) »Users »Permissions (IFM - screen level) »Roles »Groups »Organizations
© 2011 Fair Isaac Corporation. Confidential. 3 © 2010 Fair Isaac Corporation. Confidential. 3 FICO Platform Architecture
© 2011 Fair Isaac Corporation. Confidential. 4 FICO Platform Architecture »Business Objectives »Faster Application Development »Faster Time-to-Value solutions for our clients »Faster turn-around for Upgrades to our clients »Implementation »Standards-based, Service Oriented Architecture (SOA) »Integrates with Operating Systems and Middleware » Operating System » JEE – Java Platform, Enterprise Edition » Application Server » Database Server » LDAP Server »Configurable by Application
© 2011 Fair Isaac Corporation. Confidential. 5 FICO Platform Architecture Hardware »Configurations for FICO Applications »FICO Platform and shared Strategic Differentiators »Third Party Platform Stack »Operating System »Database Server»LDAP Server»Application Server »Java Platform, Enterprise Edition (JEE) FICO Platform Debt Manager Fraud Manager Origination Manager Insurance Fraud DM App DM App FICO Application Business Services
© 2011 Fair Isaac Corporation. Confidential. 6 What is FICO Platform? What functionality does it provide? »Common Data Model »Extensible Data Entities »Encryption »Data Access Layer »Audit, Logging, and History »License Management »Data Acquisition »FICO Network + Transformation »Bureau + Data Interfaces »Decision Management System »Characteristic Library »Model Deployment »Adaptive Control »Performance Reporting »Transaction Scoring »Business Rules Management »Blaze Advisor (RMA) »Business Intelligence »Browser-based reports integration »Security Framework »Role Based Access Control »LDAP Integration + Federation »Single Sign-on »UI Framework »UI Builder (SmartForms) »Context Sensitive Help »Call Scripting »Internationalized (I18N) »Double-byte character set (DBCS) »Locale aware (Region + Language) » Date, Time, Currency, Numeric separators »Externalized Translation Configuration »Case Management »History + Notes »Evidence Locker »Workflow »Document Services »Document Templates »PDF, , SMS
© 2011 Fair Isaac Corporation. Confidential. 7 © 2010 Fair Isaac Corporation. Confidential. 7 Security (LDAP)/SSO
© 2011 Fair Isaac Corporation. Confidential. 8 FICO Platform use of LDAP »What is LDAP and what purpose does it serve? » LDAP = Lightweight Directory Access Protocol »FICO client needs »LDAP integration for Administration and Support » Reuse Corporate configuration for Groups, Users, and Password policy »Centralized and Delegated Administration »FICO Platform products »Use standard LDAPv3 integration for Directory Services »Have Delegated administration features to write to LDAP »Use of LDAP Server »Users (with Group membership) » only attributes in standard LDAP schema » Extended attributes in FICO database »Groups (with hierarchy) » only attributes in standard LDAP schema » Extended attributes in FICO database »Password policy
© 2011 Fair Isaac Corporation. Confidential. 9 Single Sign On »FICO application roadmap requirements from clients »Support for Single Sign On environments »Support for Federated Security integration »Requires centralized authorization server »Typically an LDAP server or integrated with LDAP servers »Implemented by an authentication token »Federation requires trusted relationship »Site-deployed »Workstation login establishes authentication token »No user/password required to access applications supporting SSO »ASP/Hosting »One user/password in portal/extranet for multiple hosted applications »Federation allows trust to auto-provision clients
© 2011 Fair Isaac Corporation. Confidential. 10 © 2010 Fair Isaac Corporation. Confidential. 10 Users
© 2011 Fair Isaac Corporation. Confidential. 11 Users Creating Users Department is a free-form entry for “Primary Group.” In a future release, we will be making this a drop-down selector. Setting up the Users Tenants are used when you are hosting more than one customer Locales will be used in future releases for localizations (English, Dutch, German)
© 2011 Fair Isaac Corporation. Confidential. 12 Users »User Creation »Users are Created in LDAP » Username required » Validated to be unique » First and Last name required for application display » address required for sending temporary password »A temporary password is generated »An is sent to users address »Users are also created in Business Objects »User Setup for Additional details »Some additional LDAP details available for reference » Emp #, phone, mobile, title »Remaining details are user details in the database » Settings: Tenant, Locale, Time Zone » Associations: Groups, Roles, Queues » User is made member of Groups in LDAP »User locale and time zone settings are updated in Business Objects
© 2011 Fair Isaac Corporation. Confidential. 13 © 2010 Fair Isaac Corporation. Confidential. 13 Roles
© 2011 Fair Isaac Corporation. Confidential. 14 Roles »Roles should be configured by job function »Contain a set of permissions to access a resource »Typically assigned to a Group of users that do that job » Ease roles administration for large number of users » Ensure backup resource with 2 or more users in each group »IFM ships with the following default Roles: »Full Administrator »Manager »Investigator »Medical Management »Claims Reviewer »Claims Supervisor »Information Only »Triage/Case Administrator
© 2011 Fair Isaac Corporation. Confidential. 15 Roles Hierarchy example
© 2011 Fair Isaac Corporation. Confidential. 16 Permissions and Roles »Permissions »Allows access to system-level features »Roles – Job Function »Group of access permissions »Roles hierarchy » lower-level roles contain subset of upper-level role’s permissions »Users and Work Groups may have one or more Roles »Role administration can be delegated » By Role with Role Permissions (Add, Manage, Change, Modify) » Users are limited to Scope of Authority (their lower-level Roles) »Roles are not bound by organization or operational areas » Allows shared job functions across the organization and operation » ie: Delegated Administration: User Administration, Group Administration » Unless defined that way in the hierarchy
© 2011 Fair Isaac Corporation. Confidential. 17 Role Based Access Control (RBAC) »Separation of Duties »Role Type: Security Administrator » Top-level access control to all security objects and audit logs » Defines primary roles and groups » Establishes System Administrators and Delegated Administrators »Role Type: System Administrators » Manages System Configuration options » Monitors System Function and maintains operational environment »Role Type: Delegated Administrators » Manages Business or Departmental Operations » Allows configuration changes to respond quickly to business needs »Best Practice* »Define top-level roles as superset for job functions » Create lower-level child roles as permission subsets » Allows sharing some permissions for staff in cross-functional roles » Typical that some users do two jobs » or cover tasks of other staff as needed (out-of-office, vacation, sick)
© 2011 Fair Isaac Corporation. Confidential. 18 © 2010 Fair Isaac Corporation. Confidential. 18 Permissions
© 2011 Fair Isaac Corporation. Confidential. 19 Permissions »IFM Permissions are at the detailed functional level »Permissions are defined as Action and Resource pair »Permissions can be assigned to multiple roles »Authorization service checks user’s Roles for permissions »Permissions can control access to various User Interface elements » Menus » Menu Items » Screens/Page » Screen Elements » Navigation items (buttons, hyperlinks) » Controls (textbox, drop-down list, grid, etc) »Work in Progress »Renaming permissions to provide better clarity »Next release includes permission category » Ability to filter list of permissions by category » examples: Users, Groups, Roles, Queues, Menu, Grid, Domain Values
© 2011 Fair Isaac Corporation. Confidential. 20 © 2010 Fair Isaac Corporation. Confidential. 20 Groups
© 2011 Fair Isaac Corporation. Confidential. 21 Groups »Work Groups/Departments »Work Groups »set of users that are grouped »represent operational groups or teams. »Work groups simplify administration of large number of users » roles and queues associated to group apply to all members of the group »Administration for lower level user groups can be delegated to users or user groups associated to upper level user groups. »Next release changing to User Group nomenclature »Common name for container for number of users »Better represents the alignment with LDAP User Groups »New attribute in user details for Tenant-specific Primary Group
© 2011 Fair Isaac Corporation. Confidential. 22 Work Groups are defined by »Tenant »Each tenant may have different users and operational needs »User with appropriate permission in Roles »Create Work Groups (add) »Maintain Work Groups (edit) »Business Managers or Supervisors »Define group and team structure for their business operations area » Hierarchy (inheritance) to define Managers, Supervisors, Teams »Scope of Authority limited to the groups they are in » Maintaining users and assignments in “my work groups” » Maintain configuration for lower-level work groups
© 2011 Fair Isaac Corporation. Confidential. 23 © 2010 Fair Isaac Corporation. Confidential. 23 Organization
© 2011 Fair Isaac Corporation. Confidential. 24 Organization »Coming Soon – Organization lets you have better control of Document Templates, etc. »Optional – Default organization is used until configured »Authorization to certain system resources can be based on an organizational hierarchy and RBAC. »Roles determine if user can access the screen and perform actions »Organization hierarchy determines what data the user can act upon » What resource is listed as available to act on »Organization hierarchy models division, departments, and teams »Work groups are associated to one or more organizations »Users can also be associated individually to organizations »Administration for lower level organizations can be delegated to users or user groups associated to upper level organizations.
© 2011 Fair Isaac Corporation. Confidential. 25 Organization »Example »A role permission allows user to update document templates »The user is a member of one or more organizations »Certain document templates are associated to organizations »The document templates available to the user are limited to document templates that belong to the user’s organization(s) »Organization resources »document templates »business calendars »Scripts »other entities defined by FICO products »For backward compatibility, these resources are part of the Default Organization available to All User and All Groups
© 2011 Fair Isaac Corporation. Confidential. 26 Delegated Administration »Delegated Administration »Of Users, Work Groups, and Roles »managed by individual clients, divisions, departments » Such as directors, managers, and supervisors »hierarchal structure allows Scope of Authority limits to » Roles they have been associated to and the child roles of those roles » Work Groups they have been associated to, the child groups of those groups » Users within those work groups. » Organizations they have been associated to and the child organizations of those organizations »Role permissions determine which maintenance has been delegated » Users are always limited to Scope of Authority » User cannot change hierarchy without permission to act on resource » Create, Edit, or Delete » For specific hierarchy (Roles, Work Groups, or Organizations)
© 2011 Fair Isaac Corporation. Confidential. 27 Tenant with Delegated Administration
© 2011 Fair Isaac Corporation. Confidential. 28 Open Discussion »What have you found that works best? »What don’t you like? »What would you like to see differently?
Confidential. This presentation is provided for the recipient only and cannot be reproduced or shared without Fair Isaac Corporation's express consent. © 2011 Fair Isaac Corporation. 29 Insurance Fraud Manager User Group February 8-9, 2011 San Diego, CA THANK YOU
SharePoint Governance Questions January 2014 ©2014 SUSAN HANLEY LLC.
Windows 2008 Active Directory Configuration – Week 4 of 6 Microsoft Test: Mark McCoy MCSE, CNE, CISSP.
Copyright © 2010 Accenture All Rights Reserved. Accenture, its logo, and High Performance Delivered are trademarks of Accenture. Accenture Software ALIP.
Web Center v4.1 Proprietary and Confidential Topic Section Overview 1 Rates and Data 2 Creating Promotions 3 Sitemap / Formatting Content 4 Administration.
Scaling to new heights 1 STR.Grants and Our Software Solutions 123 Our Software Will Help You Meet Your Grants Management Challenges.
1 Design Guidance. 2 Contents Setting up the customer portal Implementation Checklist.
1 Capability Set - Detail. 2 Bb Academic Suite Capability Set by : System.
1 Unified Communications and Collaboration Campaign MM TI-BDM Deck User Guidance Purpose of this deck: –Show how Microsoft ® Unified Communications and.
© 2008 FedEx. All rights reserved. FedEx Ship Manager ® at fedex.com Shipping Administration Presentation for administrators.
Dec 2005 UMT Portfolio Manager Builder User Training.
Database Controls 2012 National State Auditors Association Information Technology Conference September 2012.
March Technical Documentation License Agreement (Standard) READ THIS! This is a legal agreement between Microsoft Corporation (“Microsoft”) and.
Windows 2008 Active Directory Configuration – Week 3 of 6 Microsoft Test: Mark McCoy MCSE, CNE, CISSP.
SolidWorks Enterprise PDM and Microsoft SharePoint Interoperability Marc Young xLM Solutions, LLC.,
Introduction to INCOSE Connect for Distributed Teams with Windows SharePoint Services 3.0 https://connect.incose.org Prepared by: James Chism, Adjunct.
PrevNext | Slide 1 WELCOME TO THE MEGS SYSTEM CONSOLIDATED APPLICATION Title I, Part C Migrant Education Regular School Year Presented by: Judy Byrnes.
Copyright © 2005 SOA Software, Inc. All Rights Reserved. Specifications Subject to Change Without Notice. Overcoming the SOA Network Fallacy Roberto Medrano.
© 2008 IBM WebSphere Portal v6.1 Migration Rob Holt WebSphere Portal Migration Lead.
PrevNext | Slide 1 Michigan Electronic Grants System MEGS MEGS Overview and Updates for DLEG Adult Education.
PrevNext | Slide 1 WELCOME TO THE MEGS SYSTEM HOMELESS STUDENT APPLICATION Created:
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Software Re-use IS301 – Software.
Advanced Features for INCOSE Connect Administrators with Windows SharePoint Services 3.0 Prepared by: James Chism, Adjunct Faculty-Johns Hopkins University.
Introduction to NT Administration Objectives: How to use DOMAINS Create Users & Set Properties to user accounts Manage User Accounts & Assign Security.
PrevNext | Slide 1 Michigan Electronic Grants System MEGS Career Initiatives Office of Career and Technical Preparation.
Microsoft ® Exchange Online Overview. Notes (hidden) The default view of this deck is a short (6-slide) presentation, targeted to mid-sized customers.
Performance Evaluation HR Training Sessions May , 2013.
Architectural Design IS301 – Software Engineering Lecture # 14 – M. E. Kabay, PhD, CISSP Dept of Computer Information Systems Norwich University.
Time & Labor Management Solutions XactTime Overview.
PrevNext | Slide 1 Michigan Electronic Grants System MEGS https://megs.mde.state.mi.us/megs/ MEGS Application Last Updated: 2/4/2011.
© 2016 SlidePlayer.com Inc. All rights reserved.