System security
- Various references to High Security, Low Security, Null Security, and Wormhole Space redirect here. For the EVE University Campuses focused on student activities in each of these areas, see Hi Sec Campus, Low-Sec Campus, Null-Sec Campus, or Wormhole Campus, respectively. Other campuses are listed at Campuses.
A star system's Security Level is a rough measure of how hazardous that particular system is. Players also commonly use the terms Sec Level, System Sec, Security Rating, and Sec Rating. It is displayed in-game as a number with a single decimal place in the range -1.0 to 1.0. Security level should not be confused with Security Status, which is an attribute attached to a player character.
The security level of a player's current system is always displayed in the System Information display on the upper left of the screen, both in space and while docked.
Known space
There are three general classifications of systems based upon system security: High Security, Low Security, and Null Security.
Empire space
Empire space is the name given to the regions which the four main NPC factions hold sovereignty (High Security and Low Security). In Empire space, whether high or low security, stealth bombers can't use bombs and players cannot deploy bubbles.
High security
High Security systems are those with a security level of 0.5 to 1.0. CONCORD will react to hostile actions between pilots, with the response time ranging from almost instant in 1.0 space to up to 19 seconds in 0.5 space. Players also commonly use the terms High, High-sec, Highsec, Hi-sec, and Hisec.
In these systems, stargates may be patrolled by NPC CONCORD, customs, and/or faction navy ships, and stargates and stations will have sentry guns. Aggression (i.e. committing a Criminal-level offense) will provoke a response from CONCORD and any nearby sentry guns. Aggression resulting in the destruction of another player's ship and/or pod will result in a loss of security status.
Low security
Low Security systems are those with a security level of 0.1 to 0.4. Players also commonly use the terms Low, Low-sec, Lo-sec, Lowsec, and Losec.
In these systems, stargates and stations will have sentry guns (although fewer than in Highsec), but CONCORD will not react to hostile actions between pilots, although any nearby sentry guns will still open fire on the attacking player(s) and unprovoked attacks will cause losses of security status.
Null security
Null Security systems are those with a security level of -1.0 to 0.0. Players also commonly use the terms Null, Null-sec, Nullsec, and 0.0 (pronounced "zero zero", "zero dot zero", or "oh dot oh"). The name originates from a time when instead of showing negative security status the displayed statuses were rounded to 0.0.
These systems are essentially lawless and no NPC organizations will respond to aggression, nor will actions of any kind result in a loss of security status. In nullsec the gloves are off: stealth bombers can use bombs and players can deploy bubbles; players frequently fly under not-blue-shoot-it ('NBSI') rules of engagement.
Null security space can further be split to NPC null and claimable null.
NPC null security space
NPC NullSec is null-security space where the sovereignty is claimed by NPC factions, similar to normal 'Empire' space, and therefore cannot be claimed by capsuleer alliances.
Regions classified as NPC NullSec:
- Curse, claimed by Angel Cartel
- Great Wildlands, claimed by Thukker Tribe
- Outer Ring, claimed by Outer Ring Excavations
- Stain, claimed by Sansha's Nation
- Syndicate, claimed by Intaki Syndicate
- Venal, claimed by Guristas Pirates
Claimable null security space
- Main article: Sovereignty
In the rest of nullsec sovereignty is claimed (or contested!) by capsuleer alliances. Any stations in claimable nullsec will be player-owned and will usually only allow their owners' allies to dock.
| A long, long time ago... |
|---|
| University policy, until March 2014, was that University pilots were not allowed to enter claimable nullsec, unless in a fleet lead by an ILN Officer, in order to preserve the University's neurality. That changed in March 2014, after a successful 1-month experiment, and Azmodeus Valar mailed out "[O]ur month long test of increased Sov Null access has been a success. We will be continuing it indefinitely. This means that anyone can lead a fleet into sovereign null security space for PvP purposes. Do not engage in PvE activities in Sov Null space, and do not participate in structure or sovereignty battles." See this forum thread for more details. This was later updated to allow PvE activities as well, see the Rules of Engagement page on claimable nullsec. |
A regularly-updated map of player-owned territory is available here.
Regions classified as Claimable NullSec:
- Branch
- Cache
- Catch
- Cloud Ring
- Cobalt Edge
- Deklein
- Delve (some systems owned by The Blood Raider Covenant)
- Detorid
- Esoteria
- Etherium Reach
- Fade
- Feythabolis
- Fountain (some systems owned by Serpentis)
- Geminate (some systems owned by The Society of Conscious Thought)
- Immensea
- Impass
- Insmother
- Malpais
- Oasa
- Omist
- Outer Passage
- Paragon Soul
- Period Basis
- Perrigen Falls
- Providence
- Pure Blind (some systems owned by Mordu's Legion and Sisters of Eve)
- Querious
- Scalding Pass
- Tenal
- Tenerifis
- The Kalevala Expanse
- The Spire
- Tribute
- Vale of the Silent
- Wicked Creek
Wormhole Space
- Main article: Wormhole Space
In terms of security mechanics, Wormhole Space ("w-space") is similar to nullsec: CONCORD does not monitor what happens in wormhole pockets, players can use bombs and bubbles at will and aggression will not impact player security status.
W-space also functions differently from known space ("k-space") in that players do not appear in the Local chat channel until they speak in it. This means there could be 1 player or 100 players in a wormhole system and you would not be able to tell the difference just by looking at the local window.
Game Mechanics affected by System Security
Various game mechanics are affected or limited by system security. These include:
- Asteroid types found in asteroid belts. More lucrative asteroids are generally found in lower-security systems.
- General difficulty of rat spawns, including belt and gate rats. More difficult rats are generally found in lower-security systems.
- General difficulty of cosmic anomalies and cosmic signatures. More difficult sites are generally found in lower-security systems.
- Reward level of missions. Greater LP rewards for the same mission are given by agents in lower-security systems.
- Specific types of wormholes will only form in specific classes of space.
- In 0.5 space and below the moons can be mined with refineries.
High security space
- CONCORD destroys any criminal player.
- NPC navies will chase players with very low faction standing.
- Player with a a sufficiently low security status (below -2.0) may be attacked by NPC faction navy ships.
- True capital ships (i.e. ships that specifically require the Capital Ships skill) may not enter high security space.
- Cynosural fields cannot create beacons for jump drives.
Low security space
- CONCORD no longer responds, however NPC guns on gates and stations will respond to illegal aggression.
- Player-Owned Starbases do not require Empire Charters to operate.
Null security space
- PVP aggression does not change player security status.
- Items flagged with the Banned in Empire Space attribute can now be used, including launching bombs, anchoring bubbles, and firing doomsdays.
- Sentry guns do not take any actions towards players who aggress other players.
Wormhole space
- Local chat does not display all capsuleers currently in the system, only those that have recently spoken in Local.
- Frequent and heavy use of the Directional Scanner is recommended.
- No stargates are present, wormholes are the sole means of travel.
- As truesec -1.0, w-space has the highest concentrations of planetary resources.
- Aggression timers do not restrict jumping through wormholes as they do with stargates and docking.
- Cynosural fields cannot create links to other systems.
Anchoring
The security level of a system may limit what may be anchored in that system. [1]
- 0.9 - 1.0: Containers may NOT be anchored. Starbases and starbase structures may be anchored except for structures requiring anchoring corp to have system sov.
- 0.5 - 0.8: Containers, starbases and starbase structures may be anchored except for structures requiring anchoring corp to have system sov.
- 0.0 - 0.4: All containers and starbase structures may be anchored, except structures requiring anchoring corp to have system sov. [2]
- -1.0 - 0.0: All containers and starbase structures may be anchored, assuming that anchoring corp has system sov. Player-built stations may be constructed in systems where the corp building the station has sov (as of this writing, player-built stations are completely indestructible and are limited to one station per system).
True security
A given system's security level is actually a real number between -1.0 and 1.0 (this is known as the system's True Security Level, True-Sec, or Truesec). It is rounded and displayed as the system's security level according to the following rules.
- If the true security is in between 0.0 and 0.05 the security is rounded up to precision.
- Otherwise round to precision.
Many security related mechanics use the true security instead of the rounded security status. For example belt rats and mission rewards.
The true security is not visible anywhere in game, instead it can be found in the official datadump or from ESI API. Many third party mapping tools such as Dotlan also show the true security.
| A long, long time ago... |
|---|
| In the past, truesec values in the range (0.0, 0.5) were rounded half up, i.e. rounded down to 0.0 because all numbers in that range are below 0.5. This was a bug, because EVE considers all systems above a trusec rating of 0.0 to be lowsec but the game displayed their security level as "0.0". This bug not only caused some confusion (there were sentry guns within apparently nullsec systems) but also some problems in the form of inadvertent security status loss in what seemed like nullsec.
This bug was fixed in the Revelations expansion [3], and the game now uses the rules above. This ensures that any system displayed as "0.0" is truly nullsec. Some third-party utilities may not know of the above rules, and so may incorrectly identify some lowsec systems as nullsec. |
Mining
The types of ore that can be found in a system's asteroid belts are determined by a code called the security class of the system. You cannot find out a system's security class directly in-game, but the value is present in the Eve database dumps. In null security space, you can deduce a system's security class from the region it is in, and the truesec of the system.
The security class is a letter from A to J, optionally followed by a number from 1 to 7. For example, Jita is a class "A" system, and S-U8A4 is class "J2". Generally, the higher the number, the better the ore. All security classes are viewable on dotlan via the filters on the region maps.
Ores in empire space
Security class letters A-E are used in empire regions, and systems in the same region may have different letter classes, which makes them less useful. The range of values found in the game are:
| Security class | Truesec range | Ores present |
|---|---|---|
| A | 0.95 to 1.00 | V, Sc |
| B | 0.75 to 0.949 | V, Sc, Py |
| B* | 0.75 to 0.949 | V, Sc, Pl |
| B1 | 0.45 to 0.749 | V, Sc, Py, K |
| B2 | 0.25 to 0.449 | V, Sc, Py, K, J |
| B3 | 0.00 to 0.249 | V, Sc, Py, K, J, Hm |
| C | 0.45 to 0.749 | V, Sc, Pl, Py |
| C1 | 0.25 to 0.449 | V, Sc, Pl, Py, K |
| C2 | 0.00 to 0.249 | V, Sc, Pl, Py, K, Hd |
| D | 0.75 to 0.949 | V, Sc, Pl |
| D1 | 0.45 to 0.749 | V, Sc, Pl, O |
| D2 | 0.25 to 0.449 | V, Sc, Pl, O, J |
| D3 | 0.00 to 0.249 | V, Sc, Pl, O, J, Hm |
| E | 0.25 to 0.449 | V, Sc, Pl, O, K |
| E1 | 0.00 to 0.249 | V, Sc, Pl, O, K, Hd |
V = Veldspar, Sc = Scordite, Py = Pyroxeres, Pl = Plagioclase, J = Jaspet, K = Kernite, O = Omber, Hm = Hemorphite, Hd = Hedbergite.
- Note: "B" class systems in Gallente space (shown as "B*" here) have Plagioclase, instead of Pyroxeres. They should probably be flagged as "D" class, but aren't shown this way in the database.
This table shows the system security classes present in each empire region:
| Region | Security Class |
|---|---|
| Tash-Murkon, Domain, Kor-Azor, Genesis | A, B-B3 |
| Derelik, Devoid, The Bleak Lands, Khanid, Kador, Aridia | B-B3 |
| The Forge, Lonetrek | A, B, C-C2 |
| The Citadel | A, B, C, C1 |
| Sinq Laison, Everyshore, Essence, Verge Vendor | A, B*, D1-D3 |
| Solitude, Placid | B*, D1-D3 |
| Heimatar, Metropolis | A, D, D1, E, E1 |
| Molden Heath | D, D1, E, E1 |
Ores in null security space
The security class is most useful in null security regions, since the whole region will have the same letter code, and the following number is then determined by the truesec of the system.
The following table shows the security class letter used for null security regions:
| Class Letter | Region |
|---|---|
| F | Detorid, Cache, Insmother, Impass, Feythabolis, Tenerifis, Omist |
| G | Stain, Esoteria, Querious, Paragon Soul, Delve, Period Basis |
| H | Vale of the Silent, Tribute, Venal, Geminate, Deklein, Tenal, Branch |
| I | Wicked Creek, Scalding Pass, Great Wildlands, Curse, Catch, Immensea, Providence |
| J | Pure Blind, Syndicate, Fade, Cloud Ring, Outer Ring, Fountain |
| K | Cobalt Edge, Perrigen Falls, Malpais, Oasa, Kalevala Expanse, Outer Passage, Etherium Reach, The Spire |
And this table shows the relation between the truesec and the security class number:
| Class number | Truesec range |
|---|---|
| None | 0.00 to -0.249 |
| 1 | -0.25 to -0.349 |
| 2 | -0.35 to -0.449 |
| 3 | -0.45 to -0.549 |
| 4 | -0.55 to -0.649 |
| 5 | -0.65 to -0.749 |
| 6 | -0.75 to -0.849 |
| 7 | -0.85 to -1.00 |
For instance, Syndicate has a security class letter of "J", and S-U8A4, with a truesec of -0.446, thus has a security class of "J2".
The actual ores which will spawn are given by this table:
| Security Class | F | G | H | I | J | K |
|---|---|---|---|---|---|---|
| Base | V, Sc, Hd, Hm, O | V, Sc, Pl, O, K | V, Sc, Py, Hm, J | V, Sc, Hd, Hm, O | V, Sc, Py, Pl, J | V, Sc, Hd, Hm, O |
| 1 | Sp | G | Hd | J | DO | DO |
| 2 | G | Py | DO | Sp | C | Sp |
| 3 | B | Sp | K | G | B | C |
| 4 | A | B | C | DO | Hm | B |
| 5 | Py | C | Sp | A | Hd | A |
| 6 | M | M | M | M | M | M |
| 7 | Pl | DO | B | K | A | G |
V = Veldspar, Sc = Scordite, Py = Pyroxeres, Pl = Plagioclase, J = Jaspet, G = Gneiss, K = Kernite, O = Omber, DO = Dark Ochre, C = Crokite, B = Bistot, M = Mercoxit, A = Arkonor, Sp = Spodumain, Hm = Hemorphite, Hd = Hedbergite.
- Note that, going down each column, all ores present in the class above also spawn. For instance, "J" systems spawn Veldspar, Scordite, Pyroxeres, Plagioclase, and Jaspet. "J1" systems have all of those, plus Dark Ochre. "J2" systems have everything in "J1" systems, plus Crokite, and so on.
