OLD - General Org Security

Best Practices

• Utilize the ⁠Condition Codes SOP to understand the current security stance, and the ⁠Encrypted Communications SOP for code-word use.
• Encrypted Com leaks, to include intentionally or accidentally posting or sharing code-word sheets or individual code-words, may be punished with disciplinary measures.
• During antagonization, stream-snipes, or hostile engagements, do not partake in "Global Chat" in game. Aside from general conversation or communication with a client, it is advised to remain out of "Global Chat."

Utilize "Party Chat" if necessary to discuss things with members of RS1, and create a separate "Channel" as necessary to talk with select members of the party or RS1.

• Maintain an understanding of who is on your friends list in game, and do not accept friend requests from people you do not know and trust.
• Upon joining a server, and while playing for long durations, it is advised to perform "SCs", or "Security Checks," of players currently on your server. It is also advised to occasionally monitor "Global Chat" for talk of threats, piracy, etc.

"SC's" also include checking the "Ship Channel" for stowaways when using multi-crew ships.

• No one, except for RS1 party members and a rescue client should be allowed onto RS1 ships. If a client is brought aboard, a party member should remain with and monitor the client at all times. Unless not otherwise preventable, the client should never be allowed into the cockpit.

For major events and especially with a specific location

• Add a stream delay
• Party up in deep space
• Avoid global chat
• Security Checks every 10 minutes
• Cloak and Dagger Stream
• Security Upgrades = Security Force