Security Department

Overview: The Security Department Operational Manual

Version: 3.0

This document acts as the primary resource for the Security Department in regards to departmental policy and guidance. (In the original document, tabs on the left sidebar are used to move from point to point.) The manual is split into two parts:

• Policy: covers all actively upheld policies of the department.
• Guidebook: covers all essential guidelines, regulations, and operational info for the Security Department.

§1: Security Structure

§1.1: Department Hierarchy

The department hierarchy, from highest to lowest:

1. Security Administration
2. Security Command
3. Security Senior Personnel
4. Security Personnel

§1.2: Department Structure

§2.1: Department Standards

Expectations

• All security personnel are expected to adhere to a high standard of conduct to the operational manual as well as the master guidelines.
• All security personnel are expected to maintain a level of respect and manners to other personnel on-site and within the communications.
• All security personnel are to never take any actions that may cause interdepartmental conflict that may destabilize relations.
• All security personnel are to stay within full compliance of Foundation ethics and law, and departmental policy.
• All security personnel are to wear the morph designated to their rank.

Communication

• Your communication as personnel of the Security Department is to always be kept very minimal; in areas where immediate combat or emergency response is likely, communication with civil personnel should be kept minimal.
• Unless in circumstances as listed in this section, personnel should always speak within teamchat for communication between security personnel.
• Communication with Class-D personnel is to be kept to an absolute minimum; the only permitted circumstances are:
  • Issuing orders to Class-D personnel.
  • Answering questions that relate to the joining of the Foundation.
  • Issuing warnings to Class-D personnel.
• Communication within the radio should only ever be used for operational purposes; you are to never converse within the personnel nor combative channels, under any circumstance.
• During any sort of event, that being a riot or a raid, all security personnel are to only speak within the combative radio frequency. This is mandatory.

Jurisdiction and Authority

• The Security Department holds primary authority during standard site operations for these listed areas:
  • Class-D Containment Zone
  • Light Containment Zone
  • Civil Sector
• The Mobile Task Force holds primary authority during standard site operations for these listed areas:
  • Medium Containment Zone
  • Biohazard Containment Zone
  • Surface Zone
• Within the event of riots, hostage situations, and raids, SIU may exercise authority over department personnel; security personnel must:
  • Abide by all orders by SIU personnel that are lawful and in relation to the circumstances listed.
  • Not obstruct duties of SIU personnel.
• Within the event of a riot in specific, SIU takes primary authority over the Class-D Containment Zone.
• Within the event a riot exceeds LCZ and makes its way towards MCZ overwhelmingly, MTF Xi-8 may take priority in combating the riot.
• Within the event of raids and containment breaches, MTF may exercise authority over department personnel; security personnel must:
  • Abide by all orders by MTF personnel that are lawful and in relation to the circumstances listed.
  • Not obstruct duties of SIU personnel.
• Please refer to the Code of Ethics for guidance on permitted and restricted areas.

§2.2: Disciplinary Policy

Disciplinary Fundamentals

• The authority in which discipline shall be executed is as goes:
  • The Departmental Overseer, Security Colonel, and Security Lieutenant Colonel shall be considered disciplinary oversight.
  • Security Majors and Captains shall be considered disciplinary inspectors.
  • Security Lieutenants and Sergeants shall be considered disciplinary enforcers.
• Disciplinary enforcers shall have the authority to detain any personnel a part of the Security Department within the circumstances of reasonable suspicion or the witnessing of breach of departmental policy.
  • Detainment may include the cuffing of the suspected individual.
  • Detainment shall only be used for the purpose of internal investigation of the departmental offense.
  • Detained personnel shall not be detained for unnecessary periods of time.
• Disciplinary inspectors are charged with the responsibility of reviewing internal investigations presented by disciplinary enforcers.
  • Disciplinary inspectors shall have the authority to enact discipline without review, within correct conduct.
• Disciplinary oversight shall be charged with the responsibility of upholding correct conduct within disciplinary action.
  • Disciplinary oversight shall have the authority to absolve, lift, and alter any and all internal departmental disciplinary actions, regardless of reason.
  • Disciplinary oversight shall have the authority to enact discipline without review, for any reason.
