![]() |
Brigade internal access system information - by Jimmy Manderson - Printable Version +- Discovery Gaming Community (https://discoverygc.com/forums) +-- Forum: Role-Playing (https://discoverygc.com/forums/forumdisplay.php?fid=9) +--- Forum: Stories and Biographies (https://discoverygc.com/forums/forumdisplay.php?fid=56) +--- Thread: Brigade internal access system information - by Jimmy Manderson (/showthread.php?tid=207840) |
Brigade internal access system information - by Jimmy Manderson - 34th Brigade - 05-11-2025 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:
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:
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: 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:
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. 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:
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 |