Title: |
Privacy, Monitoring, and Access without Consent |
Publication date: |
1/2/2012 |
Effective date: |
3/20/2007 |
BRIEF
Policy Summary
To further the secure and acceptable use of Laboratory Information Technology (IT) at Berkeley Lab, this policy:
- Defines no expectation of privacy in use
- Establishes authority to monitor and consent to monitoring
- Establishes policies for Access without Consent
Who Should Read This Policy
- Employees and affiliates
- Other users of Laboratory IT, including collaborators and visitors
To Read the Full Policy, Go To:
The POLICY tab on this wiki page
Contact Information
Information Technology Policy Manager
Information Technology Division
[email protected]
End Brief
Title: |
Privacy, Monitoring, and Access without Consent |
Publication date: |
1/2/2012 |
Effective date: |
3/20/2007 |
POLICY
A. Purpose
To further the secure and acceptable use of Laboratory IT at Lawrence Berkeley National Laboratory (Berkeley Lab), this policy:
- Defines no expectation of privacy in use
- Establishes authority to monitor and consent to monitoring
- Establishes policies for Access without Consent
B. Persons Affected
This policy applies to employees and affiliates as well as casual users of Laboratory IT, including collaborators and visitors.
C. Exceptions
Not applicable
D. Policy Statement
- Expectation of Privacy
- No Expectation of Privacy: Users have no expectation of privacy when they use Laboratory IT, subject to applicable state, federal, Department of Energy (DOE), and University laws and regulations.
- Authority to Monitor
- Authority: System administrators have limited authority to monitor systems for availability and security; however, only the Chief Information Officer, Laboratory Director, or Deputy Chief Operating Officer may grant broad authority to monitor content and transactions on Laboratory IT for security purposes and acceptable use.
- Minimal Access: Employees engaged in monitoring must access the minimum amount of information necessary to accomplish any monitoring task and must treat information in a confidential manner as appropriate.
- Notice of Monitoring: This policy serves as Notice of Monitoring. Systems with external users must provide notice to these users. Acceptable ways of providing notice include but are not limited to requiring users to sign an agreement or linking to the LBNL Privacy and Security Notice.
- Exceptions: The monitoring or recording of telephone conversations is illegal without the consent of all parties.
- Consent to Monitoring
- Consent: Use of Laboratory IT constitutes consent to monitoring. Any or all uses of Laboratory IT may be intercepted, monitored, recorded, copied, audited, inspected, and disclosed to authorized University, DOE, and law-enforcement personnel.
- Written Consent: Use of Laboratory IT serves as written consent to the requirements and policies of the LBNL Privacy and Security Notice for that system and all other DOE systems.
- Access without Consent
- Background: Access without Consent is access to Laboratory IT that is normally available to a single user without that user's permission. This access occurs for either investigations or operational necessity and exceeds monitoring activities.
- Authorizations for Access without Consent
- Investigation of Wrongdoing: The Laboratory Chief Operating Officer or Laboratory Counsel must authorize access for purposes of investigation of wrongdoing.
- Legal Requests: Laboratory Counsel must authorize access for legal requests, including requests from law enforcement.
- Operational Access: Any Laboratory employee who needs operational access must first request consent from the individual; if the individual is unavailable, the division director or designee must authorize requests for operational access.
- Operational Changes: Any Laboratory employee who needs access for operational changes must first request consent from the individual; if the individual is unavailable, no authorization is required.
- Fair and Reasonable Access: Employees responsible for authorizing Access without Consent must ensure that requests for access are fair and reasonable, given the potential for abuse inherent in Access without Consent and despite no expectation of privacy in the use of Laboratory IT.
- Least Intrusive Means Possible: Methods of access for operational purposes must be limited to the least-intrusive means possible. For example, it is less intrusive to set a vacation message (an operational change) than to give access to e-mail (operational access).
- Minimal Involvement: To maximize confidentiality, the number of persons involved must be limited to only those required to initiate and conduct access.
- IT Authorized Access Lead (ITAAL): The IT Division must provide a point of contact to provide and/or coordinate the provision of access.
E. Roles and Responsibilities
Employees engaged in monitoring or Access without Consent must adhere to the provisions of this policy. This policy also emphasizes the following roles and responsibilities:
Role |
Responsibility |
Chief Operating Officer |
Approves requests for Access without Consent for purposes of investigating wrongdoing; ensures that requests are fair and reasonable |
Laboratory Counsel |
Approves requests for Access without Consent for legal purposes and to investigate wrongdoing; ensures that requests are fair and reasonable; ensures that requests adhere to applicable laws and policies |
IT Authorized Access Lead (ITAAL) |
Provides and/or coordinates the provision of Access without Consent; assists with identifying the least-intrusive means possible; coordinates Laboratory approach to e-Discovery at the direction of Laboratory Counsel |
Division Directors |
Ensure that Operational Access without Consent is not for investigatory purposes and that requested access is necessary to accomplish the function |
Requestor for Operational Access without Consent |
Ensures that a good-faith effort is made to obtain consent from the individual before requesting Access without Consent; ensures that Operational Access without Consent is not for investigatory purposes and that requested access is necessary to accomplish the function |
F. Definitions/Acronyms
Term |
Definition |
Laboratory IT |
Berkeley Lab-managed IT, including computing devices, networks, services, and accounts |
Access without Consent |
Access, beyond monitoring, to Laboratory IT that is normally available to a single user without that user's permission |
Investigation of Wrongdoing |
Access to identify or detect suspected wrongdoing; examples include examining an employee's e-mail for indication of violations of policy, or searching through network-level records for indications of "time wasting" |
Legal Requests |
Legally enforceable requests, such as a subpoena, search warrant, court order, national security letter, or public records request, and requests for voluntary disclosure of information |
Operational Access |
Access to gather operational information or provide continuity of service; for example, a work document in an individual account |
Operational Changes |
Access required to modify an operational feature; examples include change/activate vacation message for an employee, change outgoing voice mail |
G. Recordkeeping Requirements
None
H. Implementing Documents
Document Number |
Title |
Type |
10.01.005.001 |
Letter granting broad authority to monitor the Computer Protection Program |
Letter |
10.01.005.002 |
Instructions |
|
10.01.005.003 |
Notice |
|
10.01.005.004 |
Procedure |
I. Contact Information
Information Technology Policy Manager
Information Technology Division
[email protected]
J. Revision History
Date |
Revision |
By whom |
Revision Description |
Section(s) affected |
Change Type |
1/2/2012 |
1 |
J. Bonaguro |
Rewrite for wiki |
All |
Minor |
Remove this text after wiki tabs are set. End Policy.
DOCUMENT INFORMATION
Title: |
Privacy, Monitoring, and Access without Consent |
Document number |
10.01.005.000 |
Revision number |
1 |
Publication date: |
1/2/2012 |
Effective date: |
3/20/2007 |
Next review date: |
1/2/2015 |
Policy Area: |
Information Technology |
RPM Section (home) |
Information Management |
RPM Section (cross-reference) |
Section 9.01 |
Functional Division |
Information Technology |
Prior reference information (optional) |
RPM, Chapter 9, Section 9.01 |
Source Requirements Documents
- DOE Office of Science Program Cyber Security Plan, June 2010
- DOE O 205.1B, Department of Energy Cyber Security Program, CRD Section 6
- DOE O 1450.4, Consensual Listening-In to or Recording Telephone/Radio Conversations
- Clause I.124 – DEAR 952.204–77 Computer Security (AUG 2006), as modified by Contract No. DE-AC02-05CH11231, Appendix P, Section 2
Implementing Documents
Document Number |
Title |
Type |
10.01.005.001 |
Letter granting broad authority to monitor the Computer Protection Program |
Letter |
10.01.005.002 |
Instructions |
|
10.01.005.003 |
Notice |
|
10.01.005.004 |
Procedure |
Remove this text after wiki tabs are set. End Document Info.
ADDITIONAL INFORMATION
Title: |
Privacy, Monitoring, and Access without Consent |
|
Document number |
10.01.005.000 |
|
Revision number |
1 |
|
Publication date: |
1/2/2012 |
|
Effective date: |
3/20/2007 |
|
Next review date: |
1/2/2015 |
|
Policy Area: |
Information Technology |
|
RPM Section (home) |
Information Management |
|
RPM Section (cross-reference) |
Section 9.01 |
|
Functional Division |
Information Technology |
|
Author name/contact info |
J. Bonaguro |
|
|
|
|
Revision 0 publication date |
3/20/2007 |
|
Retirement date |
n/a |
|
Prior reference information (optional) |
RPM, Chapter 9, Section 9.01 |
|
|
|
|
Inputs from more than one Functional Area? |
No |
|
List additional Functional Areas & contacts |
|
|
|
|
|
Inputs from more than one Policy Area? |
No |
|
List additional Policy Areas & contacts |
|
|
|
|
|
30-day notification needed? |
No |
|
30-day start date |
n/a |
|
30-day end date |
n/a |
|
|
|
|
LDAP protected? |
No |
|
|
|
|
Need TABL reminders? |
No |
|
Frequency |
n/a |
|
Brief reminder text: |
n/a |
|
|
|
|
Approval Sheet for this revision received (date) |
|
]]></ac:plain-text-body></ac:structured-macro> |
Key labels/tags:
- Information Technology,Information Management
New terms that need to be added to Glossary/Acronym list
Implementing Documents restricted to department/functional use
(optional – these will be used for tracing between requirements and associated documents)
Document Number |
Title |
|
|
|
|
Side bars:
Side bar 1 location (cite by Policy Section # - for example: Section D.2.a)
Sidebar 1 text:
Sidebar 2 location
Sidebar 2 text:
Sidebar 3 location
Sidebar 3 text:
Remove this text after establishing wiki tabs End Additional Information