RULES OF BEHAVIOR FOR PRIVILEGED USERS.docx
DOCX document 20 KB Posted
- Solicitation number
- 123A9423Q0050
About this file
This document outlines rules of behavior for privileged users of the Food Safety and Inspection Service information technology systems. Privileged users are defined as those with capabilities such as super user access, ability to change network configurations, install software, or monitor security functions. The rules require privileged users to comply with all security policies, minimize exposure by using separate accounts for privileged and general functions, not share credentials, protect passwords, grant only necessary access permissions, make systems available for review, and immediately report security incidents. Non-compliance may result in warnings, access revocation, reassignment, or termination depending on the severity of the violation.
The related federal contract opportunity is a solicitation from the Department of Agriculture's Food Safety and Inspection Service seeking a vendor to provide data quality services over a base year plus four option years.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 3 - answers to questions from vendors.docx | DOCX document | |
| 2 - answers to questions from vendors.docx | DOCX document | |
| 1 - answers to questions from vendors.docx | DOCX document | |
| Solicitation 123A9423Q0050.pdf | ||
| Solicitation 123A9423Q0050.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
RULES OF BEHAVIOR FOR PRIVILEGED USERS (FEB 2006)
Food Safety and Inspection Service (FSIS) Information Technology (IT) Security Rules of Behavior for Privileged Users Version 1.0 February 10, 2006 Introduction Purpose The intent of the FSIS Rules of Behavior (ROB) for Privileged Users is to recognize the additional responsibilities associated with special access to, and/or privileges associated with, computer resources within the Department or its offices/bureaus/components. The ROB for Privileged Users are in addition to the Computer System User IT Security General ROB to which all DOJ users are subject. The identification of these responsibilities originates in OMB A-130 and is included in the FSIS IT Security Standards.
“Privileged User” defined:
A privileged user is someone authorized access to departmental/office/bureau/component computer resources when that access provides the capability to alter the properties, behavior or control of the information system/network. It includes, but is not limited to, any of the following types of access:
a. “Super user,” “root,” or equivalent access, such as access to the control functions of the information system/network, administration of user accounts, etc.
b. Access to change control parameters (e.g., routing tables, path priorities, addresses) of routers, multiplexers, and other key information system/network equipment or software.
c. Ability and authority to control and change program files, and other users’ access to data.
d. Direct access to operating system level functions (also called unmediated access) that would permit system controls to be bypassed or changed.
e. Access and authority for installing, configuring, monitoring or troubleshooting the security monitoring functions of information systems/networks (e.g., network/system analyzers; intrusion detection software; firewalls) or in performance of cyber/network operations.
Who is covered by these rules?
These rules extend to all privileged users (FSIS employees and contractors) who use any computing resources that support the mission and functions of the Food Safety and Inspection Service. All privileged users will review and provide signature or electronic verification to these rules annually, or upon change of assigned responsibilities, whichever occurs first.
What are the penalties for Noncompliance?
Compliance with these rules will be enforced through sanctions commensurate with the level of infraction. Actions may include a verbal or written warning, removal of system access for a specific period of time, reassignment to other duties, or termination, depending on the severity of the violation. In addition, activities that lead to or cause the disclosure of classified information may result in criminal prosecution under the U.S. Code, Title 18, Section 798, and other applicable statutes.
Responsibilities Complying Privileged Users will:
1. Understand that it is their responsibility to comply with all security measures necessary to prevent the unauthorized disclosure, modification, or destruction of information; follow appropriate system security policies, guidelines and procedures
2. Agree to the FSIS General Rules of Behavior.
3. Minimize exposure and risk by utilizing a separate account to perform privileged functions from general user functions.
4. Not establish or reset any account utilizing the same password for more than one account, and will not provide the user name and password at the same time through the same medium.
5. Grant read or write authority no higher than is granted to him/her (e.g., a component level user administrator shall not assign department level access to another user administrator).
6. Access application programs only for the purpose of creating or maintaining files.
7. Not make modifications to system configurations that could impact availability or security of the system without the approval of the Change Control Board and/or change management process.
8. Not perform general user activities under the same account (user name and password) due to the security requirement for separation of duties.
9. Protect all passwords from unauthorized disclosure.
10. Not share accounts with another privileged user.
11. Make the system available at any time to the SAISO for inspection and review of audit logs.
12. Grant only read-only access to audit files to the Security Auditor; grant access to general system information only if a need-to-know is established and authorization is received from the ISSO.
13. Make the computer(s) available for periodic reviews of the security configuration by independent testers
14. Make changes to system configuration as directed to meet Vulnerability and Patch Management requirements.
15. Immediately record and report any security incidents to the ISSPM.
I acknowledge and understand the responsibilities associated with my role as a Privileged User, and I will comply with the February 10, 2006, Privileged User Rules of Behavior. The Statement of acknowledgement can be provided via email.
Typed Name
| ______________________________________ | _________________ | |
| Signature | Date |
[End of Document]
File details come from the government source that posted it. Updated .