• Disciplinary inspectors shall have circumstantial immunity to internal departmental policy, requiring investigation by disciplinary oversight.
• Disciplinary oversight shall be immune to all internal departmental policy that does not conflict with Foundation ethics and law.

Sentencing Information

Present departmental punishments:

Offense Information

Disciplinary Appeals

• Currently, the Departmental Overseer, Security Colonel, Security Lieutenant Colonel, and a select Major make up the individuals who review disciplinary appeals.
• Disciplinary appeals are to be filed through the ticket system within the department Discord.
• All appeals will be heard, aside from as listed:
  • Will not be heard if it has been more than 30 days since the offender was notified of their offense.
  • Will not be heard if the defense does not challenge the guilt or correctness factor of the decision.
  • Will not be heard if the punishment was cited as unappealable.
  • Will not be heard if the action taken on the offender was made by the Ethics Committee, the O5 Council, the O5 Representative of the Security Department, or the Internal Security Department.

§2.3: Termination Policy

• Security Department personnel have authorization to use force against Class-D when acting under the orders of a member of departmental command. The declarant of the order is liable for the actions undertaken, and any ethical violations will fall solely on them.
• The ethical restraints on the declarant are relative. If the Overseer issues the order, for example, no order can be considered unethical as the Council sits above the Code of Ethics. However, if a Lieutenant issues the order, the action must fall under acceptable uses of force as set out by the Code of Ethics.

§3.1: Escorting

General Information

• Security Guard+ may escort tests to the LCZ, and escort MD checkups.
• Security Senior Guard+ may escort tests to the MCZ.
• Security personnel may not proceed with escort requests during site protocols such as:
  • Code Red ‘Pandora’s Box’
  • Code Blue ‘Spartacus’s Folly’
  • Code Superblue ‘Serpent’s Enmity’
  • Code Green ‘Circe’s Monster’
  • Code Black ‘Paradise Lost’
• During MCZ tests, security personnel are to follow all lawful orders given by MTF.
• During MCZ tests, MTF personnel have the authority to forcefully remove you from the relevant zones.
• Active civil events like checkups and tests shall be terminated if:
  • There is imminent danger to the participants of the event or personnel beyond the test’s parameters.
  • In times of emergency, such as protocols, or when directed by personnel of authority.
• Class-D cannot be forced to participate in civil events against their will, unless ordered by Level-5 or higher.
• Class-D chosen for the event are to be authorized, scanned then disarmed, and then briefed. The brief is:
  • “Attention, Class-D. You have been selected for testing. Do not attempt to evade or breach any SCPs. Obey all orders, resisting will result in termination. We are about to begin, follow all instructions, do you understand?”
• Any Class-D misbehaving will only be allowed one single verbal warning.
• Any spectators within the event misbehaving are to be clipped and brought to the attention of their respective departmental command, or the Ethics Committee. The spectator may be removed from the event forcefully or terminated if:
  • Personnel of authority are unavailable and the spectator continues to disrupt the event and misbehave.
  • The spectator is interfering so severely that it poses a threat to the safe containment of the SCP, in which case you may terminate them.
• When an event is over, the Class-D personnel are to be returned to the CDCZ and deauthorized, unless the following is true, in which case they may be terminated:
  • They are under anomalous effects.
  • The event is forcefully terminated by personnel of relevant authority.

Zone Requirements

• LCZ tests require 1 SD per 3 Class-D.
• MCZ tests require 1 SD per 2 Class-D, plus 1 MTF.
• SCP-323 tests require 4 SD per 1 Class-D.
• SCP-914 tests require 2 SD per 1 Class-D.
• For SCP-610, SD should wear hazmat suits located in the laundry room near CDCZ.

§3.2: Riot Response

General Information

