Brigade internal access system information - by Jimmy Manderson

[Hades Brigade]

Date of creation
23/01/832

BRIGADE ACCESS SYSTEM
AUTHOR: JIMMY MANDERSON
FOR READ ONLY

---

INTRODUCTORY INFORMATION

The use of encryption and encryption systems in the Order, as in any other organization, goes back a long way. Corporations use encryption to protect their communications from outside interference and to prevent corporate espionage. Militaries use protection to avoid espionage as we know it. Intelligence agencies, including the Order, use all sorts of means, sometimes even too primitive, to preserve their data.

When the question of encryption came up, we tackled it rather tightly and applied the methods of Overwatch and other Order units that agreed to give us the necessary codes. The goal was to create methods that would literally prevent third parties from getting in where they shouldn't. This manual is applicable to all Brigade Commanders and Commandants, to understand exactly how cipher keys are handled within our structure.

TEMPLATES AND CODES

Any information in the Brigade, whether reports or internal communications, comes from “templates” which in turn are coded in a certain way. Each template belongs to its own group, and the group itself has a universal access code for all templates in that group. The code is an electronic file that is only allowed to be transferred to another agent by direct transmission in open space or to make the transfer only in person. Code transfer is prohibited through systems, within the system itself, in short - over any distance greater than 1K.

Codes vary in their purpose, and some of them apply only to specific templates, not to the group as a whole. It should be noted that if you get an access code to work with the whole group of templates - you may have actual access to only a few templates. The rest of the templates may not be known to you, for one reason or another. This avoids situations where there is a leak in code transfer and third parties can gain unauthorized access to templates and work with them. To start working with any template from a set group, an agent needs to authorize in the Order neural-net, specifically in the Brigade neural-net. After that, he enters the necessary link to the desired template and applies the code to work with it. Step by step, this process looks as follows:

1. You get access to the template.
   
2. You're logged into the Order neural-net. After that, you'll be logged into the Brigade neural-net.
   
3. You get a code to access a specific template. This means that you can see the template itself.
   
4. Using the access code, you get access to work with the template.
   

As stated earlier, codes vary in their purpose, and therefore your options for working with the template may be quite different. Let's imagine that you have a “Group” of templates. This “Group” would have the following access codes:

• Access code “A1” - allows to use templates and send their filled variants through the specified channel.
  
• Access code “A2” - allows you not only to send messages according to a template, but also to view the history of your sent messages.
  
• Access code “A3” - allows you to view the history of all messages in the communication channel.
  
• Access code “A4” - has the same permissions as “A3”, but in this case you can also edit the template and delete any unauthorized messages.
  
• Access code “A5” - allows you to track the very fact of sending messages using the template. It does not give access to editing the template or viewing any message history. Typically used to track the transmission of messages outside the Brigade.
  
• Access code “A6” - it is allowed to use the specified template a limited number of times. Usually can be useful, if you suddenly need to give access to unauthorized person to something. Code “A6” can be granted by Commanders to lower ranks. As a rule, it is used here. In other cases, "A6" is used extremely rarely and only in emergency situations, basically this key is dusting and sometimes waits for months or even for years.
  
• Code “A7” - absolutely full access to the template group, in every sense of that word.
  

It's not hard to guess that each template represents a different communication channel. As a rule, we rely on electronics, although we retain a printed version of each order or report. But access to these is extremely limited and can only be obtained with the unanimous permission of the Captain, at least one Commandant, and the Aspirant-Archivist. A good example of a standard template group that each new member of the Brigade has access to is this:

• [1] - Hades Brigade Internal Communications
  
• [2] - Hades Brigade Reporting Channel
  

That is, going back to the above key system, using key “A” will allow the agent to handle messages in both the first and second communication channels. Perhaps, some exception to the rule may be the internal communication channel - the agent will be able to see replies to its messages, but will not be able to reread its own messages.

PREVENTION OF UNAUTHORIZED WORK

By relying on the code system, we are able to track the sending of certain messages both inside and outside the Brigade. The automatic alarm system allows us to determine at a glance what message has been sent and how it was sent. That is, the principle of the code as such works as follows:

1. You follow all the steps to access the template.
   
2. You start working with the template according to the preset code.
   
3. You send the generated message via the preset communication channel. At this point, the template code you have received is activated and the message is checked to see if it corresponds to the sending location. If everything is in order, the system counts it and the message is sent.
   

That is, in any case, we will know what you are doing. All archivists have a key "A5", and the Aspirant Archivarius - "A4". Since Order neural-net differs from the general neural-net of the Sirius sector, it is much easier for us to install automatic blocking to send messages outside of Brigade to third parties. Thus, if you send a template message anywhere else, then the key will work again, the blocking is activated, and we will view the sending to the correspondence to the order. If sending of the message was allowed, then case is going to be added as the "exception". If not, this is considered a violation of the internal procedure for sending messages.

Noticement examples

---

This message is compiled from templates compiled by the 34th Brigade security division and approved by Order High Command effective April 2, 835 A.S. Transmission of the message into the hands of third parties is authorized with the written permission of the Brigade Commander or the Brigade Commandants. Any other cases will be considered a crime against the Order and will be punished in accordance with the law on violation of the secrecy provisions of internal communication. Attempting to change the internal code of the message will be treated the same way.

---

---

The filler of the form agrees that it may be archived and made available by the Brigade to other units of the Order as well as to the Order High Command in the future. Copy form encoding and security protocols are active. The coding conforms to the Order's general encryption norms - №835-4-34-2. If you found this form in open neural-net, inform the Brigade chief of secret service immediately!

---

BACKUP COPYING

As a rule, there are cases in which a third party managed to circumvent standard locking methods and get access to editing the template. In this case, the system cannot determine whether the stranger really has access to the template or not. Therefore, any editing occurs in the reserve storage of files, and not in the main communication channel.

In this case, the following is provided: any attempt to edit the template automatically sends it to the backup storage, stopping any attempts to edit it directly in the communication channel. If a person really has access to editing, then he also has access to a reserve storage, which will be essential as a copy of the "group" of templates, but empty. It is filled with whether the template is sent there or not.

It looks like this in stages:

1. You open the template.
   
2. You activate the A4 or A7 key. The system automatically sends the template to the backup storage, the alarm is activated, the blocking is applied to any work in the communication channel with the template.
   
3. After checking the conformity of the order, access to the reserve group of templates is provided, where editing itself is already taking place.
   
4. Upon completion of editing, the template is returned to its place again, and individual lock is applied to previous messages.
   

The use of individual locks means that the previous template is archiving, and access codes for it are updated. This means that the old access codes cease to be valid (with the exception of A7), new ones are generated and being shared between Brigade members. For greater reliability, the transfer of codes usually occurs through the agents of the Order across the Sirius sector. This does not take too much time, but avoids information leaks.

ASPIRANT JIMMY MANDERSON
34TH HADES BRIGADE
23/01/832