Establishing secure connection…Loading editor…Preparing document…

Fort Bliss Acceptable Use Policy

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

FORT BLISS ACCEPTABLE USE POLICY

NETWORK ENTERPRISE CENTER – FORT BLISS

FOR OFFICIAL USE ONLY

(FOIA Exemption 2, AR 25-55 applies)

Controlled Unclassified Information (See DOD 5200.01)

Reference: AR 25-2 (Information Assurance). A well-protected DoD/Army network enables organizations to easily handle the increasing dependence on the Internet. For a DoD/Army organization to be successful, it needs to integrate information that is secure from all aspects of the organization. The purpose of this policy is to outline the acceptable use of computer equipment within a DoD/Army organization. These rules are in place to protect the employee and the organization. Inappropriate use exposes DoD/Army units to risks including attacks, compromise of network systems and services, and legal issues. This policy applies to all military, civilians, contractors, consultants, temporary employees, and other workers assigned to the DoD/Army organizations.

1. Understanding. I understand that I have the primary responsibility to safeguard the information contained in the Secret Internet Protocol Router Network (SIPRNET) and/or Non-secure Internet Protocol Router Network (NIPRNET) from unauthorized or inadvertent use, modification, disclosure, destruction, and denial of service.

2. Access. Access to this network is for official use and authorized purposes and as set forth in DOD Directives 5500.7-R, Joint Ethics Regulation (JER), AR 25-2 (Information Assurance) and Army network policy and accreditation.

3. Revocability. Access to Army Information Systems resources is a revocable privilege and is subject to content monitoring and security testing.

4. Classified information processing. SIPRNET is the primary classified Information System (IS) for Army units. SIPRNET is a classified only system and approved to process SECRET collateral information as SECRET and with SECRET handling instructions.

a. The SIPRNET provides classified communication to external DoD agencies and other U.S. Government agencies via electronic mail.

b. The SIPRNET is authorized for SECRET level processing in accordance with an accredited SIPRNET Approval to Operate (ATO).

c. The classification boundary between SIPRNET and NIPRNET requires vigilance and attention by all users.

d. The ultimate responsibility for ensuring the protection of information lies with the user. The release of TOP SECRET information through the SIPRNET, or any unauthorized disclosure of classified information (SECRET) on the NIPRNET is a security violation and will be investigated and handled as a security violation.

e. Writing to removable media such as USB and DVD/CD drives is prohibited on SIPRNET without express authorization from the DAA. Read only privileges are not impacted and are allowed for DoD personnel based on existing procedures, need-to-know and mission need.

5. Unclassified information processing. The NIPRNET is the primary unclassified information system for Army units. NIPRNET provides unclassified communication to external DoD and other United States Government organizations. Primarily, this is done via electronic mail and Internet networking protocols such as Web Access, Virtual Private Network, or other approved remote access system.

a. NIPRNET is approved to process UNCLASSIFIED, SENSITIVE information in accordance with AR 25-2 and local automated information system security management policies. A Designated Approval Authority (DAA) has accredited this network for processing this type of information.

b. The NIPRNET and the Internet, for the purpose of the AUP, are synonymous. E-mail and attachments are vulnerable to interception as they traverse the NIPRNET and Internet, as well as all inbound/outbound data, external threats (e.g. worms, denial of service, hacker) and internal threats.

c. Public Key Infrastructure (PKI) Use:

(1) Public Key Infrastructure provides a secure computing environment utilizing encryption algorithms (Public/Private-Keys).

(2) Token/Smart Card (or CAC). The Cryptographic Common Access Card Logon (CCL) is now the primary access control mechanism for all Army users (with very few exceptions). This is a two phase authentication process. First, the CAC is inserted into a middleware (reader), and then a unique user PIN number provides the validation process.

(3) Digital Certificates (Private/Public Key). CAC is used as a means to send digitally signed e-mail and encrypted e-mail.

