E-Mail to All Security

By, Carlos Horno, posted 2 years ago

2 years ago - edited

# Fe6PzLD70X3ADzwY

From: [email protected]
To:
BCC: [email protected], [email protected], [email protected]


Hello Area-36!

As most of you are aware, I am Horno, your new Security Chief! I'm sure I am a familiar face to most of you, but I still felt it necessary to make this E-Mail.

First, I'd like to thank everyone for the hard work, the facility has been running phenomenally since the moment I came on area for the first time, and that is always something that makes all of our lives easier.
Second, I'd like to address some of the low hanging fruit on my agenda that I feel can easily be fixed. Incident reports! It's of no surprise that when you put approximately 30 anomalous objects into one centralized facility, sometimes shit hits the fan. That is why, whether the cause be from a breach, a GOI attempting to thwart us, or whatever the case may be, it is imperative that we log these events. Should it have major damage to the facility, give us insight on the abilities of an SCP, or injures some of our personnel, making a report does three main things for us.

1. Provide a log of events, so that we may find patterns that could cause events, or link together chains of events into one main cause.
2. Allow us to look back at how we reacted and adjust our future response accordingly in order better prepare ourselves for these sorts of situations.
3. Allows us to organize what damages or losses we have as a facility so that a solution or damage assessment can be rapidly produced.

I would also like to address when to write a report and who can write a report.
First from this list, WHEN:
When an major breach occurs, a GOI attacks us, or some new anomalous threat appears on area, an incident report is to be made. (// this only counts for canon things, please don't log every time 173 gets out...)
Second, WHO can write it.
What many may not realize, is that if you were present for the incident, you can write the report. Usually, I'd recommend Level 3 Personnel or higher write the report, but if you would like to do it yourself and you are not Level 3 or higher, that is perfectly acceptable. Just communicate that you will be writing the report in an effort to combat duplicate reports. The only limit on this, is some information may become restricted to a higher access level, so make sure you lock the report behind the proper clearance and have yourself amnestized immediately following the report if the information is beyond your clearance.

ANYONE WHO RETAINS RESTRICTED INFORMATION PURPOSEFULLY AND DOES NOT GET THEMSELVES
AMNESTIZED WILL FACE IMMEDIATE DETAINMENT, QUESTIONING, AND UP TO TERMINATION.
THIS IS NON-NEGOTIABLE UNLESS APPROVED BY THE AREA DIRECTOR.

Additionally, if you take these responsibilities when no one else is willing to, it looks quite good and will more than likely catch the attention of your branches respective S.O.C. (Just a little motivation there for you newer personnel.)

That is all for now, please direct any question about this E-Mail via a separate E-Mail chain OR ask me on area. (// only because I don't want this email chain to become a mess of replies)

Thank you very much,
Security Chief Horno

Security Chief Horno - Still somehow alive

"How am I not dead yet??"

Vault Security Agent Muller - Alive

"Well, I got that promotion."

0


2 years ago

# pKbgP9lfFnysyB2T

Hi Horny :) - Senior Security Officer Hadrian

Kyrie Elieson!

Head Engineer Rurik

SSO Hadrian

SID Recruit Vladik

New Admin

0

2 years ago

# bKTdScMzDc7G_1-s

Excited to be working under you sir! - SO Connors.

HRT PVT Thompson - Alive

Abel no lifer

0

2 years ago

# GIw79yMIRbqTPwBp

[RE: SSO Hadrian]

Bruh.

Regards,
Horno

Security Chief Horno - Still somehow alive

"How am I not dead yet??"

Vault Security Agent Muller - Alive

"Well, I got that promotion."

0

Join this community to post or comment