1,116
edits
Security (Duty Post): Difference between revisions
no edit summary
Danielwood7 (talk | contribs) No edit summary |
Danielwood7 (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
* It is uncertain what relationship exists (if any) between Starfleet Security and the secretive and unofficial Federation agency Section 31. | * It is uncertain what relationship exists (if any) between Starfleet Security and the secretive and unofficial Federation agency Section 31. | ||
* Aboard Starfleet-run facilities and vessels, security was one of the most important divisions in the 23rd and 24th centuries, combining the armory and MACO functions of the 22nd century. Security personnel served functions both defensive and offensive, ranging from security patrols on board a starship, to guarding prisoners, to firing the ship's weapons, to providing protection during landing party/away team missions, and more. In the 24th century the officer in charge of security on a starship was given the title of Security Chief. | * Aboard Starfleet-run facilities and vessels, security was one of the most important divisions in the 23rd and 24th centuries, combining the armory and MACO functions of the 22nd century. Security personnel served functions both defensive and offensive, ranging from security patrols on board a starship, to guarding prisoners, to firing the ship's weapons, to providing protection during landing party/away team missions, and more. In the 24th century the officer in charge of security on a starship was given the title of Security Chief. | ||
| Line 33: | Line 33: | ||
* ''General Quarters Seven'' - This regulation outlines some of the criteria used to determine when a starship's senior officers should implement the vessel's self-destruct sequence. | * ''General Quarters Seven'' - This regulation outlines some of the criteria used to determine when a starship's senior officers should implement the vessel's self-destruct sequence. | ||
==== ''General Security Procedures'' ==== | |||
* ''Security Clearance'' - Occasionally Security Officers will come across information that exceeds their Clearance. In those instances, they must secure the data without further examination and deliver it to their Senior Officer. If field agents are ever forced to reveal classified information, they should reveal as little as possible and express it in the vaguest terms. | |||
Surrendering - Sometimes Officers are captured by enemy forces. If capture does not jeopardize the mission, an Officer may surrender. If the Officer has a particularly high Security Clearance, they should consider a more permanent method of keeping those secrets. | |||
* ''Hostage Situations'' - Innocent bystanders will sometimes become involved in conflicts between Security Officers and their opposition. In hostage or extortion/demand situations, Security must work to safeguard the lives of hostages to whatever extent possible. However, one person or even a large number of people is not more important than the plans for a weapon that could kill millions or billions. | |||
* ''Taking Prisoners'' - Security Officers will rarely have the opportunity to take prisoners. If working on a friendly or UFP member world, Star Fleet personnel should turn the prisoners over to the local authorities. If they are operating on a neutral or hostile world where such criminals may not be prosecuted for their actions, the Officers should transfer them to the nearest Federation installation or world. Because of diplomatic relations, they may need to do this in secret. | |||
* Under no circumstances should the Senior Officer risk his starship, crew, equipment or data to transport enemies unless there is absolutely no chance that the enemy can take over the ship | |||