(4) Private Key (digital signature), as a general rule, should be used whenever e-mail is considered “Official Business” and contains sensitive information (such as operational requirements). Additionally, all emails with embedded hyperlinks and or attachments must be digitally signed. The digital signature provides for the non-repudiation of the message that the sender cannot later deny having originated the e-mail.

(5) Public Key is used to encrypt information and verify the origin of the sender of an email. Encrypted mail should be the exception, and not the rule. It should only be used to send sensitive information, information protected by the Privacy Act of 1974, and Information protected under the Health Insurance Portability and Accountability Act (HIPAA), or identified as For Official Use Only (FOUO).

(6) Secure Socket Layer (SSL) technology should be used to secure a web based (https) transaction. DoD/Army Private (Intranet) web servers will be protected by using this technology IAW DoD/Army PKI implementation guidance.

6. User Minimum-security rules and requirements. As a SIPRNET and/or NIPRNET system user, the following minimum-security rules and requirements apply:

a. I understand personnel are not permitted access to SIPRNET or NIPRNET unless they have met the appropriate DOD and Army personnel security requirements for accessing the system.

b. I have completed the required security awareness-training (Annual DoD Information Assurance Awareness Training or Computer Security for Users) and provided proof of completion to my IASO. IAW AR 25-2, prior to receiving network/system access, I will participate in all DoD/Army sponsored Security Awareness Training and Certification programs inclusive of threat identification, physical security, acceptable use policies, malicious content and logic identification, and non-standard threats such as social engineering. I understand that my initial training certificate will expire one year from the date that I successfully complete training and that I will be required to complete annual refresher training (IAW AR 25-2). I understand that my account will be disabled if I do not complete the annual certification training by the anniversary date.

c. I will protect my logon credentials (passwords or pass-phrases). Passwords will consist of at least 14 characters with 2 each of uppercase and lowercase letters, numbers, and special characters. I am the only authorized user of my account. I will not use my user ID, common names, birthdays, phone numbers, military acronyms, call signs or dictionary words as passwords or pass-phrases. IAW AR 25-2, Chapter 4, Section IV, Para 4-12, passwords should be changed at least every 60 days.

d. When I use my CAC to logon to the network, I will ensure it is removed and I am logged off prior to leaving the computer.

e. I will use only authorized hardware and software on the DoD/Army networks to include wireless technology. I will not install or use any personally owned hardware (including removable drives), software, shareware, or public domain software.

f. To protect the systems against viruses or spamming, I will use virus-checking procedures before uploading or accessing information from any system, diskette, attachment, compact disk, or other storage media.

g. I will not attempt to access or process data exceeding the authorized IS classified level.

h. I will not alter, change, configure, or use operating systems, programs, or information systems except as specifically authorized.

i. I will not introduce executable code (such as, but not limited to, .exe, .com, .vbs, or .bat files) without authorization, nor will I write malicious code.

j. I will safeguard and mark with the appropriate classification level all information created, copied, stored, or disseminated from the IS and will not disseminate it to anyone without a specific need to know.

k. I will not utilize Army or DOD provided IS for commercial financial gain or illegal activities.

l. Maintenance will be performed by the System Administrator (SA) only.

m. I will immediately report any suspicious output, files, shortcuts, or system problems to the SA and/or the Information Assurance Support Officer (IASO) and cease all activities on the system.

n. I will address any questions regarding policy, responsibilities, and duties to my IASO and/or the Network Enterprise Center (NEC) Information Assurance Manager (IAM).

o. I understand that each Information System (IS) is the property of the Army and is provided to me for official and authorized use.

p. I understand that monitoring of SIPRNET and NIPRNET will be conducted for various purposes and information captured during monitoring may be used for possible adverse administrative, disciplinary or criminal actions. I understand that the following activities are prohibited uses of an Army IS:

(1) Unethical use (e.g. Spam, profanity, sexual misconduct, gaming, extortion).

(2) Accessing and showing unauthorized sites (e.g. pornography, E-Bay, chat rooms).

