Role Based Security Planning for Lawson Security - PowerPoint PPT Presentation

1 / 20
About This Presentation
Title:

Role Based Security Planning for Lawson Security

Description:

Role Based Security Planning for Lawson Security – PowerPoint PPT presentation

Number of Views:270
Avg rating:3.0/5.0
Slides: 21
Provided by: digitalc6
Category:

less

Transcript and Presenter's Notes

Title: Role Based Security Planning for Lawson Security


1
Role Based SecurityPlanning for Lawson Security
  • Lenny Murney
  • VP Technologies Marketing

2
  • Absolute!
  • An independent Lawson service provider
    specializing in functional, technical and
    operational services
  • Lenny Murney
  • VP Technologies Marketing

3
Agenda
  • Topics
  • What is Lawson 9.0 Security
  • Role Based defined
  • Tasks, Roles and Resources
  • Security Administrator
  • Is reporting available
  • Advantages
  • Considerations

Lawson is a registered trademark for Lawson
CorporationAll other brand or product names are
trademarks or registered trademarks of their
respective companies.
4
Absolute!
  • Lawson Services Group
  • Mentoring
  • Performance Tuning
  • Lawson Reporting Services
  • Monthly Support Agreements
  • Disaster Recovery
  • New Product Implementation
  • Web Portal Expertise
  • Upgrades
  • Java Development
  • Custom Interfaces
  • Custom Development
  • Performance IT
  • A service providing a Support and Controlled for
    Lawson Production Environments.

Lawson is a registered trademark for Lawson
CorporationAll other brand or product names are
trademarks or registered trademarks of their
respective companies.
5
Lawson 9.0 Security
  • Lawsons new security solution
  • Requires System Foundation 9
  • Role based
  • Dynamically driven by rules
  • Built on tasks
  • Access is explicitly granted
  • Users are stored in LDAP
  • Gateway to Single Sign on

6
Role Based defined
  • Rule a prescribed guide for conduct or action
  • Rule a determinate method for performing an
    operation and obtaining a certain result
  • Rule a period during which a specified ruler or
    government exercises control
  • Security
  • based on defines rules
  • assigned by task

7
Task, Roles and Resources
  • Security classes tasks within an organization

8
Task, Roles and Resources
  • Roles are created for each job function

9
Task, Roles and Resources
  • Resources employee assignment

10
Task, Roles and Resources
  • Leverage across product lines

Prod Product Line
Cert Product Line
Dev Product Line
11
Task, Roles and Resources
  • No more dual logons

12
Creating Security Classes
  • Create Security Classes in the Security
    Administrator
  • Can be based on another security class

13
Rules
  • Rules are written in the Security Administrator
  • Rules are assigned to a security class
  • Rules should be dynamic

14
Creating Roles
  • Roles are created in the Resource Manager
  • Role Inheritance
  • Security is granted from child to parent

15
Assigning Security Classes
  • Security Classes are assigned to Roles

16
User Maintenance
  • Users are created in the Resource Manager
  • The new RD30
  • Roles are assigned to users

17
Implementation Strategy
  • Project Kickoff
  • Project Analysis (Whole Project Methodology)
  • Planwho, when, what
  • Security Plan
  • RM and LS training
  • Executeeach business area in a phased approach
  • Security analysis (Detailed Requirements
    gathering)
  • Lawson Security Model (planning session)
  • Controleach business area in a phased approach
  • Proof of Concept (demo, main in each area, most
    restrictive)
  • Build LS and test (phased approach)
  • Implementeach business area in a phased approach
  • Establish users under LS model (phased)

18
Reporting
  • Delivered reports include
  • User Security Report
  • Segregation of Duties Report
  • Service Report
  • Sub-Administrator Reports

19
Implementation Advantages
  • Ongoing administration benefits
  • Single Sign-on (with LDAP bind)
  • Single Self Service user record
  • Sub-Administrator functionality
  • Reporting and Auditing (database, security,
    sub-administrators, etc.)
  • Can load users
  • do not recreate LAUA security classes

20
Implementation Considerations
  • Lawson Security requires much analysis, planning,
    and testing. Plan to allow enough time.
  • Time spent in design up front will be rewarded by
    reduced administration.
  • A phased approach is strongly suggested.
  • Transition to Lawson Security 9.0 can be
    performed user by user.
  • Greatest access wins (be careful with role
    inheritance).
  • DO NOT load existing LAUA security classes into
    Lawson Security.

21
  • Lawson Services Group
  • Operational supportand mentoring
  • Upgrades
  • Enhancements
  • Performance Tuning
  • Performance IT
  • Supporting everything inand around Lawson.
  • Support Agreements

Thank You!
Questions? Lenny Murney Lenny.Murney_at_TeamAbsolute
.com 612.746.4070
Write a Comment
User Comments (0)
About PowerShow.com