• There are two types of riots: normal riots and paid riots. You will know if it is a paid riot by the soundtrack that plays, a notifier, and the timer at the top right.
• Security personnel during a paid riot are to immediately exit the immediate CDCZ area, and retreat to the riot lines.
• Security personnel are not permitted to cross the riot lines until there is 1 minute left on the timer.
• The criteria for something to be considered a non-paid riot is at least 10–15 armed Class-D rioting.
• The authority to call a lockdown during a riot or other correct circumstance is the rank of Lieutenant or higher, or the rank of Intervention Agent or higher.

Paid Riot Procedures

• All security personnel are to immediately exit CDCZ and retreat to the riot lines; all security personnel on the site are to head to the riot lines.
• If available, all security personnel are to join VC during a paid riot.
• Security Cadets may assist in countering a paid riot.
• SIU will hold primary authority during the riot; personnel are to obey all orders given by them.
• SIU will be closer to the main door from the warehouse, while security personnel are to stay behind them if there is a lot of SIU.

§3.3: Breach Response

• During the event of a containment breach, security personnel are to direct all FP towards the breach shelter, and focus their efforts primarily on upholding the containment of the CDCZ to prevent further disaster.
• Security Cadets or Security Guards will be tasked with the protection of the Breach Shelter; there must be a minimum of at least 2 SD at the breach shelter during the breach.
• Security personnel are to obey all orders given by MTF during a containment breach.
• Security personnel may assist in the termination of a 323, 008, or 610 instance if it is within their relevant line of fire, that being in LCZ, CDCZ, or Civil Sector.
• Security personnel are to avoid obstructing the role of MTF during a breach.

§3.4: Checkpoint Operating

General Information

• Throughout the facility, multiple checkpoints have been established for situations in which the site requires increased security. The purpose of these checkpoints is to ensure specific areas are secure from any threats, and/or personnel are permitted within them.
• There are four main checkpoints around the site which Security Department personnel are permitted to station themselves in.
• Checkpoints are referred to as Points, numbered 1–4. When mentioning a checkpoint in-game, whether through the radio or directly, you may abbreviate them to “P#”. (E.g. “Requesting Security to P1”)
• Security Department members holding the rank of Security Senior Agent and above are permitted to station themselves within one of the 4 checkpoints under certain conditions. They are as follows:
  • Class-D Containment is staffed with above 4 active Security members.
  • A Security Lieutenant+ orders to station at a desired point.
  • A Code Superblue “Serpent’s Enmity” is activated.
  • A Level-5 Foundation member requests a checkpoint to be activated.
  • There are excessive reports of disguised Class-D roaming the facility.

Checkpoint Locations

• Point 1 (P1): Located between the Class-D Containment Zone and the Water Room. This is the most crucial checkpoint within the facility, as it secures the main path between LCZ, HCZ, and CDCZ all at once.
• Point 2 (P2): Located to the right of the tram exit (near CDCZ/LCZ). This location is crucial for the protection of the tram station, LCZ, CDCZ, and certain SCP chambers. You may find researchers commonly take this path for their testing.
• Points 3–4 (P3/P4): Both Point 3 and Point 4 are located on the outside of the Control Room. During scenarios where the Control Room requires protection, these 2 points will be used for Security personnel to station themselves within. Point 3 is located near the entrance to LCZ, leading to the Water Room. Point 4 is located near MCZ, leading to the MCZ entrance.

Reference photographs of each checkpoint are available in the original document.

Checkpoint Procedures

1. Assume Post:
   • Arrive at the checkpoint and ensure it is staffed (maximum of 3 Security at one checkpoint).
   • Check that all equipment (doors, scanners, radios, etc.) is functioning.
   • Review any current alerts, lockdowns, or special orders.
2. Monitor Approaching Personnel:
   • Observe all individuals approaching the checkpoint.
   • Watch for suspicious behaviour such as running, bypassing queues, or carrying unauthorized items.
   • Direct personnel to stop at the designated inspection area.
3. Verify Identity:
   • Request identification credentials.
   • Confirm: name, clearance level, department, authorization status.
   • Ensure the credentials match the individual presenting them.
4. Check Access Authorization:
   • Determine the destination the individual wishes to enter.
   • Verify they have the required clearance for that area. (Check the CoE for reference.)
   • Deny access if clearance is insufficient.