(3) Accessing and showing unauthorized services (e.g. peer-to-peer, distributed computing).

(4) Unacceptable use of e-mail includes exploiting list servers or similar group broadcast systems for purposes beyond intended scope to widely distribute unsolicited e-mail (SPAM); sending the same e-mail message repeatedly to interfere with recipient’s use of e-mail; sending or broadcasting, e-mail messages of quotations, jokes, etc., to multiple addressees; and sending or broadcasting unsubstantiated virus warnings (e.g. mass mailing, hoaxes, auto-forwarding) from sources to anyone other than the IAM.

(5) Any use that could cause congestion, delay, degradation or disruption of service to any government system or equipment is unacceptable use (e.g., video, sound or other large files, “push” technology on the internet and other continuous data streams).

(6) Unauthorized sharing of information that is deemed proprietary or not releasable (e.g. use of keywords, phrases or data identification).

q. I understand that I may use an Army IS for limited personal communications by e-mail and brief internet searches provided they are before or after duty hours, break periods, or lunch time or IAW local policies and regulations, as long as they do not cause an adverse impact on my official duties; are of reasonable duration, and cause no adverse reflection on DOD. Unacceptable use of services or policy violations may be a basis for disciplinary actions and denial of services for any user.

r. I understand that AR 25-2 is the implementation of Federal Law and is punitive in nature. Violations of paragraphs 3–3, 4–5, 4–6, 4–12, 4–13, 4–16, 4–20, and 6–5 of this regulation may be punishable as violations of a lawful general order under Article 92 of the Uniform Code of Military Justice (UCMJ) or under other disciplinary, administrative, or contractual actions as applicable. Personnel not subject to UCMJ who fail to comply with these requirements may be subject to disciplinary, administrative, or prosecutorial actions.

s. I understand that I will not write to removable media on SIPRNET, such as USB or DVD/CD drives unless specifically authorized, in writing to do so by my Command.

7. By signing this document, I acknowledge and consent that when I access Department of Defense (DOD) information systems:

a. I am accessing a U.S. Government (USG) information system (IS) (which includes any device attached to this information system) that is provided for U.S. Government authorized use only.

b. I consent to the following conditions:

(1) The U.S. Government routinely intercepts and monitors communications on this information system for purposes including, but not limited to, penetration testing, communications security (COMSEC) monitoring, network operations and defense, personnel misconduct, law enforcement (LE), and counterintelligence (CI) investigations.

(2) At any time, the U.S. Government may inspect and seize data stored on this information system.

(3) Communications using data stored on U.S. Government information systems are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any U.S. Government-authorized purpose.

(4) This information systems includes security measures (e.g., authentication and access controls) to protect U.S. Government interests; not for my personal benefit or privacy.

(5) Notwithstanding the above, using an information system does not constitute consent to personnel misconduct, law enforcement, or counterintelligence investigative searching or monitoring of the content of privileged communications or data (including work product) that are related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Under these circumstances, such communications and work product are private and confidential, as further explained below:

(a) Nothing in this User Agreement shall be interpreted to limit the user's consent to, or in any other way restrict or affect any U.S. Government actions for purposes of network administration, operation, protection, or defense, or for communications security. This includes all communications and data on an information system, regardless of any applicable privilege or confidentiality.

(b) The user consents to interception/capture and seizure of all communications and data for any authorized purpose (including personnel misconduct, law enforcement, or counter-intelligence investigation). However, consent to interception/capture or seizure of communications and data is not consent to the use of privileged communications or data for personnel misconduct, law enforcement, or counterintelligence investigation against any party and does not negate any applicable privilege or confidentiality that otherwise applies.

(c) Whether any particular communication or data qualifies for the protection of a privilege, or is covered by a duty of confidentiality, is determined in accordance with established legal standards and DoD policy. Users are strongly encouraged to seek personal legal counsel on such matters prior to using an IS, if the user intends to rely on the protections of a privilege or confidentiality.

