module – implement security

9

Upload: arshad-havaldar

Post on 19-Jun-2015

386 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Module – implement security
Page 2: Module – implement security

Role Based Security Pre – Defined roles Installed with CA

Service Desk Levels of CA Service desk Security Create Access Data Types Create Contacts & groups Create Data Partitions

Page 3: Module – implement security

Access Types & Roles are primary components you use to control CA Service Desk Manager Security

Page 4: Module – implement security

Pre- Defines Roles are assigned to align with ITIL v3 best Practices & reduce amount of site-specific customization required

Microsoft Word Document

Page 5: Module – implement security

Object Manager Controls all Service Desk Security

3 Levels of Security System Level : Implemented in Object layer Secures whole collection of objects Implemented by Function Access tab of

an access type

Page 6: Module – implement security

Record Level Security :Controls access to records in DBI TablesImplemented by Data PartitionsImplemented in Logical DB Layer

Column Level Security :Controls access to same field in every Record Implemented by web page adaptationsImplemented in Logical DB Layer

Page 7: Module – implement security

Defining Access type & relating them to contact is key to setup Security in Service Desk

Using Access Types, We can Control all Security related aspects including:

1. Access & Grant levels2. Web Interface Defaults3. User Authentication 4. Internal Logs & Function Access Privileges 5. Data Partition

Page 8: Module – implement security

Users are defined as Contacts in Service Desk

Group is a collection of users that represent a specific area of responsibility in Service Desk

A user’s contact record identifies all info that system need

Group enables you to assign responsibility for resolving a ticket when the responsibility is shared among individuals

Page 9: Module – implement security

Implement Record level security in Service Desk

Purpose is to restrict access to some records in DBI Tables

Data Partition contains set of constraints, Each Constraint identifies controlled table that’s being restricted with Constraint Type & Test

Constraint type specifies what user can do in data partitions

Constraint test is like a PASS/Fail test to restrict user action