01.02.2014 Views

TABLE OF CONTENTS - Department of Public Social Services

TABLE OF CONTENTS - Department of Public Social Services

TABLE OF CONTENTS - Department of Public Social Services

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Los Angeles COUNTY<br />

<strong>Department</strong> <strong>of</strong> <strong>Public</strong> <strong>Social</strong> <strong>Services</strong><br />

LEADER Replacement System (LRS)<br />

6310<br />

6311<br />

6312<br />

6313<br />

6314<br />

6315<br />

6316<br />

6317<br />

6318<br />

6319<br />

6320<br />

6321<br />

6322<br />

6323<br />

6324<br />

6325<br />

6326<br />

6327<br />

6328<br />

6329<br />

6330<br />

6331<br />

6332<br />

6333<br />

6334<br />

6335<br />

6336<br />

6337<br />

6338<br />

6339<br />

6340<br />

6341<br />

6342<br />

6343<br />

6344<br />

6345<br />

6346<br />

4. The LRS shall include a means to prevent LSOs from<br />

assigning COUNTY-specified security pr<strong>of</strong>iles to Users.<br />

5. The LRS shall provide a unique visual indication (e.g.,<br />

grayed out) for readable fields and screens that are not<br />

updateable by the User, based on the User’s security pr<strong>of</strong>ile.<br />

6. The LRS shall include the ability to define the restrictions<br />

associated with a User’s security pr<strong>of</strong>ile such as access from<br />

an IP address, access to an LRS Application S<strong>of</strong>tware menu<br />

item, type <strong>of</strong> transaction, LRS Data field, and other<br />

COUNTY-specified criteria.<br />

7. The LRS shall include a viewable online history <strong>of</strong> all<br />

changes made by CSOs to the design <strong>of</strong> a security pr<strong>of</strong>ile.<br />

The online history shall include the following:<br />

a. The name <strong>of</strong> the security pr<strong>of</strong>ile;<br />

b. The transactions, windows, screens, fields, and controls<br />

added to, or deleted from, a security pr<strong>of</strong>ile;<br />

c. The User ID and name <strong>of</strong> the CSO making the change(s);<br />

d. The date and local time <strong>of</strong> the change; and<br />

e. The workstation or laptop ID where the change was<br />

performed.<br />

8. The LRS shall allow CSOs full access control to change the<br />

levels <strong>of</strong> LRS Application S<strong>of</strong>tware security without the<br />

assistance <strong>of</strong> technical specialists such as programmers.<br />

9. The LRS shall allow for the creation <strong>of</strong> specific User security<br />

pr<strong>of</strong>iles in order to limit the ability to access certain parts <strong>of</strong><br />

the LRS network and/or the LRS Application S<strong>of</strong>tware,<br />

including menus, screens, windows, and functions.<br />

3.4.1.4. Security Monitoring and Auditing.<br />

This includes the tools for recording and analyzing system events<br />

appropriate to security.<br />

1. The LRS shall utilize appropriate tools to monitor LRS<br />

access, access attempts, and usage.<br />

2. The LRS shall detect and log all unauthorized access<br />

attempts.<br />

3. The LRS shall generate security reports that assist<br />

COUNTY-specified Users and CONTRACTOR technical<br />

personnel in monitoring LRS security.<br />

LRS RFP - Attachment B (SOR) Page 180 November 30, 2007

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!