Security Department
On-Site
Guidelines
Table of Contents
Section I > Security Department Expectations
Security Personnel
As a member of the Security Department you are expected to follow a set of base rules and regulations at all times.
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.
All personnel regardless of clearance and department are to be respected.
While on the Security Department team, you are not to display any excessive or hostile immaturity or unprofessionalism without approval or valid reasoning to do so. This excludes friendly banter.
This includes both behavior and what you do/wear.
All sentences from the Security department should be understandable with at minimum, basic spelling outside of team and combative chat. Any usage of slangs is discouraged heavily. E.I "btw", "ion", "wyd", "gng", etc.
Members of the Security Department are allowed to talk with Class-D and Foundation Personnel freely, unless it actively disrupts Site Operations and the duties of the SD member.
All orders from Security Command should be followed. If you believe an order was against regulations, report it to the Ethics Committee or Security High Command. This doesn’t apply to members of the O5 Council, you are to follow their orders without question.
Equipment is not to be abused by members of the Security Department at any time
Base Security Members are not allowed to interfere with hostage situations unless requested by the Security Response Unit, the Military Police, or Security High Command.
Members of the Security Department are not allowed to equip themselves with SCP items or tools/gear given by SCPs and use them for their own advantage.
Only exception is High Command+ may use SCP-662 Due to them being SC3.
Security Personnel interacting with docile SCPs must interact in a calm respectful manner. Interactions should not interfere with on-site duties, unless requested otherwise.
Security Personnel may not emote while on-duty during any time
Gesture emotes(waving, pointing, saluting, etc) are exempt from this rule and may be used.
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 Upper LB is prohibited unless you are following the following regulations:
Crates can only be taken if there is a Class D juggernaut or there is a Class D riot (alarms active)
Crates may be hidden until the Class D juggernaut is terminated or the riot is over; they must then be returned immediately.
Crates may not be hidden in department spawns (This includes SRU/MP spawn)
Crates should only be put in an area accessible by a hacking device.
Crates may not be put in areas where civil personnel may easily access. (E.g middle of SL-4 Lobby)
14. All Security Personnel are expected to manage their personal items properly and thus, all actions done on their respective accounts are responsible for it. (Including dishonorable discharges from either group or server and Compromised accounts.)
15. Usage of AI on any official Security Department document (and detachments) will result in an exile from the department with an additional 1 month Blacklist.
16. Troll submissions on any Security Department document (and detachments) will result in exile from the detachment or the department on a case by case basis.
Security High Command
Security Inspectors are expected to prioritize the Main Security Force over any other subdivision when needed.
Security Inspectors are expected to oversee and only interfere with Detachment Command when absolutely necessary.
Security Inspectors are expected to uphold their general duties as High Command and not remain extended absence without notifying
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.
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.
Security Inspectors and Chief of Security are expected to update their public list of plans atleast once bi-weekly.
The Chief of Security is expected to upkeep the department and address crucial concerns within the Department's infastructure.
The Chief of Security is expected to notify those below when possible and remain a level of publicity where Security Personnel are acknowledged.
Section II > Disciplinary System
To ensure all Security Department Personnel are being held to their utmost potential, 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 WW'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.
The following punishment levels are able to be handed out.
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 harsher punishment.
This rule does not apply if you're getting this appealed with the Internal Tribunal Department. But do not leave the Security Department Server or the Group.
Security Command may change the punishment or punishment level given if deemed necessary.
Security Seniors may be punished by an extra punishment or punishment level at the discretion of Security Command.
*This list does not contain all reasons for punishment, Security Members can be punished for any valid reasoning at the discretion of Security Command.
Security Members may be punished for any of the following reasons:
Not Following Testing Queue without valid reasoning.
1st Offense: WW
2nd Offense: L1 (20 Laps)
3rd Offense: L2 (3 Day Suspension)
Excessive Immaturity.
1st Offense: VW
2nd Offense: WW
3rd Offense: L2 (3 Day Suspension)
4th+ Offense: L3 (Demotion)
Misuse of Utility/False SC’ing.
1st Offense: L1 (20 Laps)
2nd Offense: L1 (40 Laps)
3rd Offense: L2 (5 Day Suspension)
4th+ Offense: L3 (Demotion)
Mass Misuse of Utility of False SC’ing will result in an immediate exile or blacklist depending on severity.
Minor Abuse of Power.
1st Offense: L1 (20 Laps)
2nd Offense: L1 (40 Laps)
3rd Offense: L2 (7 Day Suspension)
4th+ Offense: L3 (Demotion)
Dismissed from a training.
1st Offense: WW
2nd Offense: L1 (20 Laps)
3rd Offense: L2 (3 Day Suspension)
4th+ Offense: L3 (Demotion)
Disrespect/Slandering to other Personnel.
1st Offense: L1 (40 Laps)
2nd Offense: L2 (3 Day Suspension)
3rd Offense: L2 (7 Day Suspension)
4th Offense: L3 (Demotion)
5th+ Offense: L4 (Exile)
Direct bullying will result in an Instant exile.
Purposefully disregarding security duties
1st Offense: L1 (40 Laps)
2nd Offense: L2 (3 Day Suspension)
3rd Offense: L2 (7 Day Suspension)
4th Offense: L3 (Demotion)
5th+ Offense: L4 (Exile)
AFK Farming.
1st Offense: L1 (20 Laps)
2nd Offense: L1 (40 Laps)
3rd Offense: L2 (5 Day Suspension)
4th+ Offense: L3 (Demotion)
Use of SCP Items.
1st Offense: L2 (5 Day Suspension)
2nd Offense: L2 (7 Day Suspension)
3rd Offense: L3 (Demotion)
4th+ Offense: Exile
Discharging without completing your punishments.
1st Offense: L2 (7 Day Suspension)
Goes in effect if you rejoin the Security Department
Purposely ignoring Security Command
1st Offense: L1 (40 Laps)
2nd Offense: L2 (3 Day Suspension)
3rd Offense: L2 (7 Day Suspension)
4th Offense: L3 (Demotion)
5th+ Offense: L4 (Exile)
Incorrectly interacting with SCPs.
1st Offense: L2 (3-5 Day Suspension depending on severity)
2nd Offense: L2 (7 Day Suspension)
3rd Offense: L3 (Demotion)
4th+ Offense: L4 (Exile)
Long AFK Farming.
1st Offense: L3 (Demotion)
2nd Offense: L4 (Exile)
Medium-Severe Abuse of Power.
1st Offense: L3 (Demotion)
2nd Offense: L4 (Exile)
Random Killing.
1st Offense: L4 (Exile)
2nd Offense: L5 (Blacklist)
Mass Random Killing will result in an immediate Blacklist.
Going rogue.
1st Offense: L5 (Blacklist)
Purposely breaching an SCP.
1st Offense: L5 (Blacklist)
Racism/Discrimination of any Kind (Based on Sex, Religion, Race, etc).
1st Offense: L5 (Blacklist) and Report to CMT.
Promotion/Encouragement of Terrorism, Terrorist Groups, or Illegal acts.
1st Offense: L5 (Blacklist) and Report to CMT.
Section III > Site Protocols
Site protocols are activated using On-Site terminals around the facility. While on-site you will encounter some of these.
Normal
No Security Response is needed for this protocol. Security Personnel are to resume their normal duties, such as guarding the CDC or Escorting Tests.
The following Chain of Command applies during normal operations:
Chief > Inspector > Officer > Sentinel > Base SD
Breach
During this protocol, all Site Operations are to be stopped and Foundation Personnel are to be evacuated behind the Blast Door or the Breach Shelter depending on the SCP that has breached. The Mobile Task Force known as Eta-9 holds full authority when the Breach protocol is on. This also means that Eta-9 may override the breach instructions and direct Security members elsewhere.
Containment Breach Response Hierarchy:
Eta-9 > Delta-1 > Lambda-7
The following Chain of Command applies during Breaches:
MTF Field Chief/Major > Security Chief/Deputy Chief > Eta-9 > MTF > Inspector > Officer > Sentinel > Base SD
Once a breach has been reported, all Security Department personnel are to find a position inside the Hamilton Office Complex.
Base Security will be responsible for maintaining the safety of the Hamilton Office Complex. In specific, the goal is to ensure Foundation Personnel will not be harmed and the security of Non-Sentient SCPs. The JFK Administration Complex will be handled by the Military Police.
During any breach, one Security Cadet+ should head to the Cleanrooms to ensure the safety of Foundation assets. Guard+ will be stationed at the entrance of the civil sector to close the Civil Sector's Gate when needed. Security personnel should abide by this unless ordered otherwise by the Security Response Unit, Military Police, Security Sentinel, or Eta-9.
Security personnel should not go to the Loading Bay if the path is obstructed by the breach.
During a breach of a sentient anomaly, Base SD will periodically open and shut the Blast Door to ensure the safety of Foundation Personnel. If the SCP appears to be heading to the Civil Sector, the Civil Sector's Gate is to immediately be shut.
If the breach makes it into the Civil Sector, Security Department personnel are to immediately close the Blast Door. The door may be opened after the SCP is on the other side of the Site(Only by a Select Group) OR if a Security Class - 4+ requests it to be opened or Eta-9 request it to be opened.
The following people may request for the Blast Door and Civil Sector's Gate to be opened after being closed: MTF Operative+, SC-4+, Non Hostile SCP's, SD Sentinel+, SRU Sergeant+, and MP Lieutenant+.
The Military Police will hold authority of the Civil Sector. The Military Police will also be responsible for sweeping the Civil Sector for any Foundation Personnel and getting them inside the Hamilton Office Complex or JFK Administration Complex. During a sentient breach, if a hostile SCP is to appear inside the Civil Sector, The Military Police and any Base SD outside a building should immediately find shelter. The Military Police have authority over the Blast Doors and the Civil Sector's Gate and Administrative Sector's Gate.
The Security Response Unit will be responsible for sweeping the entire site excluding the Containment Sector for foundation personnel; when found, they should bring them to the front of Civil Sector's Gate and hand them off to MP. SRU should avoid the breached SCPs area.
During Sentient Breaches, Security Guard+ may hold positions inside the Class-D Containment Zone as long as the Sentient SCP is not within the area or blocking the way the entrance to the area. If the SCP moves to the Class-D Containment Zone, Security Guard+ must hide or attempt to leave Class-D Containment Zone. If you are found to interfere with containment, you will be heavily punished. Remember that Eta-9 has the final say.
Security Department CR/Outer Positioning
Security Department HOC Positioning
If too many members of the Security Department are present at a select location, the highest ranking individual in there will take lead into creating new positions and failure to do so may result in disciplinary actions.
*Security Officer+ have the right to recall you back to the Hamilton Office Complex if deemed necessary*
Riots and Raids
Riot and Raids happen quite often on-site therefore it's essential for Security members to know how to tackle these protocols correctly. A separate document is linked below stating the information required to properly assess these protocols.
During Protocol Riot, it is recommended that all Security Department personnel that have access to the beanbag shotgun equip it to put any rioting Class-D into solitary confinement.
Security Members who are escorting a foundation event like testing or a tour that sees a Solo Raiders are to not shoot at the Solo Raiders and should report it on the radio of the Solo Raiders location and continue to escort the event to whatever location it needs. Solo Raiders may not disrupt civilian events, if Solo Raiders do disrupt the event, Security Members are to report the Solo Raiders to DEA and GRU-P command with evidence.
Blackout
When a riot becomes uncontrollable or a malfunction occurs in Paragon’s electrical units, the blackout protocol is activated. Security members are to continue their normal duties but equip their flashlights.
CDCZ Locations
While these positions are NOT required, they are recommended to reduce the risk of death.
SRU or SD Command may move Base SD to better positions if needed.
Infirmary Line
Class-Ds located in this line are prioritized for check-ups and entitled to request medical aid, denial may occur during emergency protocols.
Testing Line
Location of Test Pickups. Security Personnel are expected to prioritize any Class-Ds within this line excluding SC'D Class-Ds. Security Personnel should not report to another Line in order to pick up a Class-D
Guard Line
Main area of guarding and securing the CDCZ, Class-Ds here are do not hold any entitlements or prioritization in any regard.
Section IV > Area Restrictions
Some areas are restricted to members of the Security Department. Some of these areas may be accessed under temporary conditions for the following reasons. If the conditions are no longer valid SD are to exit the area as soon as possible. Only one of these conditions have to be valid to you to be able to enter, rank restrictions cannot be bypassed unless you are acting as a Detachment Member. Security Guards supervising cadets may only enter areas said Cadet can access. Some of these restrictions will be voided during Security Department Protocols, consult the "Protocol" page for more information.
Areas past the CDCZ Cafeteria
All areas past the Cafeteria Zone is considered a "Dead Zone" (Labeled in Red) and Security Personnel are required to have 2+ 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.
CDC Underground Level
Off limits unless a DFSC Class-D enters the area,
An SD sees a Class-D committing an action worth termination.
Senior+ or SRU/MP are searching for boxes.
Escape Tunnels
Off limits unless a DFSC Class-D enters them,
MP/SRU are looking for SCP boxes,
If MP/SRU are not present, Guard+ are able to enter to sweep for boxes.
Class-D commits actions worth termination.
Blowing up the wall doesn’t count towards this.
MP/EC/SRU/AAC request assistance in catching rogues.
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.
Clean Rooms
Base SD may enter when escorting a test or when there is a reasonable suspicion that hostiles and/or boxes are within.
MP may enter freely whenever,
SRU may enter when conducting their duties or while escorting a test.
Security Sentinel+ may enter freely whenever
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.
Section V > SCP Interactions
Friendly SCPs
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
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
SCP-527, SCP-2561, SCP-049 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’
Section VI > Solitary Confinement
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
Section VII > Weaponry
The Security Department has a variety of weapons at their disposal upon reaching higher ranks within the Security Department and its department detachments. The following is a list of each rank and which weapons they will receive.
Base Security:
M1911 - Security Cadet+
M3 Grease Gun - Security Cadet+
Colt M365 - Security Junior+
M16A1 - Security Guard+
CAR 15 - Security Senior+
Ithaca 37 - Security Guard+
MP5 - Security Sentinel+
Section VIII > Utility
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 'Prisioners Nightmare' is activated. View more information here.
Base Security:
Strike Clipboard - Security Cadet+
Do not Revenge Strike (Striking a Class D when you Respawn and the Class D is still alive)
Combative Flashlight - Security Cadet+
Leave it on your shoulder by equipping and unequipping it.
Press "L" to turn it off and on while it's on your shoulder.
Pepper Spray - Security Cadet+
Used by Security Cadet+ to stun Class-D (does not apply to juggernauts)
Examples of use include 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.
Cuffs - Security Junior+
Cuffs cannot be used on any Juggernauts
Cuffs can only be used for Rogues/DFSC/Getting CD for test's.
Keybinds;
Press 'F' and click (MB1) to disarm an individual
Press 'Q' and click (MB1) to make an individual jump. [ONLY WHEN CUFFED].
Nightstick - Security Cadet+
Hit may be used to warn Class-D personnel for violating the termination criteria.
Nightsticks may not be used on GRU-P.
Must press Q with Nightstick + Riot shield to taunt.
Only be used for Riot Rushing,
Gaining the attention of personnel,
Backing Class-D off the line,
And dispersing large crowds.
Beanbag shotgun - Security Junior+
May be used to warn Class-D personnel for violating the termination criteria, DFSC Class-Ds, and rogue FP.
May also be used for testing purposes
Riot Shield - Security Guard+
Provides extra cover at the expense of your primary weapon, and may be used freely.
Must press G with a Secondary/Nightstick to Equip
Supporter Hats/Gears - Security Guard+
The Hat/Gear must fit the scenario the individual is in.
Must fit the current wear of the National Guard.
It must fit the time period. (1980s)
CSgas - Security Senior+
May be used during in-game protocols only.(Riot, Rise, Breach, etc)
May be used freely by Security Sentinel+
Formal Uniform - Security Sentinel+
May be used freely by Security Sentinel+
Garage/Fire Doors - 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.
Terminal Protocols
Rise - Security Guard+/Probationary Response Agent/Primary Constable
In terminal enter: protocol Rise on/off
Riot- Security Senior+/Response Agent/Primary Constable
In terminal enter: protocol Riot on/off
CDC Cellblock Lockdown - Officer+, Senior Response Agent+
only be used:
a Riot/Rise has occurred for 15+ Minutes
Security Inspector+ requires it.
Riot Gear - Security Cadet+
May be used during Riots, Breaches, and Raids
Authorised by Security Sentinel+
May be used freely by Security Senior+
Vehicles:
Security Sedan - Security Junior+
A Compact Sedan with its primary purpose to provide a comfortable view for all passengers. Security Personnel should expect a well rounded vehicle when entering this car.
Security Bronco - Security Senior+
Provided to the models of the Security Department, this vehicle excels in turning and cutting corners for high speed chases and tight corridors.
SD is to park properly in designated parking spots not already reserved for other parties.
SD is not to use vehicles to purposely run over Foundation Personnel or Juggernauts.
(Eg, ramming Hostile Juggernauts to disadvantage them by: ragdolling, damaging, immobilizing, terminating them, etc.)
SD is not to utilize vehicles as "car bombs". Doing so will result in harsh punishment.
SD are not to spam spawn vehicles at any time.
Warning: Vehicles have irregular drifting during off-road surfaces, Security Personnel are expected to adapt if needed.
Section IX > Activity
While the Security Department currently has no set activity expectations for those ranking Security Guards 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.
Section X > Closing Remarks
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.