|
|
| Security Command |
Security is responsible for maintaining peace within the United Federation of Planets.
| Rank/Title | Name/Alias | Rank Image |
|---|
1 total officers
| Rear Admiral |
Ruslan Lee |
 |
|
|
|
| Security Officers |
| Rank/Title | Name/Alias | Rank Image |
|---|
1 total officers
| Commander |
Taylynn |
 |
|
|
|
|
Security
|
|
|
|
I. Formation
|
The Council of Admiral’s forms the Department of Federation Security of the United Federation of Planets with the purpose of conducting forum moderation, admissions, arrests, punishments, intelligence and investigations This document hereinafter referred to as the "Federation Security Charter" is designed to outline all Federation Security policies and procedures as lawfully promulgated hereto govern Federation Security. To achieve the department’s goals, the following sub-departments are formed: Starfleet Bureau of Investigations and the Department of Starfleet Security. Federation Security is under the authority of the UFP Fleet CO/XO, Council of Admirals, and Operations Command.
I.I Command
The Department of Federation Security will be commanded by a Deirector Federation Security (DFS) and a Deputy Director Federation Security (DDFS) whom will assume the positions of CO and XO respectively.
|
|
II. Starfleet Security
|
Starfleet Security's role will be to monitor forum threads, maintain stability, resolve minor disputes, conduct admissions and protect the United Federation of Planets from internal threats.
II.I Starfleet Security Command
Starfleet Security will have a Constable appointed by the Director of Federation Security. The Constable and Superintendent will serve as subcommand CO and XO. They will be subordinate to the DFS and DDFS. The officers occupying the positions of Starfleet Security CO and XO are required to have achieved a minimum rank of Commander. The only officers with the authority to overrule the CSFS are the Fleet Admiral, Fleet Executive, a vote by the Council of Admirals, Operations Command, the Director and Deputy Director of Federation Security. The Constable will report directly to DFS/DDFS when a fleet-wide situation arises. The Constable shall submit weekly reports to the DDFS.
II.II Manning
A Constable, Superintendent, two Admissions Officers and four Moderators will staff Starfleet Security.
II.III Starfleet Security Members
Any UFP officer of Ensign rank or higher may apply to join the Security Department. When a position is open, the Constable may provide a qualification exam to the applicant(s) to be judged by the DDFS or in the case the DFS should the DDFS be unavailable. Upon approval from command, the Constable may accept new applicants into the department. Security Officers are expected to keep a higher level of maturity and respect. Security Officers will make a mandatory weekly report to Starfleet Security Command who will in turn file a monthly status report to Federation Security Command a copy each to the DFS and DDFS. Starfleet Security Members are bound to this charter by accepting their position in Starfleet Security. Violating this charter is a violation of an order and will be disciplined as such.
II.IV Admissions
Only the DFS, DDFS, Councilors, Constable, Superintendent and Admissions Officer’s may approve oaths and accept officers into the Academy. Admissions Officers will perform IP Checks on UFP’s IP Database and perform a reverse DNS lookups. Any anomalies or signs of a proxy should be reported to the Constable or DFS or DDFS as soon as possible using the available Chain of Command. Only Councilors may accept oaths of returning members. If pending Council intervention is present within an oath; Security’s authority is superseded by that of a councillor. Security members will continue to monitor recruits during their stay at the Academy.
II.V Theard Moderation
The DFS, DDFS, Constable and Security Moderators will be responsible for maintaining an environment on the forums in accordance with fleet policy. Vigilance is required for detecting any suspicious activity and this will need to be reported to the Constable. Starfleet Security Members are only authorized to edit threads. Deletions and locks will only be made by the approval of Federation Security Command, The Constable, or the Council of Admirals. If a Starfleet Security Member feels a thread is becoming unstable and damaging to the fleet, they may move it to the Starfleet Security forums for review by Starfleet Security Command. Starfleet Security members should only edit a thread if the thread contains excessive cursing, threats, obscene sexual remarks, spamming, or anything that is considered a violation of the Code of Conduct. For any questions concerning this, follow the discretion of the Constable. Security Officers will not edit posts where the Constable, Federation Security, or a member of the Council of Admirals has decided not to.
II.VI Forum Moderators
All forum moderators fall under the command of Starfleet Security in the matter of moderating the forums. However, they are not endowed with all powers of Starfleet Security. This includes any UFP Officer with any moderation power on UFP forums, or other assets. The Constable has the final decision on Moderation matters except where a member of the Council of Admirals or Federation Security is concerned. Any member of the Council of Admirals and Federation Security Command may overrule Security Command on moderation issues.
II.VII Disputes Within Starfleet Security
If there is a dispute between two Starfleet Security members, both members will surrender the issue to the Constable, but the senior officer in the dispute authority should be respected as this is the rank and responsibility the Admiral’s Council has placed in him. The Constable will make final decisions concerning locking and deleting threads. If the DFS and/or DDFS are involved in the dispute, the matter will be passed to Federation Security Command.
II.VIII Administrative Access
The DFS, DDFS, Constable, Superintendent, and Starfleet Security members are authorized access to user management sections of the forum’s admin control panel. The required access is the ability to accept cadet’s oaths and assign proper academy access, ban users, and issue arrests. Using the access for any other purpose other than that specifically listed in this paragraph will be considered an abuse of powers. This will be considered a cat II offense and result in the minimum of a demotion and removal of admin access; no matter the good or bad intentions.
|
|
III. Arrests and Charges
|
In the event a UFP member needs to be arrested, the Starfleet Bureau of Investigations will investigate and report to Federation Security Command. Only the Fleet Admiral or as directed by policy may authorize an arrest. Only a councillor, Operations Command, Federation Security Command and the Constable may perform an arrest. When an arrest has been made, the arrested will have their access restricted to the brig. The arresting official has 48 hours to issue formal charges and punishment or release the arrestee, unless the Fleet Admiral authorizes a longer time. Once formal charges are enacted and punishments issued, the JAG will be contacted and made aware. If a charge is appealed, all investigative material will be released to the JAG immediately. Security Officers will follow the JAG charter for trial. Violation of the JAG charter is violation of an order and will be treated as such.
|
|
IV. Starfleet Bureau of Investigations
|
The Starfleet Bureau of Investigations hereafter SBI will be led by the Director of Investigation (DI) with a minimum rank of Commander. The SBI will be responsible for all investigations by Security into any internal incidents on UFP forums. SBI will be manned by three Agents who will all hold equal authority except for the Director who is the highest authority in SBI. Once SBI has conducted an investigation, it will hand all material over to the Department of Starfleet Security for arrests and punishments; if required. The SBI will be responsible for maintaining a blacklist of IP Addresses that are not to be admitted into UFP. The SBI Director can be public fleet knowledge, but SBI agents must remain secret to all except the Admiral’s Council, DFS, DDFS, and the Constable. Revelation of a SBI member will result in a demotion of the officer responsible for the exposure and expulsion from SBI of the member exposed unless the officer responsible for the exposure is a member of the Admiral's Council or the DFS.
|
|
V. Powers and Roles
|
V.I Director of Federation Security
- Detention, punishment of cat II offenses, bans
- Thread deletions, closures, moves and edits
- Appointment/Removal of all DFS, SFS, and SBI staff members and commanders
- Approve or disapprove admission into the UFP member body
- Work with foreign security representatives to achieve community security
- Maintain a database of user’s ip addresses and a blacklist
V.II Deputy Director of Federation Security
- Punishment of cat II offenses, bans when the DFS in unavilable for 24 hours
- Thread deletions, closures, moves and edits
- Appointment/Removal of all SFS, and SBI staff members excluding the DI and CSFS
- Approve or disapprove admission into the UFP member body
- Work with foreign security representatives to achieve community security
- Maintain a database of user’s IP addresses and a blacklist
V.III Constable and Superintendant
- Thread deletions, closures, moves and edits
- Appointment/Removal of all SFS staff members
- Approve or disapprove admission into the UFP member body
V.IV Director of Investigations
- Work with foreign security representatives to achieve community security
- Appointment/Removal of all SBI staff members.
- Maintain a database of user’s IP addresses and a blacklist
V.V Starfleet Security Members
- Thread deletions, closures, moves and edits
- Approve or disapprove admission into the UFP member body (Admissions officers only)
V.VI Investigations
- Work with foreign security representatives to achieve community security
- Maintain a database of user’s IP addresses and a blacklist
|
|
|
|
|