5. Process Class-D and/or Tests:
   • Verify escort requirements.
   • Confirm approval from authorized personnel if necessary.
   • Ensure Class-D remain with their escort at all times.
6. Grant/Deny Entry:
   • If approved: open the checkpoint, allow the individual(s) through, and record the entry for future entrances/exits.
   • If denied: inform them of the reason, direct them to the proper authority, and maintain professionalism.
7. Emergency Situations:
   • Follow lockdown procedures.
   • Restrict any non-combative personnel from entering through the checkpoint.
   • Report all sightings of hostile entities, intruders, or containment breaches.
   • Permit passage to only authorized emergency personnel.

Example checkpoint script:

• “Halt. Present identification and state your destination.”
• “Your clearance has been verified. Please proceed through the checkpoint.” (OR)
• “Your clearance is insufficient for this area. Access denied. Please return to an authorized area.”

§4: Equipment Policy

Primary Weapon

• Cadets through Senior Guard are given the VPX-5 Carbine, while Specialists and above are given the HK-440.

Secondary Weapon

• Security personnel are issued the semi-automatic pistol G-20, with higher-ranking members gaining access to the SMG Micro.
• Switching to your secondary is faster than reloading.

Taser

• The Taser allows personnel to ragdoll and apprehend targets without the use of lethal force.
• Combat tasing is not permitted.

Handcuffs

• Handcuffs are used to detain and transport subjects. Equip the tool and interact with the prompt above the individual to apply the handcuffs; they will follow you when you do.
• Combat cuffing is not permitted.
• Combat cuffing refers specifically to the usage of cuffs while someone is actively engaging in combat with you or others. It does not refer to cuffing someone while they are fleeing.

Scanner

• The Scanner tool is used to search the inventory of designated subjects.
• Approaching a player with the Scanner tool equipped will cause an interact prompt to appear over their head.
• The Scanner does not allow for direct confiscation; you must confirm they have contraband, and order the subject to take it out and press ‘G’.
• The Scanner tool may only be used when processing Class-D for tests or searching personnel suspected of being disguised Class-D.

Authorizer

• The Authorizer tool is used to authorize Class-D for tests and other events when needed.
• Authorized Class-D will have a green wristband, and their profile will appear on the side of your screen.
• Unauthorized Class-D will be automatically targeted by roaming security robots.

This section is marked “to be updated” in the source document.

Guidebook: General Guidelines

§1.1: Duties and Cadets

• The primary area in which all security personnel aside from Cadets will be stationed at is the Class-D Containment Zone. All personnel can position themselves wherever, as long as it is in an effective position. Security personnel are not to idle nor be around in other parts of the facility while on team, aside from these instances:
  • CDCZ is staffed with 7+ security personnel.
    • Note: In the event that testing is requested while CDCZ is not staffed at 7, SD may leave CDCZ to escort tests given there are at least 2 SD able to staff CDCZ while the test takes place.
  • Pursuing escaped Class-D.
  • Guarding the breach shelter.
  • Responding to a nearby SCP (323, 008, 610) near the LCZ entrance, elevators, LCZ hallways near the Water Room, at FP Gym, etc.
• During a Code Red, or Code Green, the primary duty of Cadets is to guard the Breach Shelter. There are to be at least 2 security personnel stationed at the breach shelter during these emergency protocols.
• Security Cadets are permitted on-site after they attend their Cadet Orientation; however, they may not go down the elevators without permission from Corporal+, or during listed circumstances:
  • CDCZ is understaffed.
  • Pursuing Class-D.
  • During a Code Blue (riot, paid riot).
  • If authorized under emergency circumstances by a Security Specialist+.
• Security Cadets are automatically authorized into LCZ and CDCZ if there are less than 7 Security online.
• Under normal operations, Security Corporal+ may authorize Cadets into LCZ and CDCZ. Under emergency operations, Security Specialists may authorize Cadets into LCZ and CDCZ.
• Cadet progression is as follows:
  1. Attend a Cadet Orientation.
  2. Complete the Security Cadet Examination.
  3. After both are done, send in a promo request in the correct channel.

§1.2: ID Checks

