Security Personnel §1
On-site Regulations §1(a)
All Foundation Documentation should be followed at all times, including The Code of Ethics, Global Raid Regs, Solitary and Termination Criteria, and Combative Raid & Riot Procedures.
Security Personnel are not to state or display excessive or hostile immaturity, unprofessionalism, discriminatory, NSFW, or terrorism. This excludes friendly banter which may be concluded if the aggravated states that they did not view it as banter.
This includes behavior, emotes, and what you do/wear.
Security Personnel must perform basic English spelling within public chat.
Security Personnel may talk with other personnel freely unless it actively disrupts their duties or hinders their effectiveness.
All Security Personnel are obligated to comply with SD Superiors that are Sentinel+ on-site. Deviations may occur within other Official Security Documentation or Sections. If you believe a order is disregarding guidelines, comply with it and report to Security High Command or the overseer of the department.
Detachment command may overrule if an order pertains to their detachment.
Detachment members may hold similar authority to Sentinel+ IF a certain duty requires external help. (E.I Hostage sits for SRU, Rogue catching for MP) to a reasonable degree. Inspector+ may overrule.
Reasonable is defined as any order that can be performed without disrupting site operations or involving un-needed personnel following the duty pertaining the hierarchy of that set duty.
Base Security Command ranking higher than the initial member ordering excluding §1.6.1 and §1.6.2 may overrule.
Equipment is not to be abused by members of the Security Department at any time.
Security Personnel are not allowed to interfere with hostage situations unless they're required to, authorized by the respective authorities outlined in Hostage Guidelines, or it's deemed invalid.
Members of the Security Department are disallowed from using SCP Items or SCP Given Items.
Base Security High Command+ may use SCP-662.
Security Personnel should not intentionally put themselves in harm's way in order to justify an action which would be otherwise prohibited.
Security Department Personnel are prohibited from retaliating against any individual who shoots them in crossfire.
13. Hiding SCP boxes from Loading Bay is prohibited.
Private Server Regulations §1(b)
Security Personnel should avoid disrupting hosted events whether internally or externally.
Security Personnel must not harass others, discriminate, or talk about NSFW topics in a private server.
Security Personnel are not to state or display excessive or hostile immaturity. this excludes friendly banter which may be concluded if the victim states that they did not view it as banter.
This includes behavior, emotes, and what you do/wear.
Discord/Application Regulations §1(c)
Security Personnel may not harass or discriminate others in any form within the Discord.
Security Personnel are responsible for any actions that occurs within their account including discharges.
Security Personnel are expected to follow all channel rules and use them for their intended purpose.
Should a member be caught saying derogatory terms prior to joining to an external individual not within the DM/Conversation within Discord with SD unable to identify whether it's consensual or not, Security Command may remove them if found under a 12 month period.
Real life crimes of any sort will result in an immediate blacklist.
Security Personnel are disallowed from promoting terrorism within the Discord.
Security Personnel may received a 7 day suspension if they attempt to discharge without completing their expected punishments.
Goes in effect if you rejoin the Security Department
Upcoming Security Personnel and current Security Personnel may not use AI within their application of any kind and may be blacklisted up to 1 month.
Upcoming Security Personnel and current Security Personnel may not perform troll submissions within applications of any kind and may be blacklisted up to 1 month.
Security High and Central Command §2
Security Inspectors are expected to prioritize the Main Security Force over any other subdivision when needed. DA
Security Inspectors are expected to oversee and only interfere with Detachment Command when absolutely necessary. DO
Security Inspectors are expected to uphold their general duties as High Command and not remain extended absence without notifying. DO
Security Inspectors and Chief of Security are expected to update the population of the Department regarding major finalized plans to the best of their ability. DA
Security Inspectors and Chiefs are responsible for ensuring that day-to-day department operations and security operations on-site are running smoothly and up to a high standard of quality. D&PA
Security Inspectors and Chief of Security are expected to update their public list of plans atleast once bi-weekly. DA
The Chief of Security is expected to upkeep the department and address crucial concerns within the Department's infastructure. DO
The Chief of Security is expected to notify those below when possible and remain a level of publicity where Security Personnel are acknowledged. DO
Universal Command and Academy Students (UCAS) §3
UCAS are expected to oblige with any order provided by Security High Command and above. D&PA
UCAS acknowledge that they're held to a higher conduct compared to others and may be subjected to harsher punishments D&PA
UCAS acknowledge that Academy Command/Staff hold the authority to conduct investigations and check in on conduct within all Discord servers if needed. D&PA
This excludes any form of Hearings and/or Questioning via force.
UCAS acknowledges that Security High and Central Command hold the authority to remove any member under a vote of no confidence if 100% is agreed upon to remove under supporting evidence. DO
UCAS acknowledge that a suggestive or hostile character and conduct may impact the Security Department regardless if it was under digital media or on-site and may be subjected to a harsher punishment. D&PA
UCAS acknowledges that the Security Chief hold the right, if they view a member to be inadequate within the UCAS, to remove or demote them without the need to explicitly state a violation of the guidelines or provide hard-proofed evidence if it is evident that they have lacked in their position and the Overseer of the Security Department agrees of their incompetency.
D = Discord
& = And
P = Private Server
A = Also
O = Only
This Key serves as where expectations are held, if no letter is attached next to an expectation, Security personnel may only need to abide it on-site.
Security Officer+ are able to issue punishments.
Punishments are able to be handed for breaking the Security Department Master Guidelines, Code of Ethics and any other legislative document under the Foundation.
Only Written Warning's are able to be reset after 2 months of clean service in the Security Department. In addition, Security Seniors are subject to higher standards and as such, they will be subject to harsher punishment.
Security Personnel have the right to be notified of their punishment and how they're able to appeal their punishment.
Security Department Members who receive laps as part of their punishment will have 1 week to complete them. Failure to do so will result in a suspension until completed.
If your hearing has been accepted by the Internal Tribunal Department, you may not abide this time limit.
The following punishment levels are able to be handed out.
Site protocols are activated using On-Site terminals around the facility with varying sets of Authority. Security Personnel should deviate from base procedures if an authoritative figure tells him to do so based on the corresponding hierarchy.
Security Personnel are expected to resume duties outlined within Security Duties.
If the lights on-site perform a blackout, Security Personnel should continue as normal.
Security Personnel should follow the following hierarchy.
Chief > Inspector > Officer > Sentinel > Senior > Base SD
Breach §2
Security personnel should perform either of the following areas correspondent to their rank following a priority list 1st to last:
Manned Control of the Hamilton Office Complex's Blast Door.
Manned Control of the Civil Sector Gate. (Security Senior+)
Providing support to the Class-D Containment Zone
Guard+ / S.R.U
Manned Control of the Breach Shelter's Blast Door.
Guarding of the Cleanrooms.
Retrieving personnel outside of the Hamilton Office Complex
If an Eta-9 member reports a breach but is unable to activate the on-site protocol, Security Personnel should treat it as a regular Breach.
Security Personnel should close the corresponding Door/Gates if:
Close the Hamilton Office Complex's Blast Door if a Breached SCP is located within the Civil Sector or within Train Tunnels.
Close the Civil Sector Gate if the SCP is approaching or near the Civil Sector Gate.
Close the Breach Shelter's Blast Door if the SCP is located within the Civil Sector or within Train Tunnels.
3.1. Security Personnel must open if the following individuals request:
MTF Operative+
Security Class-4+
Non-Hostile SCP's
SD Sentinel+
SRU Sergeant+
MP Lieutenant+
Security Personnel may treat the Military Police as an authoritative figure of the Civil Sector unless Eta-9/Security Sentinel+ orders otherwise.
Operational Procedures, [Section-1], §1.6 is voided during breaches.
Security Personnel must acknowledge that the Breach Protocol is considered an Alarm Protocol.
The Security Response Unit and the Military Police are in charge of handling their own procedures within their respective documentation and may deviate from set rules and procedures except rules that involve the hierarchy and handling of authoritative figures.
Should Breach Procedures fail, Security are to stay within spawn until an authoritative figure within the Hierarchy deems it clear.
Security Personnel should follow the following hierarchy:
MTF Field Chief/Major > Security Chief > Eta-9 > MTF > Inspector > Officer > Sentinel
10. Containment Breach Response Hierarchy:
Eta-9 > Delta-1 > Lambda-7
Civil Sector Gate
Hamilton Office Complex's Blast Door
Breach Shelter's Blast Door
Riots/Raids §3
Security Personnel should equip the beanbag during the Riot Protocol
Security Personnel should avoid attacking Solo Raiders while escorting, should a see one, you should:
Report within the radio and location of the Solo Raider
If the Solo Raider terminates you while you were escorting, clip and report it to
Department of External Affairs;
The Foreign Command that the raider is apart of.
Security Personnel must acknowledge that the Riot Protocol and the Raid Protocol are considered alarm protocols.
Security Personnel should follow the Combative Riot and Raid Procedures.
Security Personnel must understand the area restrictions that is around site. Deviations may occur within other Security Documentation.
CDC Mines/Underground Level
The CDC Mines or Underground Level is considered a "Dead Zone" (Labeled in Red) and Security Personnel are required to have one other combative Personnel with them when entering Dead Zones. Dead Zones are voided during Riots
Rogue Chasing is excluded from this rule for the Military Police.
Seniors are excluded from Dead Zones
Security Response Units are excluded from Dead Zones
Escape Tunnels
MP/SRU are looking for SCP boxes or chasing a Class-D with SCPs.
If MP/SRU are not present, Guard+ are able to enter to sweep for boxes.
MP/EC/SRU/AAC request assistance in catching rogues.
Class-Ds are actively firing from Tunnels
CDC Inner Cells
Off limits unless a Class-D commits actions worth termination,
DFSC Class-D is held up inside.
You are not allowed to spawn camp them.
Class-D staying in their cell <30 seconds are spawn protected. After 30 seconds, you can enter.
CDC Access Road
Off limits to all BSD,
EMS/Detachment access only.
SRU are deploying into the CDC during Protocol.
MP are conducting enforcement duties within the CDC.
Detachments may use the road to transport boxes out of the CDC quickly.
BSD may do so as well if asked to by SRU or MP.
Light/Moderate Containment Zone (Anomaly Containment Hub)
Off Limits unless the SD is escorting a test.
Requires Eta-9 or MP escort.
Security Department personnel may not enter the ACH for any other reason unless explicitly authorized by MTF.
SD must report Hostile sightings to MTF/SRU/MP. They cannot enter to chase any Hostiles themselves unless authorized by Eta-9.
SD must request for MTF to handle any Hostiles within any Containment Chambers (Past Chamber Airlock).
Restricted to Security Junior+,
Requested by MTF. (Required to be escorted as stated above)
Detachments should check their guidelines for more information.
Friendly SCPs §1
SCP-131, SCP-4966 and SCP-343 are considered friendly SCPs and should not be shot at under any circumstances. Should SCP-131 (usually Purple) instances annoy certain SCPs (049, 2561, etc.) or disrupt on-site operations, Security Department members are permitted to fire near the instance or use pepper spray.
Security Personnel are permitted to freely interact with said SCPs should it not interfere with their duties.
However, SD should refrain from purposefully feeding or forfeiting items to instances of SCP-4966, as to minimize the risk of harm towards personnel.
Hostile SCPs §2
SCP-173 and SCP-457 are considered ‘hostile’ SCPs and should not be interacted with under any circumstances for any reason. Upon meeting said SCPs, Security Department members are highly advised to evade their current area as to not interfere with recontainment efforts.
Neutral SCPs §3
SCP-527, SCP-2561, SCP-049, SCP-035, SCP-662 are considered ‘neutral’ SCPs and may ‘breach’ at any time. Security Personnel are to actively communicate the status of said SCPs should Eta-9 Operatives not be present. These SCPs should not be directly shot unless exempted below.
SCP-527, commonly known as “Mr. Fish” is a generally friendly SCP. This SCP should only be shot at if it is actively rogue and shooting at personnel.
SCP-2561, commonly known as “Broadcast” is generally friendly. This SCP actively hunts for SCP-527 and should not be DIRECTLY shot at. Should Eta-9 Operatives be absent, personnel are advised to negotiate with SCP-2561, offering it fish in the CDCZ Cafeteria. Should SCP-2561 persist, you are permitted to shoot around SCP-2561. You are to comply with requests given by SCP-2561 if reasonable.
SCP-049, commonly known as “The Doctor” is generally friendly with personnel. This SCP should always be referred to as “Doctor”. Security Personnel are advised not to interact with the SCP-049 unless spoken to or ordered to do so. Personnel are to abide by all requests given by SCP-049 unless it is deemed ‘unreasonable’
SCP-035, commonly known as “The Mask” is generally friendly with personnel. SCP-035 will be declared breached exclusively by ETA-9 personnel. Security Personnel, even if 035 is harming others, are not to shoot it unless explicitly stated by Eta-9.
SCP-662, commonly known as "Mr. Deeds" or simply "Deeds", is generally passive with all personnel. Deeds is capable of providing virtually anything to anyone at request, SD are not to request items outside of their clearance level as outlined in Chapter 3: Anomalies & Testing of the Code of Ethics. SD are not to shoot Deeds unless confirmed to be hostile (attacking personnel). SD are to cease terminating Deeds once the bell holder is confirmed to of been terminated, or Deeds becomes no longer hostile.
The Security Department has to follow the Solitary and Termination Criteria documented at all times at any point in-time On-Site.
The Document can be found below:
Members of the Security are equipped with tools to - SC Class-Ds.
Security Cadet+ are equipped with a “Strike Clipboard”. The clipboard will show the Class-D and the amount of strikes they are on.
After the Class-Ds has been given 3 strikes and marked for DFSC. You will bring the Class-D close to the cell, when they are given their green uniform . You will release them back into the CDC.
If a Class-D has acquired 4 strikes and are currently SC’ed, you will be able to cuff the CD and go back to the SC area in order to put them in the SC Cells.
DFSC - Due for Solitary Confinement
Security Personnel are equipped with the following weapons:
M1911 - Security Cadet+
M3 Grease Gun - Security Cadet+
Colt M365 - Security Junior+
M16A1 - Security Guard+
Ithaca 37 - Security Guard+
MP5 - Security Senior+
CAR 15 - Security Sentinel+
The Security Department and its detachments are given a variety of different utilities and equipment while on-site with each serving a specific purpose.
Weapon restrictions may be voided when Security Protocol 'Last Stand' is activated. View more information here.
Any Rank with F. attached means it may be used freely by that rank and above.
Handcuffs - Security Junior+
Only be used for Rogues/DFSC/Getting CD for test's.(Excluding Juggernauts)
Strike Clipboard - Security Cadet+
Do not Revenge Strike (Striking a Class D when you Respawn and the Class D is still alive)
Night-stick - Security Cadet+
Nightsticks may not be used on GRU-P.
Nightstick taunting Usage:
Riot Rushing,
Gaining the attention of personnel,
Backing Class-D off the line,
And dispersing large crowds.
Pepper Spray - Security Cadet+
Stunning Class-D (does not apply to juggernauts)
Eg, warning Class-D personnel for violating the termination criteria, searching for SCP-268, etc.
Security Department personnel are to utilize common sense when using pepper spray.
Do not use through walls, doors, etc.
Bean-Bag Shotgun - Security Junior+
May ONLY be used to warn Class-D personnel for violating the termination criteria, Stunning/Ragdolling DFSC Class-Ds, rogue FP or for tests.
CS Gas - Security Senior / F.Sentinel+
In-game protocols only. (Riot, Rise, Breach, etc)
Tall Barricades - SRU | MP
May only be used to create blockades for Civil Events or Block the Guard Line in CDCZ if a riot has proceeded for 10+ minutes.
Sector Gates - Security Senior+
Gates located at the entrance of the Civil Sector and AD Sector
May only be closed during a Breach with Eta-9 authority or with proper reasoning.
CDC Inner Gates - Security Senior+ | SRU Response Agent+ | MP Primary Constable+
Only be used:
If a Riot lasts more than 20+ minutes
During a CDC Lockdown (refer below)
Terminal Protocols
Rise - Security Senior+/Probationary Response Agent/Primary Constable
In terminal enter: protocol Rise on/off
Security Seniors MUST request any objections on the radio before activating/deactivating protocols.
Objections from: Security Sentinel+, SRU, MP Primary Constable+, and MTF must be abided by.
Riot- Security Sentinel+/Response Agent/Primary Constable
In terminal enter: protocol Riot on/off
Blackout Request - Security Officer+
Request within radio "@ets Blackout "Area"
CDC Housing Block Lockdown - Security Officer+ | SRU Senior Response Agent+
Only be used:
If a Riot has occurred for 1+ hour.
Any of the SCP Boxes (including 035s RC Box) have been lost to CDs within the CDC for over 10 minutes, this may only stay on for 10 minutes as to not kill site activity.
Security Inspector+ requires it.
Sector Lockdowns - Security Officer+ | SRU | MP (Exact Ranks may vary)
Only be used:
Formal Events that require Increased Security
Concentrated Area of Hostility for 15+ Minutes (Excluding Juggernauts and Raids)
Uniforms - Security Cadet - Security Guard+
All Uniforms and Gear must tie together, SD may not cross-match by using Peaked Cap with BDU Gear and vice versa. This includes Supporter Gear as well.
Supporter Gear
The Hat/Gear must fit the scenario the individual is in.
Must fit the general wear of the National Guard.
It must fit the 1980s.
Formal Uniforms/Headgear - Security Junior / F.Sentinel+
May be used only for Formal Foundation Events.
THESE DO NOT REFER TO GAMEPASS UNIFORMS
Riot Gear - Security Cadet / F.Security Senior+
May be used during Riots, Breaches, and Raids
Security Personnel are to park properly in designated parking spots. If all designated parking spots are full, Security Personnel may park on a leveled patch of dirt.
SD is not to use vehicles to purposely run over SCPs, Foundation Personnel or Juggernauts.
(Eg, ramming Hostile Juggernauts to disadvantage them by: ragdolling, damaging, immobilizing, terminating them, etc.)
If a Juggernauts has been on-going for 15+ minutes or obtained an SCP item, SRU are excluded and may ram hostile juggernauts freely.
All Vehicles provided to Base Security Personnel may be used freely. Detachments hold their own regulations within their documentation regarding their vehicles.
M274 Mule - Security Cadet+
Able to transport boxes
Willys MB- Security Junior+
Security Van - Security Junior+
A vehicle used for testing.
Security Sedan - Security Guard+
Security Bronco - Security Senior+
Warning: Vehicles have irregular drifting during off-road surfaces, Security Personnel are expected to adapt if needed.
While the Base Security Department currently has no set activity expectations for those ranking Security Senior and below, a constant amount of activity shows command you are willing to progress in the Security Department. Each of the department detachments have their own set quota of expectations, trainings and activity requirements that members must follow along with the ability to file Inactivity Notices. SD High Command and above hold the right to edit, change, or suspend them if deemed reasonable.
Security Command holds you to the right to follow any and all regulations listed in this document. Attempting and using any loopholes in these or other guidelines is subject and ground for punishment.
This document has been reviewed, passed and approved by the following members of Security High Command.