Information Control and Classification/Information Security: Difference between revisions
(Actually, Omega is known by captains and above, which is how the Borg knew about it as well, having done their own experiments and assimilated past captains) |
(typos, minor corrections) |
||
Line 17: | Line 17: | ||
*'''Secret''' - Secret information is information that could harm the Federation if given out to enemies, used improperly or poses an risk to Federation civilians. This information is restricted to specific personnel - and typically, are read into the program. (Example: the physicals of how the Quantum Slipstream Drive integrates into Starfleet Deflectors. The history of how we acquired the QSD is also more than likely still classified as Secret by Starfleet Command. Essentially, any post 2380's technology Voyager produced would be rated Secret as how it works and where it was acquired.). There are several times where characters will generate Secret information - but think twice about applying this. Secret classification should be used sparingly. In many cases, Secret information may be withheld from people even with Top Secret clearances if they are not read into the program. Dissemination Limiters begin to see usage here. <font color=red>'''Any temporal incident not released by the DTI or obviously cannot be classified should be considered Secret'''</font> | *'''Secret''' - Secret information is information that could harm the Federation if given out to enemies, used improperly or poses an risk to Federation civilians. This information is restricted to specific personnel - and typically, are read into the program. (Example: the physicals of how the Quantum Slipstream Drive integrates into Starfleet Deflectors. The history of how we acquired the QSD is also more than likely still classified as Secret by Starfleet Command. Essentially, any post 2380's technology Voyager produced would be rated Secret as how it works and where it was acquired.). There are several times where characters will generate Secret information - but think twice about applying this. Secret classification should be used sparingly. In many cases, Secret information may be withheld from people even with Top Secret clearances if they are not read into the program. Dissemination Limiters begin to see usage here. <font color=red>'''Any temporal incident not released by the DTI or obviously cannot be classified should be considered Secret'''</font> | ||
*'''Top Secret''' - Top Secret information is information that will harm the Federation's interests. Generally, Top Secret is subdivided into special access programs. A blank Top Secret clearance would let you know certain programs exist but wouldn't tell you anything about them. People are read into Top Secret programs only as required. An important note is that there are several Top Secret programs that even someone with a Top Secret clearance | *'''Top Secret''' - Top Secret information is information that will harm the Federation's interests. Generally, Top Secret is subdivided into special access programs. A blank Top Secret clearance would let you know certain programs exist but wouldn't tell you anything about them. People are read into Top Secret programs only as required. An important note is that there are several Top Secret programs that even someone with a Top Secret clearance wouldn't know. Just because you have the clearance doesn't mean that many people would know all that is under this classification. Almost any information Top Secret will be stamped with other dissemination limiters. <font color=red>'''An example is the Omega Directive. This is a very need to know basis. '''</font> | ||
*'''Most Secret''' - A rumored classification, but not one that officially exists. If it DID exist however, Section 31 might fall under it.. (OOC Note: This is also conspiracy theory territory. Please do not use this. It's added just as a thing that is a popular rumour.) | *'''Most Secret''' - A rumored classification, but not one that officially exists. If it DID exist however, Section 31 might fall under it.. (OOC Note: This is also conspiracy theory territory. Please do not use this. It's added just as a thing that is a popular rumour.) | ||
Line 31: | Line 31: | ||
*'''Core Federation Only''' (COREFED): Information tagged this is not to be released to planetary governments or ambassadors unless it's a need-to-know. (Example: Needed.) | *'''Core Federation Only''' (COREFED): Information tagged this is not to be released to planetary governments or ambassadors unless it's a need-to-know. (Example: Needed.) | ||
*'''Not for Public Release''' (NOPUB): Information tagged this is for eyes-only, not to be released. This information must not be above Restricted. (Because anything above Restricted shouldn't be released anyway | *'''Not for Public Release''' (NOPUB): Information tagged this is for eyes-only, not to be released. This information must not be above Restricted. (Because anything above Restricted shouldn't be released anyway.) | ||
*'''Release to <>''' (REL TO ): Information that can be released to a specific stellar nation. Such as the Klingon Empire (usually KLIN), Romulan Star Empire (RSE), Cardassian Union (CAR), for examples. (If it's tagged //COREFED// there may be //COREFED//REL TO VULCAN - for something that only Vulcan needs to know, as an example.) | *'''Release to <>''' (REL TO ): Information that can be released to a specific stellar nation. Such as the Klingon Empire (usually KLIN), Romulan Star Empire (RSE), Cardassian Union (CAR), for examples. (If it's tagged //COREFED// there may be //COREFED//REL TO VULCAN - for something that only Vulcan needs to know, as an example.) |
Revision as of 00:04, 19 May 2015
Divisions and Personnel Assignments |
---|
COMMAND DIVISION | OPERATIONS DIVISION | SCIENCES DIVISION | MARINE CORPS | CIVILIAN CONTINGENT |
1.0 Information SecurityInformation security covers the practice of keeping information secret that could be harmful, the control of dissemination of restricted information, and controlling access and use. The primary method this document examines to achieve information security is security classifications. There are more methods (such as controlling physical access.) 1.1 Basic ClassificationsThe classifications are as follows
1.2 Dissemination LimitersEven with the above classification, information may be desired for specific classes of personnel, allies or planetary governments. In these situations, additional limiters will appear on the information, immediately following the broad classification principle (i.e //RESTRICTED//FOUO//)
1.3 Special Access ProgramsThere are projects or intelligence that needs to be restricted even further for various reasons. Examples include the development of new ship classes, the intelligence gathered by covert listening posts, and ongoing infiltrations of criminal groups. These programs are given codenames, and are all considered Top Secret until declassified. (Examples: The Sovereign class development project was at the time Top Secret Project Sovereign but referred to in any documentation as NOPEBADGER. Currently, it is considered unclassified. However, the project for a new class of ship, referred to as TIGERRUN, is considered Top Secret.) An example (from the Sovereign-class project) is: //TOPSECRET//xNOPEBADGER.
1.4 Examples of Information That Might Be ClassifiedStarfleet (and the Federation) have general guidelines as to what types of information is classified. In certain situations, other kinds of information might become classified, but situations outside the norm are generally also directives from Command. Examples
|
Mission Specialist | Helm/Com/Ops | Engineer | Science Officer | Medical Officer | Nurse |
Intelligence Officer | Security Officer | Tactical Officer | Marine | Counselor | Civilian |
Duty Posts |
---|