• Class-D have the ability to wear disguises by interacting with the pile of clothes in the Laundry Room. To counteract this, SD conducts ID checks on personnel when possessing reasonable suspicion.
• Reasonable suspicion is defined as: specific, articulable facts that suggest an individual is disguised.
• Situations fitting this standard could be, but are not limited to:
  • Attire that does not meet the area’s clearance level.
  • Any Foundation Personnel who are not combative personnel who are passing a checkpoint.
  • Any Foundation Personnel who are not combative personnel within the CDCZ.
  • Any Foundation Personnel who are loitering or committing an obvious violation of Foundation law.
  • All non-combative Foundation Personnel who are visibly in possession of a weapon on their back.
  • Any Foundation Personnel seen exiting the Laundry Room or overall CDCZ area without a lanyard on their person.
  • Any reports of disguised Class-D within the area.
• Corporals and above may issue an ID sweep for selected areas, in which all personnel can be ID’d without suspicion.

§1.3: Rogue Personnel

• Rogue Personnel engage in activity that is in clear violation of Foundation law, including but not limited to:
  • Aiding Class-D in escape.
  • Attempted breach of SCPs.
  • Severe disruption to on-site activity.
  • Intentional homicide of other personnel.
• When encountering Rogue Personnel, members are advised to first record, document, and report actions to on-site EC and Officers via radio, then to the EC Discord Tipline prior to intervention.
• Security personnel are authorized to attempt to detain rogue individuals if feasible to prevent further disruptions.
• Security personnel are authorized to terminate rogue individuals if they pose a clear threat to others on-site or to SCPs.

§1.4: Misbehaving Personnel

• Security personnel are to report any misbehaving security personnel with proper proof and information to a Sergeant or higher.
• Misbehaving behavior can be classified as listed, but not limited to:
  • Unauthorized use of force against Class-D.
  • General misconduct.
  • Failing to comply with orders.
  • Any breach of policy listed within the offenses in the disciplinary policy section.
• Violations should be reported by creating a ticket in the Security Department Discord.
• To ensure proper documentation of violations, personnel are advised not to intervene in correcting misconduct themselves unless blatant rogue activity is occurring.
• Instead, personnel are advised to document and report violations to both on-site officers and through the aforementioned tickets.

§1.5: MCZ/BCZ Access

• MCZ access is restricted to Security Lieutenant or higher outside of official events, such as escorts.
• Security Senior Guard or higher is permitted to escort tests into MCZ.
• BCZ access is restricted to Security Colonel or higher outside of official events.

§1.6: Vent Access

• Security personnel are not permitted to access the ventilation network at any of the access points throughout the site unless for the following exceptions:
  • In pursuit of armed Class-D.
  • Responding to an anomaly.
  • When permitted by Sergeant+ or SIU.

§1.7: Personnel Identification

• Members of SD should recognize members of other combative departments to avoid confusion with Hostile Forces. The Mobile Task Forces and their associated duties are:
  • Mobile Task Force Beta-7: responsible for containment of anomalies throughout the site. Their primary post is the Medium Containment Zone and throughout LCZ.
  • Mobile Task Force Xi-8: the primary combative Task Force, tasked with enemy suppression and responding to raids. They are posted throughout the site. Commonly confused with Chaos Insurgency.
  • Mobile Task Force Alpha-1: responsible for the protection of high-ranking Foundation Personnel. They operate on behalf of the O5 Council, and may act with impunity given they are acting within this directive. They are posted throughout the site.
  • Mobile Task Force Omega-12: a special task force composed of reality-bending Foundation Personnel. They are posted throughout the site.
• Members of the Mobile Task Forces can be confused with hostile raiders. The only hostile team on-site is Chaos Insurgency.
• Chaos Insurgency currently spawns inside of the CDCZ vents.

Reference images of the MTF morphs and the Chaos Insurgency uniform are available in the original document.

§1.8: LCZ Sweeps

