- Joined
- Apr 18, 2015
- Messages
- 3,229
- Reaction score
- 1,800
Sector Monitoring (SM) Dataplague
AFFILIATION
Sector Rangers
MANUFACTURER
Darmus Onn
TYPE
MalwarePOWER SUPPLY
Computer System Power
SENSORS
N/A
SIZE
N/A
COMPOSITION
Electronic Code
A dataplague - also known as a computer virus - is a type of malignant computer program often used by slicers and other criminals to attack, incapacitate or otherwise infiltrate electronic devices such as computers and droids. At their simplest, dataplagues can be nothing more than self-replicating code, which spreads in the memory banks of an infected system until it has consumed all available storage and run-time, causing the system to crash. At their most complex, dataplagues can be sophisticated artificial intelligence entities, capable of subverting entire networks to their will.
The Sector Monitoring Dataplague is a code written by Sector Ranger Darmus Onn to aid in various law-and-order pursuits. It is strictly being used by the Sector Rangers, however, since not everyone is as savvy as the original creator it is possible that the code itself is either duplicated from an infected server or outright copied from the datacard, thus creating a black market variant.
As the name implies, the SM dataplague was created for monitoring purposes (IE intelligence gathering and data theft) and designated with Class 3. This means that once infected in a local server it will allow the rangers to monitor all activity of said server and spread through connected datacards and devices. For example: If a spice dealer on Coruscant is infected, the dataplague can, over time, end up identifying the supplier of spice on Kessel and everyone that is involved in the crime (including senators, crooked local security officers, shipping companies etc).
Infecting a system with a dataplague is simple; the pathogen can be introduced using standard datacard, a connection to a previously infected system, or really any method of electronic data transfer. Once introduced, a dataplague must be given time to take hold, the amount varying depending on the class of dataplague; a class 1 plague will require 1 posting round to take hold, a class 2 will require 2 rounds, and a class 3 will require 3 rounds. If the infection process is interrupted - say, the power is cut, or a slicer begins a counter-dataplague scan - the round count must be reset, or the attempt can be considered a failure.
Once introduced, dataplagues are not simple to get rid of, although this can be accomplished by a decent slicer. 1 posting round is required for a slicer to properly diagnose the type of dataplagues - or dataplagues - present in a system, and additional rounds are required to eradicate the infection. For a class 1 dataplague, 1 round is required, for class 2, 2 rounds, and class 3 will need 3 rounds. If the process is interrupted, the round count must be reset, or the attempt can be considered a failure.
Upon eradication of a class 3 dataplague, 1d6 must be rolled to determine success. If a 1 is rolled, the dataplague is to be considered in remission. At the start of each thread where a device previously infected with a dataplague is used, roll 1d100; if a roll of 10 or less is made, the previously "deleted" plague will reinfect the device. Another attempt to remove it can be made using the methods described above.
01000111 01100101 01110100 00100000 01100001 00100000 01101000 01101111 01100010 01100010 01111001 00101100 00100000 01110000 01101100 01100101 01100001 01110011 01100101 00101110 00100000 01010100 01101000 01101001 01110011 00100000 01101010 01110101 01110011 01110100 00100000 01110011 01100001 01111001 01110011 00100000 01100100 01100001 01110100 01100001 01110000 01101100 01100001 01100111 01110101 01100101 00101110
AFFILIATION
Sector Rangers
MANUFACTURER
Darmus Onn
TYPE
MalwarePOWER SUPPLY
Computer System Power
SENSORS
N/A
SIZE
N/A
COMPOSITION
Electronic Code
DESCRIPTION
A dataplague - also known as a computer virus - is a type of malignant computer program often used by slicers and other criminals to attack, incapacitate or otherwise infiltrate electronic devices such as computers and droids. At their simplest, dataplagues can be nothing more than self-replicating code, which spreads in the memory banks of an infected system until it has consumed all available storage and run-time, causing the system to crash. At their most complex, dataplagues can be sophisticated artificial intelligence entities, capable of subverting entire networks to their will.
The Sector Monitoring Dataplague is a code written by Sector Ranger Darmus Onn to aid in various law-and-order pursuits. It is strictly being used by the Sector Rangers, however, since not everyone is as savvy as the original creator it is possible that the code itself is either duplicated from an infected server or outright copied from the datacard, thus creating a black market variant.
As the name implies, the SM dataplague was created for monitoring purposes (IE intelligence gathering and data theft) and designated with Class 3. This means that once infected in a local server it will allow the rangers to monitor all activity of said server and spread through connected datacards and devices. For example: If a spice dealer on Coruscant is infected, the dataplague can, over time, end up identifying the supplier of spice on Kessel and everyone that is involved in the crime (including senators, crooked local security officers, shipping companies etc).
Infecting a system with a dataplague is simple; the pathogen can be introduced using standard datacard, a connection to a previously infected system, or really any method of electronic data transfer. Once introduced, a dataplague must be given time to take hold, the amount varying depending on the class of dataplague; a class 1 plague will require 1 posting round to take hold, a class 2 will require 2 rounds, and a class 3 will require 3 rounds. If the infection process is interrupted - say, the power is cut, or a slicer begins a counter-dataplague scan - the round count must be reset, or the attempt can be considered a failure.
Once introduced, dataplagues are not simple to get rid of, although this can be accomplished by a decent slicer. 1 posting round is required for a slicer to properly diagnose the type of dataplagues - or dataplagues - present in a system, and additional rounds are required to eradicate the infection. For a class 1 dataplague, 1 round is required, for class 2, 2 rounds, and class 3 will need 3 rounds. If the process is interrupted, the round count must be reset, or the attempt can be considered a failure.
Upon eradication of a class 3 dataplague, 1d6 must be rolled to determine success. If a 1 is rolled, the dataplague is to be considered in remission. At the start of each thread where a device previously infected with a dataplague is used, roll 1d100; if a roll of 10 or less is made, the previously "deleted" plague will reinfect the device. Another attempt to remove it can be made using the methods described above.
LEGALITY
This code his highly illegal if not used by Sector Rangers for ranger businessINTENT
To introduce a Sector Ranger specific malware for use against criminal elements (and the Sith). As per the original write-up for dataplagues I'm giving it its own write-up.