RPM | REQUIREMENTS AND POLICIES MANUAL

Viewable by the world

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Unknown macro: {dojo-tabs}
Unknown macro: {dojo-tab}

Title:

Financial Management System (FMS) User Access Control

Publication date:

1/2/2012

Effective date:

12/7/2011

BRIEF

Policy Summary

Berkeley Lab's Office of the Chief Financial Officer (OCFO) is responsible for managing the secure stewardship and control of its business and financial systems. This includes maintaining clearly defined roles and permissions, setting up and managing user accounts, and ensuring that users' access privileges and assigned roles are approved and consistent with business needs.

Who Should Read This Policy

Any Berkeley Lab employee responsible for managing user access for Laboratory business and financial systems

To Read the Full Policy, Go To:

The POLICY tab on this wiki page

Contact Information

  • Deputy, Chief Financial Officer
  • Manager, Business Systems Analysis (BSA)
Unknown macro: {dojo-tab}

Title:

Financial Management System (FMS) User Access Control

Publication date:

1/2/2012

Effective date:

12/7/2011

POLICY

A. Purpose

This document defines the policy and procedures for managing Office of the Chief Financial Officer (OCFO) business and financial system user access controls, which includes roles and permissions, user accounts, and access privileges that meet approved criteria and are consistent with business needs.

B. Persons Affected

Any Lawrence Berkeley National Laboratory (Berkeley Lab) employee responsible for managing user access for Laboratory business and financial systems

C. Exceptions

None

D. Policy Statement

OCFO is responsible for managing the secure stewardship and control of its business and financial systems. This includes maintaining clearly defined roles and permissions, setting up and managing user accounts, and ensuring that users' access privileges and assigned roles are approved and consistent with business need.

OCFO employs this policy and a variety of security-enforcement mechanisms for controlling system user access. Consistent with the Berkeley Lab Requirements and Policies Manual (RPM), Section 9.01(E), Information and Computer Security Responsibilities, these controls ensure that data resident in systems are sufficiently protected from unauthorized use, alteration, and manipulation; and that users, data owners, and system owners take appropriate precautions to secure business and financial systems and the data contained therein.

Division managers and supervisors are responsible for communicating changes in employee job responsibility and/or employment status to the OCFO System Module Owner, Business Systems Manager, or designee. For some OCFO systems, such as the PeopleSoft Financial Management System, Berkeley Lab's Termination Notification System (TNS) automatically locks the user's account, preventing further system access when an employee is terminated.

OCFO employs a risk-based approach to conducting regular reviews and validations of users' system access.

E. Roles and Responsibilities

Role

Responsibility

Business Systems Analysis Manager or Designee

  • Manages the OCFO business and financial system user access program consistent with this policy
  • Ensures that changes to a user's access and privileges are authorized by the user's manager or supervisor
  • Supports system module owners in defining and documenting requirements for basic and enhanced user access and privileges. Where changes are required, communicates functional requirements to the IT Business Systems unit.
  • Conducts and/or coordinates regular reviews of user access and privileges as defined in the attached Risk Based User Access Program
  • Establishes the time limit for automatic application time-outs and communicates these parameters to IT
  • Manages the use of anonymous accounts

OCFO System Module Owner or Designee

  • Working with the Manager of Business Systems Analysis or designee, defines requirements for user access and privileges related to a specific module. For user roles that provide enhanced user access, the System Module Owner establishes access criteria such as completion of specific skills training, appropriate job titles, or other criteria consistent with business need.
  • Identifies roles that are incompatible due to potential conflict of interest requiring separation of functional duties/responsibilities. Working with the Manager of Business Systems Analysis or designee, ensures that no user has access to multiple roles that, when assigned to the same user, create a potential for conflicts of interest.
  • Reviews and approves requests for enhanced user access. Verifies pre-conditions are met and that the intended system usage is appropriate.
  • Submits approved system access and privilege changes via e-mail to Business Systems Analysis Manager or designee
  • Where applicable, manages user access to division-specific (i.e., row-level) information
  • Periodically reviews and, as necessary, requests changes to basic and enhanced system access and privileges consistent with business requirements
  • Participates in regular user access reviews to help confirm user access and privileges

Supervisors of System Users (including employees and/or affiliates)

  • Request enhanced user access via e-mail from the System Module Owner (or designee), consistent with business need. Ensure that access pre-conditions and criteria (such as completion of specific skills training) are completed by the new user.
  • If a user's assigned job responsibility, organization, or other condition changes, assess whether a change to the user's systems access or privilege level is required. If so, request this change via e-mail from the System Module Owner (or designee).

ITBS (IT Division Business Systems)

  • Based on functional specifications and consistent with this policy, establishes, monitors, and maintains system parameters and controls in support of the requested system access and privileges
  • Supports regular access reviews and confirms access and privileges assigned to ITBS staff
  • Maintains the time limit for automatic application time-outs based on input from Business Systems Analysis Manager


F. Definitions/Acronyms

Term

Definition

Anonymous Accounts

System accounts established to run background processes and/or to test and maintain system capabilities

Enhanced User Access

Additional access to system capabilities that provide read/write permissions and/or read access to sensitive information

System Module Owner

Functional manager with assigned responsibility for a system component consistent with the OCFO Business System Ownership policy

User

Individual employee, affiliate, or system process authorized to access an information system

G. Recordkeeping Requirements

None

H. Implementing Documents

Document Number

Title

Type

11.04.002.000

Business System Ownership

Policy

Multiple

Berkeley Lab RPM Section 9.01, Computing and Communications

Policy

11.04.003.001

Risk Based Review — Categories, Criteria and Review Cycle

Procedure

I. Contact Information

  • Deputy, Chief Financial Officer
  • Manager, Business Systems Analysis (BSA)

J. Revision History

Date

Revision

By whom

Revision Description

Section(s) affected

Change Type

1/2/2012

1

Axthelm

Reformat for wiki

All

Minor

Unknown macro: {dojo-tab}

DOCUMENT INFORMATION

Title:

Financial Management System (FMS) User Access Control

Document number

11.04.003.000

Revision number

1

Publication date:

1/2/2012

Effective date:

12/7/2011

Next review date:

12/17/2012

Policy Area:

Financial Business Systems

RPM Section (home)

Financial Management

RPM Section (cross-reference)

Section 11.49

Functional Division

OCFO

Prior reference information (optional)

RPM Section 11.49

Source Requirements Documents

None

Implementing Documents

Document Number

Title

Type

11.04.002.000

Business System Ownership

Policy

Multiple

Berkeley Lab RPM Section 9.01, Computing and Communications

Policy

11.04.003.001

Risk Based Review — Categories, Criteria and Review Cycle

Procedure

  • No labels

Printed or exported copies of this LBNL policy are not official.
Users are responsible for working with the latest approved revision located in the online LBNL Requirements and Policies Manual.