Difference between revisions of "Operational Security Policy"
From EVE University Wiki
(Added Template:Eunispecific. Changed category.) |
m (Minor lingustic adaptations and addition of a simple definition of Operational Security) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{eunispecific}} | {{eunispecific}} | ||
| − | |||
| − | + | Operational Security is the process by which potential adversaries are denied access to information about operations and activities. | |
| − | + | Since [[EVE University]] has a fairly open recruitment policy, members should never assume full operational security. As we try to allow maximum access for genuinely new players who want to learn EVE, it is not difficult for any player to create a 'fake' new character to put it into EVE University. Players may do that for a variety of reasons, including spying on EVE University or making their character's employment history look genuine so they can spy on another corp later on. | |
| − | |||
| − | |||
| − | |||
| − | + | As a result, members should never assume that communications within any of our channels or fleet activities are secure. While we can never guarantee security of communications, we can reduce the risk of harmful information being leaked. It is therefore requested that members observe the following rules: | |
| + | |||
| + | * Never disclose any passwords to [[EVE University Chat Channels|EVE University chat channels]] to anyone. If someone is allowed to access the channel they will be able to see the password either in the Corp Bulletins (Neocom > Corp > Home > Bulletins) or in this [https://forum.eveuniversity.org/viewtopic.php?f=31&t=23156 Forum Post]. If they cannot view either of these, they should not be in the channel. The ''only'' exception to this rule, is that [[Intake & Progression Department|Intake Officers]] may disclose the password to a successful applicant in the course of an interview if it is needed to get them into the chat channels. | ||
| + | * Do not discuss fleet movements anywhere other than in fleet chat or other chat channels set up by leadership in the fleet for the purposes of the fleet itself. This includes discussing the current or future location of a fleet, and asking for information about an active fleet. | ||
| + | * Do not join fleet channels in [[Mumble]] unless you are a current member of that fleet. The only exception is that [[Directors]] may at their discretion listen in to fleets. If anyone is found to be listening to the fleet communications while not in the fleet they will be removed from the channel and possibly disciplined. | ||
| + | * Be careful when streaming or publishing video recordings not to compromise the safety of any members. This means if the streamer is on an active fleet, they should have at least a five minute delay on the stream. Streamers should also ensure that sensitive information, such as chat channels, are obscured. For more information on our streaming rules see our [[Streaming and Video Publishing Policy]]. | ||
| + | |||
| + | {{EVEUniversityNav}} | ||
[[Category:EVE University Policies]] | [[Category:EVE University Policies]] | ||
Latest revision as of 17:52, 13 October 2023
|
This page is specific to EVE University. Other corporations or groups in the game may operate differently. For a summary of EVE University's rules and code of conduct, see EVE University Rules. |
Operational Security is the process by which potential adversaries are denied access to information about operations and activities.
Since EVE University has a fairly open recruitment policy, members should never assume full operational security. As we try to allow maximum access for genuinely new players who want to learn EVE, it is not difficult for any player to create a 'fake' new character to put it into EVE University. Players may do that for a variety of reasons, including spying on EVE University or making their character's employment history look genuine so they can spy on another corp later on.
As a result, members should never assume that communications within any of our channels or fleet activities are secure. While we can never guarantee security of communications, we can reduce the risk of harmful information being leaked. It is therefore requested that members observe the following rules:
- Never disclose any passwords to EVE University chat channels to anyone. If someone is allowed to access the channel they will be able to see the password either in the Corp Bulletins (Neocom > Corp > Home > Bulletins) or in this Forum Post. If they cannot view either of these, they should not be in the channel. The only exception to this rule, is that Intake Officers may disclose the password to a successful applicant in the course of an interview if it is needed to get them into the chat channels.
- Do not discuss fleet movements anywhere other than in fleet chat or other chat channels set up by leadership in the fleet for the purposes of the fleet itself. This includes discussing the current or future location of a fleet, and asking for information about an active fleet.
- Do not join fleet channels in Mumble unless you are a current member of that fleet. The only exception is that Directors may at their discretion listen in to fleets. If anyone is found to be listening to the fleet communications while not in the fleet they will be removed from the channel and possibly disciplined.
- Be careful when streaming or publishing video recordings not to compromise the safety of any members. This means if the streamer is on an active fleet, they should have at least a five minute delay on the stream. Streamers should also ensure that sensitive information, such as chat channels, are obscured. For more information on our streaming rules see our Streaming and Video Publishing Policy.