(d) Users should take reasonable steps to identify such communications or data that the user asserts are protected by any such privilege or confidentiality. However, the user's identification or assertion of a privilege or confidentiality is not sufficient to create such protection where none exists under established legal standards and DoD policy.

(e) A user's failure to take reasonable steps to identify such communications or data as privileged or confidential does not waive the privilege or confidentiality if such protections otherwise exist under established legal standards and DoD policy. However, in such cases, the U.S. Government is authorized to take reasonable actions to identify such communication or data as being subject to a privilege or confidentiality, and such actions do not negate any applicable privilege or confidentiality.

(f) These conditions preserve the confidentiality of the communication or data, and the legal protections regarding the use and disclosure of privileged information, and thus such communications and data are private and confidential. Further, the U.S. Government shall take all reasonable measures to protect the content of captured/seized privileged communications and data to ensure they are appropriately protected.

c. In cases when the user has consented to content searching or monitoring of communications or data for personnel misconduct, law enforcement, or counterintelligence investigative searching (i.e., for all communications and data other than privileged communications or data that are related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants), the U.S. Government may, solely at its discretion and in accordance with DoD policy, elect to apply a privilege or other restriction on the U.S. Government's otherwise-authorized use or disclosure of such information.

d. All of the above conditions apply regardless of whether the access or use of an information system includes the display of a Notice and Consent Banner. When a banner is used, the banner functions to remind the user of the conditions that are set forth in this User Agreement, regardless of whether the banner describes these conditions in full detail or provide a summary of such conditions, and regardless of whether the banner expressly references this User Agreement.

8. Remote access. Remote access will be via virtual private network (VPN). Government owned hardware and software will be used. The employee is the only individual authorized to use this equipment. Access will be as authorized by the supervisor. In addition, the user will not divulge any information that is viewable by the user regarding settings or how remote access is managed to any individual not authorized to have access to that information. Requirements as indicated throughout this AUP are applicable for access to USG resources.

9. Blackberry devices.

a. I will be held responsible for damage caused to a Government system or data through negligence or a willful act.

b. I am not authorized and will not use Bluetooth technology with Blackberry devices except for the authorized CAC sled and wireless headset found on the DISA Unified Capabilities Approved Products List.

c. I will not operate a wireless device in areas where classified information is electronically stored or processed.

d. I will ensure the Blackberry handheld device is cradled or synced at least once every 30 days to the Blackberry Enterprise Server (BES) to receive updated keys and/or software updates.

e. I understand that all charges incurred in excess of the normal monthly service charge will be the responsibility of the Blackberry user. Charges will be incurred for the following misuses of the device: exceeding allocated minutes per month, use of text messaging, downloading of any services, ring tones, games, etc.; neglect or abusive damage to the device or accessory.

f. I have completed wireless training at the IA Virtual Training Web site.

g. I understand that I must immediately notify appropriate site contacts (e.g. IASO, BES administrator, supervisor, etc.) if my BlackBerry is lost or stolen.

10. Short Messaging Service (SMS) on Blackberry/Wireless devices. If authorized to use SMS, I am aware of the following risks when utilizing this service:

a. Messages are not encrypted and copies are stored in memory on the phone and in the wireless carrier database. Sensitive information will not be sent via SMS/Text/Messages/Multimedia Messaging Service (MMS).

b. URL to hacker web sites can be sent to a SMS/Text Message/MMS. If a user connects to the URL, malware could be downloaded on the phone.

c. Executable files (including malware) can be embedded in SMS/Text Message/MMS.

d. Photos sent via SMS/Text Messages/MMS can have URLs to hacker web sites embedded in the photo. When the photo is viewed the phone will connect to web site of the embedded web site.

e. Photos sent via SMS/Text Messages/MMS can have executable files (including malware) embedded in the photo. When the photo is viewed the phone will execute the file.

