S6 Department – Access Management Procedures

This is the Document Release Information
Article Number:	7CAV-S6-004
Scope:	S6 Department – Access Management Procedures
Version:	Version 1.1
Effective Date:	06SEP26
Last Modified Date:	06SEP26
Approving Authority:	S6 1IC
Point of Contact:	S6 2IC

Purpose and Scope

This Standard Operating Procedure establishes how S6 verifies, approves, grants, reviews, modifies, and revokes access to systems administered by the department.

It applies to all S6 personnel and all access requests processed by S6.

Governing Requirements

This SOP governs how S6 processes and administers access. It does not establish eligibility for game-administration access.

Eligibility, training, and authorization requirements for game-administration access are established by 7CAV-R-027 (Assignment of Admin Access). S6 must verify those requirements before granting access and may not independently waive or modify them.

Access Principles and Levels

Access must be limited to what is required for the member's assigned duties. Access must not be granted for convenience, status, or anticipated future need.

The following access levels apply:

• Automatic Baseline Access: Access assigned automatically through the member's billet or organizational placement.
• Standard System Access: Routine access required to perform assigned duties.
• Specialized Administrative Access: Elevated access to administrative functions that could affect users, services, or configurations.
• Privileged System Access: High-level access to sensitive systems, security controls, infrastructure, or department-wide administration.

Temporary administrative access is not provided. When additional access is no longer required, it must be revoked.

Baseline Access and Verification

After S1 processes a member's appointment and updates MILPAC, access associated with the billet is normally assigned automatically.

After completing the required onboarding and acknowledging the applicable Initial Counseling Statement, the member must submit an S6 ticket to verify that their baseline access is correct.

Separate Lead approval is not required for access automatically assigned through the member's billet. Any missing, incorrect, or excessive access must be documented and corrected through the ticket.

Additional Access and Approval

A member requiring access beyond their baseline must request it through their Senior. The Senior must confirm the operational need and submit an S6 ticket identifying:

• The member requiring access.
• The system and access level requested.
• The duty requiring the access.
• Any applicable eligibility or training requirement.

For personnel serving as a Senior or higher, the request must be submitted by the next authority in their reporting chain.

Approval requirements are:

• Standard System Access: Applicable Lead approval. The S6 2IC must be notified.
• Specialized Administrative Access: S6 2IC approval.
• Privileged System Access: S6 1IC approval.

Approval authorizes only the access documented in the ticket.

Account and Security Requirements

Accounts must be individually assigned whenever the service supports individual accounts.

Members must:

• Protect their credentials and authentication methods.
• Use multi-factor authentication when required by the service and whenever otherwise practical.
• Not share accounts or credentials.
• Report suspected compromise or unauthorized access immediately.
• Comply with 7CAV-S6-002 (Acceptable Use Policy).

Credentials must not be included in tickets, private messages, source-code repositories, or general documentation.

Access Reviews and Modifications

Access must be reviewed when a member changes billets, duties, teams, or membership status.

Leads are responsible for reviewing access assigned to their teams. The S6 2IC coordinates department access reviews, verifies their completion, and reviews access assigned to Leads.

The S6 1IC must review access assigned to the S6 2IC when the 2IC resigns, transfers, or is reassigned. The Regimental IMO must review access assigned to the S6 1IC under the same circumstances.

Access that is no longer required must be modified or revoked.

Revocation and Immediate Suspension

Automatic access is normally removed through the applicable personnel or billet update.

A Senior or Lead must submit an S6 ticket when manually assigned access must be revoked. The ticket must identify the member, affected system, and reason for removal.

A Senior or higher may request immediate suspension when continued access presents a credible security or operational risk. Immediate suspension requires approval from the S6 2IC or higher and must be documented as soon as practical.

Revocation must not be delayed solely because a routine review or personnel action remains incomplete.

Denials, Reconsideration, and Records

An access request may be denied when the member lacks an operational need, required eligibility, required training, or appropriate authorization.

The denial and reason must be documented in the ticket, and the requester must be notified.

A denied request may be reconsidered only by the next authority in the applicable approval chain. Unrelated personnel must not approve or override the request.

Access requests, approvals, denials, modifications, suspensions, revocations, and reviews must be documented in the applicable ticket or authorized departmental record.