SECURITY PROCEDURES

Most of these procedures are based on common sense relating to the security onboard a Starfleet starship. Any player who deviates from common sense in their posts in relation to violating security procedures will 'suffer' the consequences of their actions. If you wish to do something that includes modifying or bypassing security procedures, please contact the Security Chief, XO or CO for advice, otherwise your character may suffer unintended in-game consequences, or your post may be declared invalid. If so, the reasons will be made clear to you.

-----------------------------------------------

1) Apart from the computer system acting upon established security procedures, only security personnel and Department Chiefs can manually disable all levels of internal force fields.

1.a) All crew can enable all levels of force fields, but once enabled, they are subject to rule 1) above.

1.b) If the enabling of a force field was done with a voice authorisation code from the officer who enabled it, then only the Chief of Security, the XO or the CO can override it.

1.c) All Department Chiefs are able to disable all internal force fields, unless the enabling of the force field was done by the XO or CO.

-----------------------------------------------

2) Monthly medical inspections of all personnel, to ensure that no changelings (Founders) are onboard.

-----------------------------------------------

3) Internal sensors continuously looking out for sudden air displacements within the ship, potentially indicating cloaked or invisible intruders moving around. (Invisible includes those subjects that the computer has been somehow programmed to ignore.)

3.a) Internal sensor modifications of any kind can only be authorised by the CO, XO and Chief of Security (together), without exception, as this is the most important aspect of ship security.

-----------------------------------------------

4) All transporter use is to be authorised. Any unauthorised transporter use will be disabled and prevented by the computer system. Only the Transporter Chief, the Chief of Security, the XO, or the CO, can authorise transporter use. If all authorised personnel are unavailable (dead or off the ship), only then does authorisation go to Department Chiefs.

4.a) There is no internal site-to-site transport, unless authorised by the Chief of Security, the Chief Medical Officer, the XO, or CO, and the destination is only the sickbay or the brig. The Marine Delta Team CO, the XO and the CO, are the only ones who have the authorisation to activate site-to-site transport to any point on the ship for members of Delta Team only.

-----------------------------------------------

5) Anyone transporting onto the ship by unauthorised means will be detected by internal sensors, and a level 10 modulating frequency force field will be immediately enabled around them by the computer and security is alerted.

-----------------------------------------------

6) The computer and sensor system is modified so that all personnel will be identified and located via their bio-signature. The comm badge will also act as a bio-signature enhancer.

6.a) All unauthorised personnel entering the ship will immediately be restrained by force fields and then detained by security.

6.a.i) Security will enable authorisation for visitors and new crew at airlock entry points by scanning them and entering their bio-signature into the computer system and providing them with a comm badge.

6.b) All authorised transports bringing new people onboard will automatically scan those people during transport and enter them into the system as being authorised personnel, with the authorisation being removed once they are transported off the ship, or removed manually by the CO, the XO, or the Chief of Security.

6.b.i) Except when such transport is straight into the brig.

6.c) All personnel inside the brig will be regarded as unauthorised personnel if they step foot outside the area of the cell they are held in, unless authorised by the Chief of Security, XO or CO, and subject to rule (6.a) above.

6.d) Due to the linking of authorised comm badges with bio signatures, ship and computer systems will not respond to any person who is wearing a comm badge that is not their own.

6.d.i) Security will be advised by the computer of any comm badge being worn by an unauthorised person.

-----------------------------------------------

7) The transporters are reconfigured so that transport works on bio-signatures in unison with comm badges (which acts as a bio-signature enhancer).

7.a) If the transporter registers that the owner of a comm badge is no longer wearing it, then the badge will be beamed back onto the ship to prevent the technology from getting into the hands of potential enemies.

7.b) If a crew member's comm badge is attached to an unauthorised person, that person is beamed straight to the brig, and Security, the XO and the CO are alerted. (Transporting of authorised personnel onto the ship while docked will have the authorisation of the XO, as per standard procedures.)

7.c) All off-ship transport of cargo and other non-animate objects is to be authorised only by the XO or the CO first. Without that authorisation, transport is locked down by the computer. (Transporting of cargo and personnel while docked will have the authorisation of the XO, as per standard procedures.)

-----------------------------------------------

8) On away missions, all members will wear transporter enhancer armbands, placed strategically around the leg (underneath the trouser leg).

-----------------------------------------------

9) External sensors will continuously monitor the hull for changes to surface configuration. This will detect external intruders and devices being placed upon the hull.

-----------------------------------------------

10) The Marines will be used as backup for Security in the event of internal unrest, and they will fall under the command of the Chief of Security. However, if there is enemy boarding parties onboard, then Security will provide backup for the Marines, and command is given to the Marine Chief.

10.a) Definition of threat responsibility is: internal threats are the responsibility of Security, while external threats are the responsibility of the Marines.

-----------------------------------------------

11) All hardware and software modifications are by authorisation only.

11.a) Any unauthorised opening of an access panel for any system at any time will result in the systems accessible from that location having all power diverted to redundancy systems, and the area will effectively become 'dead'.

11.a.i) A level 10 modulating force field will immediately drop down around the area, as well as a force field activating inside the wall and replacing the removed panel, and security will be notified. This includes the unauthorised opening of any wall or system paneling, and Jefferies Tube entry points - all access is by authorisation only.

11.a.ii) When security is alerted, they will use internal sensors to determine who is accessing the area and identify them. If it's an authorised crew member who made an error, relevent authorisation will be gained from relevent Engineering or Science Chiefs (as they are the only departments allowed access to ship systems, hardware and infrastructure), and systems will be reactivated for authorised access.

11.a.iii) If authorisation is unavailable or denied, suspect will be beamed to brig and detained for questioning, or until authorisation is granted by relevent Department Chief, XO or CO.

-----------------------------------------------

12) All personnel on duty will have security access as per their assigned duties (eg. authorised work only). Personnel will be assigned duties within an area and will have security access for work only in that area.

12.a) If personnel leaves the assigned work area, their security access will be denied to them outside of their authorised work area and they become unauthorised personnel if they try to modify any computer or ship systems.

12.a.i) If personnel leaves assigned work area, their security access becomes as if they are off-duty, with all relevant levels of authorised access.

-----------------------------------------------

13) All flight vehicles are completely locked down and unable to be activated until authorisation from the Flight Control Chief, the XO, or the Captain, is granted for exercises or missions.

13.a) All maintenance access to flight vehicles are under the same authorisation restrictions as the maintenance procedures on the Scorpion.

-----------------------------------------------

14) All personal projects are to be authorised by the crew member's Department Chief, the XO or CO.

-----------------------------------------------

15) Computer system will not recognise any unauthorised modifications. Modifications must be authorised by Department Chief, XO or CO.

-----------------------------------------------

16) All high-level authorisation by Department Chiefs, the XO or CO is done by personal access codes or voice authorisation.

16.a) All junior crew (Asst. Dept. Chiefs and below) have only authorisation according to their position or what is given to them by members of senior staff.

-----------------------------------------------

If you believe any of the above procedures need to be modified, or new procedures need to be added, please contact the Captain with your feedback. Thank you.