• Security Department personnel are to periodically sweep LCZ if the CDCZ is fully staffed (6 stationed personnel).
• There will be a maximum of 4 Security Department personnel per LCZ sweep.
• If there are less than 8 guards present, two or three personnel must go.
• You must sweep inside cells and report over the radio any missing SCPs and/or hostiles spotted.
• Prioritize likely areas Class-D may be spotted (SCP-914, MCZ entrance, etc.).

§1.9: Re-containment of SCPs

• Security Department personnel are not to recontain SCPs unless MTF is not available (15 minutes after pinging them).
• Security Department personnel who rank Lance Corporal or higher may minor an SCP that is breached which is not an anomaly actor (put it in a secure area like an empty room or containment chamber).
• Security Department personnel are not to enter MCZ unless escorting. (You are not permitted to enter MCZ for a breach.) Refer to the Code of Ethics to see if you are permitted to enter MCZ based on your clearance level.

§2.0: Anomaly Actor Interaction

• Security personnel present in-game whilst anomaly actors are deployed on-site will be required to follow the presented information. These regulations apply to all classes of SCP (Safe → Euclid → Keter):
  • Security personnel are prohibited from demonstrating any form of hostility towards peaceful SCPs. This includes:
    • Aiming at
    • Shooting at
    • Verbally threatening (e.g. “I’m going to terminate Grug”)
    • Verbally harming (e.g. *steps/kicks/punches* the designated SCP)
    • Verbally insulting/discriminating
  • Security personnel are prohibited from complying with SCP directives that would actively risk the integrity of the Foundation’s security. Examples include:
    • Bringing Class-disposables past restricted areas without explicit permission from Mobile Task Forces or Clearance Level-5 personnel.
    • Breaching SCPs.
    • Utilizing SCPs.
  • Security personnel are prohibited from using Anomaly Actors for malicious intent. This includes:
    • Eliminating individuals who pose no threat.
    • Intentionally breaking the Foundation’s stability.
    • Breaching SCPs.
    • Utilizing SCPs.
    • Allowing hostiles access to restricted areas.
  • Security personnel are prohibited from valuing their life over alternative options when at the risk of death from an SCP.
  • Security personnel are prohibited from following Anomaly Actor directives that violate the Code of Ethics. Refer to the CoE.

Guidebook: Site Protocols

Code Red ‘Pandora’s Box’

In the event of a breach, Security Department personnel should escort all non-combative personnel to the breach shelter. At least two operatives must staff the breach shelter while the remaining default to the CDCZ to prevent Class-D from escaping and interfering with operations. Operatives should refrain from interacting with ongoing MTF containment operations.

Code Blue ‘Spartacus’s Folly’

In the event of a paid riot, all personnel are to immediately exit the CDCZ, retreating to the Riot Lines to contain and hold back the riot. No personnel are to pass the riot line until the timer reaches 1 minute left. Lockdowns may not be initiated during a paid riot.

Code Superblue ‘Serpent’s Enmity’

In the event of a hostile raid, security personnel are to stage at several posts throughout the site, such as chokepoints leading to CDCZ and the LCZ entrance, and overall contain the CDCZ to prevent further chaos.

Code Green ‘Circe’s Monster’

In the event of an outbreak, security personnel are to wear the hazmat suit and prevent the outbreak from reaching CDCZ, as if it does it can result in catastrophe.

Guidebook: Ranks and Requirements

Promotional Requirements

Two rank headers in this table did not survive the document export (they appear between Security Senior Agent and Master Specialist). Consult the original document for the complete table.

Points System

• Points are the main factor used for promotions. You gain one point for the following events:
  • Riot
  • Escorting an event
  • Guarding the breach shelter
  • Responding to a breach
  • Attending a raid
  • Being awarded points by a Sergeant or higher
  • 30 minutes of activity
    • Every 30 minutes consists of 1 point; you are able to achieve multiple points with one log.
• You can gain more than one point for the following events:
  • Mass Deployments (scheduled raids, large events, etc.)
  • Operational Deployments (events hosted on other games)
  • SD-Wide Rally (monthly rally)
  • At default it is two points at minimum, but can be upwards of 3 points at the discretion of the highest-ranking officer at the event.
• Points are logged within the #point-logs channel, with a screenshot with your ID out.

