Deck of Cards |
---|
id | Security for Information Technology |
---|
|
Card |
---|
| Title: | Security for Information Technology | Publication date: |
|
|
...
...
...
2024 | Effective date: | 3/20/2007 |
Anchor |
---|
| SecurityforInformationTechnology-BRIEF |
---|
| SecurityforInformationTechnology-BRIEF |
---|
| BRIEF Anchor |
---|
| SecurityforInformationTechnology-PolicyS |
---|
| SecurityforInformationTechnology-PolicyS |
---|
| Policy SummaryThis policy describes cyber security responsibilities and requirements for |
|
...
Berkeley Lab Information Technology (IT). This includes responsibilities and requirements for: - Individuals and supervisors
- Certain roles such as system administrator, web server owner, and application developer
- Divisions, including division security liaisons and
- The
|
|
...
...
Anchor |
---|
| SecurityforInformationTechnology-WhoShou |
---|
| SecurityforInformationTechnology-WhoShou |
---|
| Who Should Read This Policy- Employees and affiliates who use or manage
|
|
...
...
- Berkeley Lab information
- Employees with additional security responsibilities for
|
|
...
...
- cyber security liaisons or members of
|
|
...
Anchor |
---|
| SecurityforInformationTechnology-ToReadt |
---|
| SecurityforInformationTechnology-ToReadt |
---|
| To Read the Full Policy, Go To:The POLICY tab on this wiki page Anchor |
---|
| SecurityforInformationTechnology-Contact |
---|
| SecurityforInformationTechnology-Contact |
---|
| Contact InformationInformation Technology Policy Manager Information Technology Division [email protected] |
|
...
Card |
---|
| Title: | Security for Information Technology | Publication date: |
|
|
...
...
...
2024 | Effective date: | 3/20/2007 |
Anchor |
---|
| SecurityforInformationTechnology-POLICY |
---|
| SecurityforInformationTechnology-POLICY |
---|
| POLICY Anchor |
---|
| SecurityforInformationTechnology-A.Purpo |
---|
| SecurityforInformationTechnology-A.Purpo |
---|
| A. PurposeThe purpose of this policy is to enable a computing environment for Lawrence Berkeley National Laboratory (Berkeley Lab) that is both open and appropriately secure. Anchor |
---|
| SecurityforInformationTechnology-B.Perso |
---|
| SecurityforInformationTechnology-B.Perso |
---|
| B. Persons AffectedThis policy applies to employees and affiliates as well as individuals with additional cyber security responsibilities for |
|
...
Berkeley Lab Information Technology (IT). Anchor |
---|
| SecurityforInformationTechnology-C.Excep |
---|
| SecurityforInformationTechnology-C.Excep |
---|
| C. ExceptionsThe Berkeley Lab Chief Information Officer, the |
|
...
Chief Information Security Officer, and the |
|
...
Cyber Security Program may approve exceptions to this policy. Anchor |
---|
| SecurityforInformationTechnology-D.Polic |
---|
| SecurityforInformationTechnology-D.Polic |
---|
| D. Policy Statement Anchor |
---|
| SecurityforInformationTechnology-D.1Empl |
---|
| SecurityforInformationTechnology-D.1Empl |
---|
| D.1 Employees and Affiliates- Everyone Is Responsible for Security.
|
|
...
...
- cyber security is a line-management function at Berkeley Lab. Employees and affiliates are responsible for the security of computers and devices that they use or manage. They must take appropriate steps to secure
|
|
...
...
- information that they create, possess, manage, or have access to in connection with their
|
|
...
- employment or research.
- Authorizing Access to IT Resources. Employees and affiliates may authorize the use of
|
|
...
- Berkeley Lab IT that they manage. When authorizing use, employees and affiliates assume cyber security responsibility for the use and/or user and must ensure that
|
|
...
- Berkeley Lab IT policies are communicated to the user and followed in the course of granting access.
- Reviewing Authorization. After authorization, employees and affiliates must review access on a schedule appropriate to the risks presented by the service or system.
- Cyber Security Requirements. Employees and affiliates must ensure that computers and devices they use or manage meet the
|
|
...
...
...
- Cyber Security determines are necessary to secure the Laboratory.
- Minimum Security Requirements. Minimum security requirements protect both the integrity of Laboratory
|
|
...
- information and our network by providing a baseline level of protection for devices.
|
|
...
- Requirements may include training, security patches, passwords, media protection, anti-virus protection, physical protections, and network access.
- Role-based Security Requirements. Certain roles require additional security requirements to protect
|
|
...
...
- information. Roles include system administrators, web server owners, and application developers.
- Other Requirements. Employees and affiliates must adhere to additional requirements, standards, and procedures that
|
|
...
- Cyber Security determines are necessary to protect
|
|
...
...
- information. Additional requirements are available on the
|
|
...
- Cyber Security Requirements page.
- Reporting Cyber Security Incidents. Employees and affiliates must follow the appropriate procedures to report cyber security incidents, including the loss or theft of
|
|
...
...
- information.
Anchor |
---|
| SecurityforInformationTechnology-D.2Labo |
---|
| SecurityforInformationTechnology-D.2Labo |
---|
| D.2 Laboratory Management- Supervisors and managers must provide adequate oversight to ensure that employees and affiliates under their management are taking appropriate steps to secure
|
|
...
...
- information throughout its lifecycle.
- The division or department director must ensure that the division adheres to policies, requirements, and procedures related to securing
|
|
...
...
- information.
- The division or department director must designate a
|
|
...
- Cyber Security Liaison who has authority and responsibility for coordination of
|
|
...
- cyber security activities.
Anchor |
---|
| SecurityforInformationTechnology-D.3Exce |
---|
| SecurityforInformationTechnology-D.3Exce |
---|
| D.3 Exceptions and Enforcement- Exceptions to Cyber Security Requirements
- Some systems, most commonly scientific ones, are unable to meet the cyber security requirements. Possible reasons include:
- Technical. For example, a legacy operating system that does not have patches for
|
|
...
- a vulnerability.
- Operational. For example, a device that performs experiments, such as genome sequencing or systems used in the Advanced Light Source (ALS) control, may have uptime requirements such that they cannot be patched or rebooted.
- Cost-efficiency. For example, the cost, either monetarily or for mission reasons, of upgrading a device to meet requirements exceeds the cyber security benefit.
- Exceptions. Employees and affiliates should take a risk-based approach to using exceptions and seek guidance from
|
|
...
- Cyber Security as appropriate.
|
|
...
- Cyber Security may refuse exceptions based on institutional risk or require compensating controls.
- Enforcement. Employees and affiliates who do not comply with this policy may temporarily be denied access to
|
|
...
- Berkeley Lab IT or information and may be subject to other penalties and disciplinary action up to and including termination. Non-compliant devices may be disconnected from the
|
|
...
- Berkeley Lab network at any time and until the device is compliant.
Anchor |
---|
| SecurityforInformationTechnology-D. |
---|
|
|
|
...
4Cybe | | SecurityforInformationTechnology-D.4Cybe |
---|
| D.4 Cyber Security ProgramCyber Security has the authority and responsibility to support the cyber security of |
|
...
...
information. The program must: - Provide general protection for
|
|
...
...
- information that is risk-based, cost-effective, and supports the mission of the Laboratory;
- Establish requirements, standards, procedures, and guidelines to help secure
|
|
...
...
- information and comply with all applicable regulations and requirements;
- Provide information and resources to help Laboratory divisions and employees meet their cyber security responsibilities; and
- Elicit input from divisions and programs on cyber security policies and procedures.
Although |
|
...
Cyber Security supports the cyber security of |
|
...
...
information, ultimate responsibility for cyber security and its implementation rests with each Berkeley Lab employee and affiliate. Anchor |
---|
| SecurityforInformationTechnology-E.Roles |
---|
| SecurityforInformationTechnology-E.Roles |
---|
| E. Roles and ResponsibilitiesEmployees and affiliates must adhere to this policy. The table below describes specific responsibilities, authorities, and accountabilities by role: Role | Responsibility | Authority | Accountability | Director | Oversees site management and operations | Delegates cyber |
|
|
...
security responsibilities (to CIO) | Accountable to DOE and UCOP for site operations | Chief Information Officer (CIO) | - Oversees institutional cyber
|
|
|
...
...
- Oversees cyber security policy and related oversight activities
| |
|
|
...
- the Chief Information Security Officer
- Directs resources to prioritize cyber security efforts
| - Accountable to Director for cyber security performance and policy
|
|
|
...
Chief Information Security Officer (CISO) | - Manages and directs the institutional cyber
|
|
|
...
- security program
- Ensures that the cyber security program is effectively managing risk
- Evaluates overall cyber security posture and direction for
|
|
|
...
- Berkeley Lab
- Recommends cyber security
|
|
|
...
...
| - Directs resources to cyber
|
|
|
...
- security efforts
- Establishes risk management approach
- Establishes cyber security requirements
- Establishes cyber security policy
| |
|
|
...
- cyber security performance
|
|
|
...
Cyber Security | - Develops and operates the institutional cyber
|
|
|
...
| - Recommends and enforces cyber security requirements
| |
|
|
...
- CISO for cyber security performance
|
|
|
...
...
...
...
...
- security program by representing their division
- Communicate cyber security policies and requirements to their divisions
| - Recommend changes to cyber security policy and requirements
| - Accountable to division line management for contributions to cyber security posture
| Supervisors and Managers | - Ensure safety and security of employees and systems within span of control
| - Direct work and resources to operate in a safe and secure manner
| - Accountable to defined line manager for cyber security performance within span of control
|
Anchor |
---|
| SecurityforInformationTechnology-F.Defin |
---|
| SecurityforInformationTechnology-F.Defin |
---|
| F. Definitions/Acronyms |
|
...
Berkeley Lab IT | Berkeley Lab-managed |
|
|
...
information technology, including computing devices, networks, services, and accounts. |
|
|
...
Berkeley Lab information | Information used to accomplish job-related tasks |
|
|
...
. Information may be owned by the Regents of University of California or the Department of Energy. |
Anchor |
---|
| SecurityforInformationTechnology-G.Recor |
---|
| SecurityforInformationTechnology-G.Recor |
---|
| G. Recordkeeping RequirementsNone Anchor |
---|
| SecurityforInformationTechnology-H.Imple |
---|
| SecurityforInformationTechnology-H.Imple |
---|
| H. Implementing Documents |
|
...
...
...
Anchor |
---|
| SecurityforInformationTechnology-I.Conta |
---|
| SecurityforInformationTechnology-I.Conta |
---|
| I. Contact InformationInformation Technology Policy |
|
...
ManagerInformation Technology Division |
|
...
[email protected] Anchor |
---|
| SecurityforInformationTechnology-J.Revis |
---|
| SecurityforInformationTechnology-J.Revis |
---|
| J. Revision HistoryDate | Revision | By whom | Revision Description | Section(s) affected | Change Type |
|
|
...
...
...
0 | J. Bonaguro | Rewrite for wiki ( |
|
|
...
...
...
...
1 | J. Bonaguro | Rewrite for wiki ( |
|
|
...
All
...
Minor
...
policy) | All | Minor | 2/5/2014 | 1.1 | J. Bonaguro | Periodic review | All | Minor | 3/30/2017 | 1.2 | S. Lau | Editorial updates | All | Minor | 6/15/2021 | 1.2 | A. Sultan | Periodic review. No changes. | All | Editorial | 8/9/2024 | 1.3 | A. Sultan | Periodic review: R&Rs update. No policy changes. | E | Editorial |
|
Card |
---|
label | Document information |
---|
| Title: | Security for Information Technology | Document number | 10.01.002.000 | Revision number | 1.3 | Publication |
|
|
...
...
...
...
2024 | Effective date: | 3/20/2007 | Next review date: |
|
|
...
...
8/2027 | Policy Area: | Information Technology | RPM Section (home) | Information Management | RPM Section (cross-reference) |
|
|
...
|
| Functional Division | Information Technology | Prior reference information (optional) |
|
|
...
Anchor |
---|
| SecurityforInformationTechnology-SourceR |
---|
| SecurityforInformationTechnology-SourceR |
---|
| Source Requirements Documents |
|
...
...
- Cybersecurity Program, CRD
- DOE P 205.1, Departmental
|
|
...
- Cybersecurity Management Policy (cancelled on 9/23/21)
- UCOP IS-3, Electronic Information Security
Document number | Title | Type | 10.01.002.001 | Minimum Security Requirements | Requirements | 10.01.002.002 | Role-Based Security Requirements | Requirements | 10.01.002.003 | Security Requirements | Requirements |
|
|
...
Show If |
---|
| Card |
---|
label | Additional Information |
---|
| Title: | Security for Information Technology | Document number | 10.01.002.000 | Revision number | 1.3 | Publication |
|
|
|
...
...
...
...
2024 | Effective date: | 3/20/2007 | Next review date: |
|
|
|
...
...
...
2027 | Policy Area: | Information Technology | RPM Section (home) | Information Management | RPM Section (cross-reference) |
|
|
|
...
Sections 9.01 and 9.02
| Functional Division | Information Technology | Author name/contact info |
|
|
|
...
...
...
|
| Revision 0 publication date | 3/20/2007 | Retirement date | n/a | Prior reference information (optional) |
|
|
|
...
RPM Sections 9.01 and 9.02
...
...
|
|
|
| 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 |
|
|
|
...
...
...
...
|
|
| Need TABL reminders? | No | Frequency | n/a | Brief reminder text: | n/a |
|
|
|
...
...
|
| Approval Sheet for this revision received (date) |
|
|
|
...
...
Note: author is responsible} |
|
|
|
...
Anchor |
---|
| SecurityforInformationTechnology-Keylabe |
---|
| SecurityforInformationTechnology-Keylabe |
---|
|
|
|
|
...
Key labels/tags:- (Policy Area 1), (Policy Area 2), (Section)
Anchor |
---|
| SecurityforInformationTechnology-Newterm |
---|
| SecurityforInformationTechnology-Newterm |
---|
| New terms that need to be added to Glossary/Acronym list: Anchor |
---|
| SecurityforInformationTechnology-Impleme |
---|
| SecurityforInformationTechnology-Impleme |
---|
| Implementing Documents restricted to department/functional use(optional – these will be used for tracing between requirements and associated documents) 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: |
|
|
...