11. “Road Warrior” Laptop Security. Users of mobile computing devices (laptops, portable notebooks, tablet-PCs, and similar systems) are tasked with the physical security of these mobile devices while administrators must protect the IS from compromise when used as a standalone system or when remotely connected. I have read and understand the BBP, “Road Warrior” Laptop Security, which can be found on the NEC IA Policy SharePoint Portal in the Shared Documents area.

12. Data at Rest. ALARACT 134/2008 has tasked all subordinate commands with the requirement to implement ONE of the three approved Data at Rest (DAR) encryption solutions, which are Microsoft BitLocker, Mobile Armor or Microsoft Encrypting File System (EFS). This includes all mobile computing devices (e.g. laptops, PDAs and Blackberry devices), and all desktop systems with the enabled capability to write to or host USB mobile storage devices.

Unlike BitLocker or Mobile Armor, EFS requires affirmative action on behalf of the end user to ensure important data is encrypted and properly stored. All sensitive information must be stored in the encrypted file directory in order to be properly protected. Individuals who do not take the proper steps to protect sensitive data are subject to administrative, disciplinary, and/or criminal penalties.

If I am using EFS, I understand that I have the following responsibilities:

a. Ensure all compliance with this DAR Policy when using Mobile Computing Devices (MCDs).

b. Ensure files and folders that contain sensitive information are placed into an EFS folder when stored on any form of media to include MCDs and Desktops.

c. Ensure the “My Documents” folder is not encrypted.

d. Ensure domain login based encryption recovery keys (password or non-password protected) are not stored on desktops or MCDs that are used to process or store sensitive information.

e. Ensure encrypted files are not forwarded, saved, or copied to a network share or MCD that is not formatted for NTFS, as it will result in a loss of encryption.

f. When transporting files to another device, ensure the encryption key is imported to the designated desktop or MCD prior to transporting encrypted files. Once a file is encrypted, the user will not be able to access the NTFS files from another device unless the encryption key is imported to the device.

Should you not feel confident that you understand how to properly use EFS, it is your responsibility to contact your local IAM/IASO for further guidance.

13. In accordance with CTO 10-133, writing to removable media on SIPRNET is prohibited unless authorized and approved. I understand that I have the following responsibilities:

a. If authorized and approved to utilize ‘write’ capabilities on SIPRNET, I understand that I must utilize the two person integrity (TPI) rule.

b. I must keep a log of each and every data transfer and ensure all required log items are completed, and that the second person under the TPI rule will witness each and every data transfer and complete the log as a witness.

c. I understand that AR 25-2 is the implementation of Federal Law and is punitive in nature. Violations of paragraphs 3–3, 4–5, 4–6, 4–12, 4–13, 4–16, 4–20, and 6–5 of this regulation may be punishable as violations of a lawful general order under Article 92 of the Uniform Code of Military Justice (UCMJ) or under other disciplinary, administrative, or contractual actions as applicable. Personnel who are not subject to the UCMJ who fail to comply with these requirements may be subject to disciplinary, administrative, or prosecutorial actions.

Unit/Directorate

Date (mm/dd/yyyy)

Last Name, First MI (print)

Rank/Grade

Signature

Phone number (xxx) xxx-xxxx

Enter text✕

What the Fort Bliss Acceptable Use Policy Covers

The Fort Bliss Acceptable Use Policy establishes expectations and rules for authorized use of installation information systems, networks, and computing assets. It defines permitted activities, prohibited conduct, data handling and classification rules, remote access and mobile device requirements, monitoring and privacy notices, and reporting and disciplinary procedures for violations. The policy applies to military personnel, civilian employees, contractors, and affiliates who access Fort Bliss IT resources and supports compliance with Department of Defense guidance and applicable federal laws while preserving mission continuity and cybersecurity posture.

Why a Clear AUP Matters for Fort Bliss

A well‑defined Fort Bliss Acceptable Use Policy reduces cyber risk, clarifies user responsibilities, and supports accountability, audits, and incident response. It helps align everyday user behavior with federal standards, installation directives, and legal requirements while protecting mission data and personnel privacy.