Point log format:

• Username:
• Current Rank:
• Date:
• Event Attended: CHECKUP / BREACH / RIOT (remove the ones that don’t apply)
• Researcher/Doctor (if Checkup): (remove if N/A)
• SCP Breached (if Breach): (remove if N/A)
• RIOT: send proof (remove if N/A)
• Screenshot:

Activity log format:

• Username:
• Current Rank:
• Date:
• Start Time (with timezone):
• End Time (with timezone):
• Total Time:
• Screenshot: (must contain screenshots of both start time and end time)

Promotion Requests

• Personnel are expected to keep track of their own progress. There are various channels for logs; when you request a promotion in #promo-requests, you copy the links of those logs that involved you for proof within the request to meet your requirements.
• If the current user is on LOA (leave of absence), point requests are neither to be used to their benefit nor to be considered.
• If a user is on LOA, point requests are to be denied and nullified.

Corporal Progression

The Security Leadership Academy has been created as a secondary measure to ensure all future candidates of the Security Department’s Non-Commissioned Officer (NCO) positionings, along with all ranks progressing above NCO, are capable of reaching the necessary standards Security Command would like them to achieve. The Security Leadership Academy covets mature, competent, knowledgeable individuals who strive to prove their dedication alongside their commitment to the department. Overseen directly by the Security Department’s HICOM, individuals will go through multiple trials to prove their compassion within becoming an exemplary role model to all Security personnel. Failure is not tolerated within this program; we strive for success.

Requirements:

• Candidates must pass the SLA Entrance application in order to render them capable of being accepted into the Security Leadership Academy.
• Candidates must attain the rank Security Operative before applying. Applying whilst not holding this rank will result in your acceptance being denied and/or voided immediately.
• Candidates are required to have served a minimum of 25 days within the department before acceptance within the Academy is permitted for consideration.
• Candidates are expected to retain an overall acceptable reputation within the department. Constant offenses, reports, or violations under a candidate’s name may negatively affect their probability of acceptance.
• Candidates are required to utilize a microphone in relation to certain sections of the Academy.
• As Lance Corporal, candidates must have co-hosted at minimum ONE event. A multitude of co-hosted events does look good on record.
• All candidates should be 16+.
• Candidates’ Roblox account age should exceed at minimum 2 months. Exceptions are negotiable.
• Candidates’ Discord account age should exceed at least 1 month.

Guidebook: Class-D Containment Zone

Class-D Team Regs

• Within the Security Department, personnel are permitted to go on the Class-D team. However, we require that personnel maintain a ratio of 1:2. That means, for every two Class-D, there needs to be at least one SD.
  • For example, if there are six Class-D on, there must be 3 people on SD.
• You may NOT be on CD team while an on-site event is being hosted (i.e. patrol, rally, etc.).
• Sergeant+ may authorize you to be on the CD team as long as the other two regulations have been met.
• Cadet Orientation does not count unless you are a cadet.

CDCZ Guidelines

• At all times, there must be a minimum of six or seven security personnel within the CDCZ.
• While within the CDCZ, you may not venture off into the cellblocks (past the two corridors) in the far back of the CDCZ unless it is for the following:
  • Pursuing a Class-D.
  • Authorized by a Sergeant+, or an SIU Agent.
• You may not scan any Class-D within the CDCZ except during tests.
• At its most simplified form, the criteria for termination is as follows:
  • If they show anomalous characteristics (this includes reality benders).
  • If they possess a weapon.
  • If they attack anyone, including Class-D.
  • If they pass the termination line.
• Refer to the Termination Policy (§2.3 above) for specific criteria in regards to terminations.

Testing Procedures

• When an appropriate party requests Class-D, this is the process you follow:
  1. Choose Class-D
  2. Authorize Class-D
  3. Bring to Transfer Room
  4. Instruct to line up
  5. Scan
  6. Confiscate if needed
  7. Brief
• For a full understanding of procedures, refer to the Escorting section (§3.1 above).

Guidebook: Site Map and Riot Line

This section of the source document consists of site map and riot line images only. Please consult the original document (linked above) to view them.