For information regarding Security Duties, refer to the Department Duties subpage.
§1. Department Conduct
As a member of the Security Department you are expected to follow a set of base rules and regulations at all times.
The Security Guidelines and all Foundation policies listed in the department information channel must be followed at all times, such as the Code of Ethics, CD Solitary & Termination Criteria, etc.
All personnel must be treated with respect. Toxicity and harassment are not tolerated anywhere, in any form.
This includes displaying excessive or hostile immaturity, unprofessionalism, discrimination, and discussing NSFW or terrorism topics.
Security personnel must avoid excessively immature or unprofessional appearance and conduct on-site.
Emotes cannot be used except for basic gestures such as wave and salute.
All global and radio messages by security on-site must be comprehensible and not use slang terms and acronyms. (ex. "btw," "wyd," etc.)
Security personnel may speak freely to Class-D and other Foundation Staff unless it is obstructing security duties.
On-site equipment is not to be abused by security personnel on-duty or at any department events.
Security personnel must not equip SCP objects, or items given by SCPs for personal use or without official reason.
SCP Boxes may not be hidden at anytime.
Security Inspector+ may use SCP-662 in accordance with the Code of Ethics.
Security personnel must interact with SCPs in a respectful and proper manner, as guided in the Operational Standards.
Security personnel must comply with combative superiors, Security Sentinel+, in accordance with the Operational Standards.
If you believe an order is unlawful, follow the order but take evidence and report it up the chain-of-command.
Security personnel must not interfere with situations handled by specialized units, such as hostage situations. Security response to these situations is outlined in the Operational Standards.
Loopholing is prohibited, such as baiting self-defense.
Security personnel are solely responsible for their account and the actions and conduct of said account, regardless of who may have been controlling the account.
Usage of AI on any department applications will result in denial of the submission of a 1-month blacklist from detachments. Troll submissions to any department forms can result in discipline up to an exile on a case-by-case basis.
§2. Command Conduct
All Security Command are expected to use their proper authority as dictated by these regulations and the Code of Administrative Regulations.
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 in 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 at least biweekly. DA
The Chief of Security is expected to upkeep the department and address crucial concerns within the Department's infrastructure. DO
The Chief of Security is expected to notify those below when possible and remain at 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 Security Department's Standards & Education Team, this time limit does not apply.
The following punishment levels are able to be handed out.
Security Command also has the right to remove Experience Points as part of any punishment, with the number of points determined by the severity of the punishment.
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 Department Duties
Chain of Command during Normal Protocol
Chief > Inspector > Officer > Sentinel > SRU/MP > Senior > Base SD
Security Personnel should follow the same procedures as they would if it were Normal Protocol.
Security Personnel are to follow all orders given to them by the Military Police.
Chain of Command during Heightened Security Protocol
Chief > MP Divisional Inspector > Inspector > MP
Security Personnel should follow orders from those in the Chain of Command, especially SRU.
Security Personnel should focus on reinforcing the CDC and coordinating with each other.
Chain of Command during Riot Protocol
Chief > SRU Divisional Inspector > Inspector > SRU > Lambda-7 > Officer > Sentinel
Security Personnel should follow orders from those in the Chain of Command, especially Lambda-7 and during Assassination Raids, Delta-1.
Security Personnel should focus on reinforcing HOC, CR, and LB during the raid unless otherwise told.
The exception is during hardpoint raids, in which Security Personnel should focus on securing the hardpoint
All Security Personnel must abide by the outlined Raid Regulations for the ongoing raid type.
Chain of Command during Raid Protocol
MTF Chief/Major > SD Chief > Lambda-7 > Delta-1 > SRU Command > Officer > Sentinel
Chain of Command during Assassination Raids
MTF Chief/Major > SD Chief > Delta-1 > Lambda-7 > SRU Command > Officer > Sentinel
There are two types of breaches, Euclid and Keter. Both breaches follow the same protocols.
Security Personnel are to man and station in areas based on importance:
Manning the HOC Blast Door Controls. (Security Junior+)
Manning the Civil Sector Road Gate Controls. (Security Guard+)
Manning the Breach Shelter Controls. (Security Junior+)
Guarding of the Cleanrooms. (Security Cadet+)
Guarding of the Loading Bay (Security Cadet+)
Providing support to the Class-D Containment Zone (Security Guard+)
Evacuating civil personnel towards HOC and behind both HOC Blast Doors.
Security Personnel should close the corresponding Door/Gates if:
Close the Civil Sector Road Gate if:
A breached SCP is approaching the Civil Sector.
Close the HOC Blast Doors if:
A breached SCP gets past the Road Gate.
Close the Breach Shelter if:
A breached SCP gets past the HOC Blast Doors.
Security Personnel must open the BS, BDs, and Road Gate if ordered by:
MTF Operative+
Security Class-4+
Non-Hostile SCP's
SD Sentinel+
SRU Sergeant+
MP Lieutenant+
Should Breach Procedures fail or a Breached SCP is in front of SD Spawn, Security Personnel are to remain in spawn until safe to leave.
Chain of Command during Keter or Euclid Breach Protocols
MTF Field Chief/Major > SD Chief > Eta-9 > MTF > Inspector > Officer > Sentinel
Security Personnel are expected to log protocol responses in #database_requests to claim experience points required for promotion. When doing so, Personnel must follow the requirements below.
When logging ANY protocol response, Security Personnel must:
Ensure their username and rank are present within the screenshot.
When logging a RIOT Security Personnel must include TWO screenshots of:
ONE screenshot showing the Riot Protocol message on a TV or the radio.
ONE screenshot showing the Normal/Rise Protocol message on a TV or the radio.
When logging a BREACH Security Personnel must include TWO screenshots of:
ONE screenshot showing the Keter/Euclid Breach Protocol message on a TV or the radio.
ONE screenshot showing the Normal/Possible Breach Protocol message on a TV or the radio.
When logging a RAID Security Personnel must include TWO screenshots of:
ONE screenshot showing the Raid Protocol message on a TV or the radio.
ONE screenshot showing the End of Raid Rally or the Normal Protocol message on a TV or the radio.
When logging a BACKUP REQUEST Security Personnel must include TWO screenshots of:
ONE screenshot showing the Backup Request on Discord with the current time.
ONE screenshot showing you on-site with the current time which should be at least 10 minutes after the backup request was sent.
If you forget a screenshot, MTF Operative+/SRU Sen. Response Agent+/MP Spe. Constable+/Base SD Command are allowed to vouch for you, but you must provide proof of them vouching for you (DM, message, etc).
Security Personnel who excessively abuse the vouching system will have their database requests denied and may face punishment if they continue.
Security Personnel must understand the area restrictions that is around site. Deviations may occur within other Security Documentation.
Inner CDCZ
The Inner CDCZ or past the Lockup Gates is considered a "Dead Zone" (Labelled in Red below), and Security Personnel are required to have one other combative Personnel with them when entering Dead Zones for their safety. Dead Zones are voided during Riots
Security Senior+ may enter Dead Zones freely.
Escape Tunnels/Vents
Security Guard+ are able to enter to sweep for boxes if SRU and MP are not available.
MP/EC/SRU/AAC request assistance in catching rogues.
Class-Ds are actively firing from Tunnels/Vents
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.
Light/Medium Containment Zone (Anomaly Containment Hub)
Off Limits unless the SD is escorting a test.
Security Department personnel may not enter the ACH for any other reason unless explicitly authorized by Eta-9.
SD must report Hostile sightings to MTF/SRU/MP. They cannot enter to chase any Hostiles themselves unless authorized by MTF.
SD must request for MTF to handle any Hostiles within any Containment Chambers (Past Chamber Airlock).
Restricted to Security Junior+,
Requested by MTF.
Friendly SCPs §1
A list of Friendly SCPs and how to handle them.
SCP-131
SCP-4966
SCP-343
These SCPs should not be shot at under any circumstances. Should SCP-131 instances annoy certain SCPs (049, 2561, etc.) or disrupt on-site operations (opening transfer gates, etc), 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 not purposefully feed items to instances of SCP-4966 to minimize the risk of harm towards personnel.
Neutral SCPs §2
A list of Neutral SCPs and how to handle them.
SCP-527
SCP-2561
SCP-049
SCP-035
SCP-662
SCP-066
These SCPs may ‘breach’ at any time, but not always. In the event they are breached, SD should communicate the location(s) of these SCPs to Eta-9. These SCPs should not be directly shot unless exempted below.
Security Personnel are permitted to interact with neutral SCPs if they are not breached/pose a threat to the Foundation, and do not interrupt Security Duties.
The activation of the Euclid Breach Protocol signifies a Neutral SCP has breached.
SCP-527 ("Mr. Fish")
Generally friendly.
Should be referred to as "Mr. Fish"
This SCP should only be shot at if it is actively rogue and shooting at personnel.
SCP-2561 ("Broadcast")
Generally friendly.
Should be referred to as "Broadcast"
Broadcast actively hunts for SCP-527 and should not be given Mr. Fish's location.
If Broadcast finds Mr. Fish and Eta-9 are not available to handle the situation, Security Personnel should negotiate with Broadcast, offering it fish in the CDCZ Cafeteria.
If Broadcast refuses the offer, Security Personnel are permitted to shoot around but never DIRECTLY at SCP-2561. All requests from Broadcast should be followed unless deemed unreasonable.
SCP-049 ("The Doctor")
Generally friendly.
049 should always be referred to as the "Doctor".
Security Personnel should not interact with The Doctor unless spoken to or ordered to.
All requests from The Doctor should be followed unless deemed unreasonable.
SCP-662 ("Mr. Deeds")
Generally friendly.
Should be referred to as "Deeds"
Deeds is capable of providing virtually anything to anyone at request.
Security Personnel are not to request items outside of their clearance level as outlined in Section 3, Chapter 3: Anomalies & Testing of the Code of Ethics.
Deeds is not to be terminated unless he is confirmed to be "hostile" (attacking personnel)
Security Personnel are to cease terminating Deeds once the bell holder is terminated, or Deeds becomes no longer hostile.
SCP-035
Generally friendly when acted.
035 has an acted and non-acted version.
Acted: A member of Anomaly Actors is currently controlling 035.
Non-Acted: The wearer of the mask is currently controlling 035.
Security Personnel are not to shoot an Acted 035, even if it's harming others, unless explicitly ordered by Eta-9.
Non-Acted 035 is to be shot on sight if breached.
SCP-066
Generally friendly.
This SCP should only be shot at if it is actively rogue and shooting at personnel.
Hostile SCPs §1
A list of Hostile SCPs and how to handle them.
SCP-173
SCP-457
These SCPs should not be interacted with under any circumstances for any reason. These SCPs pose an active threat to all personnel at all times, and in the event a breach is declared, Security Personnel are to follow standard breach procedures outlined in Section III.
The activation of the Keter Breach Protocol signifies a Neutral SCP has breached.
The Security Department has to follow the Solitary and Termination Criteria documented at all times at any point in-time On-Site.
All Security Personnel are equipped with the “Strike Clipboard”. The clipboard will show the Class-D and the number of strikes they are on.
After a Class-D has reached 3 strikes and is Designated for Solitary Confinement (DFSC), through the use of handcuffs and the beanbag shotgun, a Security Junior+ will:
Bring the cuffed DFSC Class-D in front of a cell in the Solitary Wing.
There, they will receive a green uniform indicating they have been Solitary Confined (SC'ed).
Release the Class-D back into the CDC once they have this uniform.
If a Class-D who is already SC'ed receives a 4th strike, with cuffs, return the Class-D to the Solitary Wing, and they will be automatically placed inside a cell.
Primary Weapons
Secondary Weapons
Security Personnel may use weapons purchased from the SD Vendor and Gamepass weapons freely.
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 and equipment restrictions may be voided when Security Protocol 'Last Stand' is activated. View more information here.
Equipment available to Security Personnel.
Pepper Spray
Stunning Class-D (does not apply to juggernauts)
Eg, warning Class-D personnel for violating the termination criteria, searching for SCP-268, etc.
Keep in mind the Pepperspray does chip damage
Security Department personnel are to utilize common sense when using pepper spray.
Do not use through walls, doors, etc.
Night-Stick
Used to give physical warnings to Class-D's or finish hostiles.
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.
Refer to information on the Riot Shield for more info regarding taunting.
Strike Clipboard
Used to strike Class-Ds for violating the Solitary & Termination Criteria and track how many strikes each Class-D is on.
Do not Revenge Strike (Striking a Class D when you Respawn and the Class D is still alive)
Combative Flashlight
Used to light up areas during nighttime or if the power goes off.
CONTROLS:
[Left-Click] to turn on while equipped.
Unequipping will place the flashlight on your shoulder.
[Press L] to turn the flashlight on and off while it's on your shoulder.
Handcuffs - Security Junior+
Only be used for Rogues/DFSC/Getting CD for test's.(Excluding Juggernauts)
CONTROLS:
[Left-Click] on them to cuff.
[Left-Click + F] on them to disarm.
[Left-Click + Q] on them to make them jump, helpful if the CD is sitting down.
Beanbag Shotgun - Security Junior+
A long-range weapon used to stun/ragdoll people for easy cuffing.
May ONLY be used on/for:
DFSC Class-Ds
Rogue Personnel
Testing purposes if requested by the Host.
Riot Shield - Security Guard+
A shield used to stop bullets from hitting you while in combat, like when pushing.
The shield takes up your primary weapon slot and has 265 HP before it breaks.
CONTROLS:
[Press G] with your secondary weapon or nightstick equipped to equip your riot shield.
[Press Q] with your nightstick and riot shield combo to taunt.
CS Gas - Security Senior+
Gas that causes those affected to slowly lose health and not be able to equip their weapons.
Useful for crowd control or room clearing.
May only be used during protocols. (Riot, Rise, Breach, etc)
Security Sentinel+ may free use.
SD Vendor
Security Personnel can purchase a variety of weapons and equipment from the SD Vendor ran by Coach. Some equipment
Crate Tracker - 50$ (One Life)
Activating the tracker allows Security members to locate an SCP Box. It's used whenever a box's location is unknown and needs to be retrieved.
M17A2 - 15$ (One Life)
The gasmask helps in scenarios in which Combatives are deploying smoke or csgas. While it may help against infections, it's extremly minimal and often better to avoid the infection entirely. They are gasmask filters around site to refill your filter.
Permanent Weaponry - 2,000 or 4,000+
Permanent Weaponry are able to be bought from the Armorer and be a permanent staple within a Security member's loadout. It is worth noting that these weapons are usually in the 2,000s or higher.
Field Bandage
Stops bleeding from continuing.
Does not heal damaged areas.
Sector Gates and CDC gates SD can access.
HOC Sector Gate - Security Guard+
May only be closed during a Breach in line with breach procedures.
Inspector+ requests the gate to be closed.
CDC Lockup Gates - Security Senior+
Only be used:
If a Riot lasts more than 20+ minutes
During a CDC Lockdown (refer below)
All Terminal protocols are to be entered on a wall terminal located around the site, following the formats listed for lockdowns and protocols below.
Rise - Security Senior+
protocol rise yes/no
Can only be turned on if:
The CDC is generally unstable for 5+ minutes.
The CDC cannot be held for 5+ minutes.
A CD Juggernaut is active.
Security Seniors MUST request any objections on the radio before activating/deactivating rise protocol.
Objections from: Security Sentinel+, SRU, MP Primary Constable+, and MTF must be abided by.
Riot - Security Sentinel+
protocol riot yes/no
Can only be turned on if:
The CDC cannot be held for 10+ minutes.
CDs have been reported in multiple locations across the site and have not been terminated for 10+ minutes.
Security Sentinels MUST request any objections on the radio before activating/deactivating riot protocol.
Objections from: Security Officer+, SRU, and MTF L7 must be abided by.
Blackout - Security Officer+
Request within radio "@ets Blackout "Area"
CDC Lockdown - Security Officer+
lockdown CDC yes/no
Only be turned on if:
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
Lockdown must be turned off after 10 minutes, even if the boxes have not yet been recovered.
Security Inspector+ requires it.
HOC Lockdown - Security Officer+
lockdown HOC yes/no
Only be turned on if:
Formal Events that require Increased Security
Concentrated Area of Hostility for 15+ minutes (Excluding Juggernauts and Raids)
Uniform regulations SD must abide by.
SD may use any uniforms, headgear, and gear they can access.
Not including Riot Gear, Formals, and the Peaked Cap.
All Uniforms and Gear must tie together; SD may not cross-match by using a 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.
Riot Gear
May be used during Riots and Breaches ONLY
Formal Uniforms - Security Junior+
Includes Formal Uniforms and the Peaked Cap/Bucket Hat.
May be used only for Formal Foundation Events.
Does not apply to Gamepass Uniforms.
Holders of the Retired Command Service Medal may wear Formals freely as long as they hold the medal.
Security Sentinel+ may wear freely.
A list of SD vehicles and vehicle related regulations SD must abide by.
Regulations
Security Personnel are to park properly in designated parking spots.
SD are not to use vehicles to ram/run over SCPs, Foundation Personnel or Hostile Juggernauts.
If a Juggernaut has been ongoing for 15+ minutes or obtained an SCP item, SRU are excluded and may ram hostile juggernauts freely.
SD may use any of the vehicles listed below and supporter vehicles freely.
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+
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 Command.