Why a Clear AUP Matters for Fort Bliss

Who Needs to Read and Acknowledge This Policy

The policy applies to multiple user groups across the installation to ensure consistent use and oversight of Fort Bliss IT assets.

  • Active-duty service members with network and system access
  • Civilian DoD employees and Army contractors with privileged accounts
  • Third-party vendors, researchers, and visitors granted IT access

Each group has distinct obligations; coordinated compliance reduces operational risk and supports audits and investigations.

Typical Signatories and Their Roles

IT Security Officer

Responsible for implementing and enforcing the AUP, configuring technical controls, reviewing incidents, and coordinating periodic training and audits. Signs off on policy versions and approves user attestation workflows for their assigned organizational units.

Contractor Manager

Manages contractor access requests, ensures contractors complete required training and attestations, and verifies that subcontractor agreements include appropriate security and handling clauses before granting system privileges.

Core Components of an Effective Fort Bliss AUP

A professional AUP should be concise, role-specific, enforceable, and aligned with DoD guidance and federal law. Include sections on acceptable use, prohibited items, data classification, authentication, incident reporting, and enforcement.

Scope

Defines covered users, systems, and environments; clarifies applicability to on‑ and off‑installation devices.

Acceptable Use

Permitted activities, approved tools, and authorized resource purposes tailored to mission needs.

Prohibited Actions

Explicitly lists disallowed behaviors such as credential sharing, unauthorized scanning, and data exfiltration.

Access Controls

Authentication, MFA, remote access rules, least privilege, and privileged account management requirements.

Monitoring & Privacy

Notification of system monitoring, expectations of limited privacy, and retention of logs and recordings.

Enforcement

Disciplinary measures, reporting escalation, and contract remedies for violations.

Step-by-Step: Acknowledging the Fort Bliss AUP

Follow these steps to review, attest, and record acceptance of the Fort Bliss Acceptable Use Policy using the installation’s approved workflow.

  • 01
    Review Policy: Read the full policy and any role attachments carefully.
  • 02
    Complete Fields: Enter name, rank, unit, and effective date as required.
  • 03
    Select Authentication: Authenticate with DoD credentials or approved MFA method.
  • 04
    Sign and Submit: Apply signature, submit acknowledgment, and save confirmation.

How Electronic Acknowledgment and eSubmission Work

Electronic acknowledgment follows a simple, auditable workflow that captures identity, timestamp, and retention metadata for enforcement and audit purposes.

  • Upload Policy: Admin publishes the latest policy PDF or HTML record.
  • Place Fields: Signature, date, and role fields are positioned for signers.
  • Send to Users: System sends secure signing links or MFA prompts.
  • Store Audit: Signed record and audit trail are retained securely.

Typical Electronic Workflow Settings for Policy Acknowledgment

Standard configuration choices ensure consistent capture of identity and audit data across the installation.

Field Configuration
Authentication Method DoD CAC or approved MFA
Retain Audit Trail Yes — IP, timestamp, and actions
Document Formats PDF/A or secure HTML
Access Control Role-based, least privilege

Technical Requirements for eSubmission and Storage

Use a platform that preserves audit trails, supports DoD authentication, and secures stored records.

  • Supported Formats: PDF, PDF/A, and DOCX
  • Integrations: Active Directory, SIEM, records management
  • Authentication Options: CAC, SSO, MFA

Security Controls and Data Protections to Include

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
Multi-Factor: MFA or DoD CAC required
Audit Trail: Timestamped actions and IP address
PHI Protections: HIPAA BAA when PHI is present
Access Logging: SIEM integration and alerting
Record Integrity: Tamper-evident stored copies

Consequences of Policy Violations

Disciplinary Action: Loss of network privileges
Administrative Sanctions: Counseling or reprimand
Contract Remedies: Contract termination or financial penalties
Criminal Liability: Unauthorized access may trigger prosecution
HIPAA Penalties: Civil fines and corrective plans
Operational Risk: Mission impact and data loss

Common Errors to Avoid When Completing the AUP

  • Using personal email or unauthorized cloud storage for Fort Bliss data, creating uncontrolled copies that complicate incident response and breach notification.
  • Sharing credentials or accounts instead of using individual access; this prevents accurate attribution and violates least‑privilege principles.
  • Failing to report suspected compromise promptly; delayed reporting increases remediation complexity and may violate command reporting rules.
  • Not completing required role‑based training before requesting elevated access, which can lead to improper privilege grants and audit findings.

Practical Tips for Accurate and Efficient Policy Completion

Follow these procedural tips to reduce errors, speed onboarding, and maintain a reliable audit trail for attestation records.

Keep Records Consistent
Use the same official name and unit identifier across all DoD systems and attestations to avoid mismatches during audits or background checks.
Use Approved Authentication
Authenticate with CAC or approved MFA when signing; this strengthens attribution and simplifies verification of the signer’s identity.
Archive Audit Evidence
Store signed acknowledgments together with audit logs, timestamps, and access-control metadata in a records management system to support compliance reviews.
Schedule Regular Reviews
Review and reissue the AUP annually or after material changes to systems, applicable regulations, or operational requirements.

Key Deadlines and Review Schedules

Maintain a clear schedule for distribution, training, attestation, and policy review to ensure continuous compliance and timely updates.

Policy Publication Date:

Date when the current AUP version is released to users

Mandatory Acknowledgment:

Users must acknowledge within 30 days of publication

Annual Review:

Policy reviewed and reauthorized at least yearly

Training Completion:

Role-based training due within 45 days of assignment

Incident Reporting Deadline:

Report suspected compromises immediately per installation guidance

Typical Policy Lifecycle Milestones

Track the AUP from draft through implementation and regular review so stakeholders can anticipate reviews, approvals, and refresh cycles.

01

Drafting and Consultation

Stakeholders draft policy text and collect legal and operational input.

02

Approval and Signoff

Command leadership and legal counsel approve the final policy version.

03

Deployment and Acknowledgment

Policy published and users complete mandatory acknowledgments.

04

Review and Audit

Periodic audit and updates based on incidents or regulatory changes.

How the Fort Bliss AUP Compares with a Generic IT Security Policy

AUPs focus on user conduct and acceptable resource use, while IT security policies address technical controls. Both are complementary and often cross‑referenced.

Criteria Fort Bliss AUP Generic IT Security Policy
Primary Focus user behavior technical controls
Enforcement personnel actions system controls
Audience all users it staff and administrators
Typical Contents acceptable use rules configuration and hardening

Representative eSignature Vendor Pricing and Capabilities

Comparison of commonly used eSignature vendors and plan entry points; signNow is listed first per procurement comparisons. Confirm current pricing and feature details with each vendor before selection.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day trial Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Real‑World Examples of Electronic Acknowledgment Workflows

Examples show how organizations use electronic signing and audit trails to streamline policy distribution, training, and attestation collection.

Optica Ventures — COO

When rolling out operational acknowledgments we needed a simple interface for staff

  • quick adoption supported faster returns
  • The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers.

Martin Properties — Founder

Property teams required mobile signing for on-site forms

  • offline capability was essential during inspections
  • I can process and execute all of these documents online with 100% compliance and built-in security. Whether on mobile or working offline, I can get forms back to their necessary parties efficiently.

Primary Users Who Complete the AUP

Facility IT Lead

Coordinates deployment and verifies technical controls, ensures systems support required authentication and logging, and validates exported audit trails for retention and review by command leadership and auditors.

Personnel Security Officer

Ensures users complete required training and attestations, maps user roles to access levels, and maintains records to support investigations, background checks, and compliance reporting.

Frequently Asked Questions About the Fort Bliss Acceptable Use Policy

Answers to common questions about acknowledgment, eSigning, retention, and enforcement when using the Fort Bliss AUP.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users