comStar Firewall alert - PhaseThrough
comStar Firewall alert - PhaseThrough
comStar Firewall alert - PhaseThrough
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
datatrail<br />
Every interaction on the Matrix leaves a record. When a construct<br />
or node interacts with another construct or node, even when<br />
just routing a connection through the Matrix, access IDs are used in<br />
order to identify each different party and avoid confusion and conflicts.<br />
These interactions are typically logged, including the access ID.<br />
This information may be used to investigate what actions took place<br />
(see The Access Log, p. 65) or to track down a particular construct to<br />
its originating node (see Track, p. 219, SR4). For this reason, many<br />
hackers make efforts to spoof their datatrail (see p. 224, SR4), anonymize<br />
their activities (see Proxy Servers,<br />
p. 104), or edit away incriminating logs<br />
(see p. 65).<br />
Subscriptions<br />
In the case of full AR and VR<br />
connections (including the interactive<br />
simsense needed by a jumped-in rigger<br />
and sensible connections needed to<br />
command agents or drones), a simple<br />
data request is not enough. In these and<br />
other cases (see the Actions Needing<br />
Subscriptions table, p. 55), a fast, twoway,<br />
maintained connection called a<br />
subscription is needed (see Linking and<br />
Subscribing, p. 212, SR4). A persona can<br />
only maintain a number of subscriptions<br />
equal to the size of its subscription list<br />
(System x 2). If more subscriptions are<br />
assigned, each additional subscription<br />
over the limit counts as an additional<br />
program run on the node and may lead to Response degradation (see<br />
Matrix Attributes, p. 212, SR4).<br />
networkS<br />
Not all nodes are directly linked to the world-spanning<br />
Matrix. Some are instead gathered in isolated networks, including<br />
corporate, national, and private networks. Some networks exist<br />
only at certain time intervals, and some are never connected to<br />
the Matrix, protected behind wireless-inhibiting walls or other<br />
defenses. Some have various access nodes to other networks and<br />
grids, while others only have one gateway (see Chokepoints, p. 72)<br />
that is heavily protected. In principle, anyone with two nodes has<br />
the ability to form their own network. The most well-known examples<br />
of networks are the PANs that everybody in 2070 carries.<br />
grids<br />
Grids are a series of interlocking networks. Every grid is<br />
run by one or more Matrix service providers, who maintain the<br />
infrastructure of the component networks. Grids are organized<br />
into Local Telecommunication Grids (LTGs), used by cities and<br />
corporations (and also Private Local Telecommunications Grids,<br />
or PLTGs, which are not open to the public), and Regional<br />
Telecommunication Grids (RTGs), which connect the LTGs and<br />
PLTGs in a given state or nation. The RTGs connect together in<br />
a global network to form the Matrix. Space stations like Zurich<br />
Orbital also have links to the Matrix, but maintain their own<br />
private networks.<br />
Unwired<br />
node configUrationS<br />
Certain node configurations are more useful than the standard<br />
network model for security and other purposes.<br />
clusters<br />
Sometimes, you have a lot of low-powered devices, but what<br />
you really need is a single node able to sustain several personas<br />
and/or run a lot of programs at once. For this purpose, two or<br />
more nodes can be linked together to work as one super-node or<br />
cluster with greater processing power. To do this, all the nodes<br />
are linked together and placed<br />
actionS needing<br />
SUBScriptionS:<br />
• Accessing a node*<br />
• Command connections to drones and agents<br />
• Encrypted connections†<br />
• Jumped-in rigger connections to a drone<br />
• Slaved connections (p. 59)<br />
• Tacnets (p. 125)<br />
• Using a program on another node<br />
* An agent run on a persona does not take up an<br />
extra slot, while an independent agent does<br />
† Only encrypted connections that wouldn’t<br />
otherwise take up a subscription slot count. For<br />
example, an encrypted link to an agent takes up<br />
only 1 subscription, not 2.<br />
into cluster mode, requiring<br />
a Computer + Logic (2) Test.<br />
Admin access on each node is<br />
required for this operation. Once<br />
clustered, the group of nodes<br />
is treated as a single node with<br />
effective <strong>Firewall</strong> and System ratings<br />
equal to the lowest respective<br />
ratings of the nodes. The cluster’s<br />
Response is equal to the average<br />
of the node’s Response ratings.<br />
The processor limit is determined<br />
by adding the respective limits of<br />
the nodes composing the cluster<br />
and halving them. Persona limit is<br />
determined by adding the respective<br />
limits of the devices together.<br />
All accounts present in each node<br />
are valid for the cluster node.<br />
Slaving<br />
One node, the slave, may be linked to another node, the master.<br />
In this setup, the master is given full admin access to the slave.<br />
When slaving a node to a master, the slaved node does not accept<br />
any Matrix connections from any other node but the master and<br />
instantly forwards any connection attempts to the master.<br />
Hackers have three options when faced with a slaved node.<br />
First, they can hack in directly to the slave with an additional<br />
threshold modifier of +2, though this requires a physical (wired)<br />
connection to the device. Second, they can hack the master node<br />
(thus gaining access to the slaved node—and any other slaves—<br />
as well), though this node is usually more secure. Third, they can<br />
spoof the access ID of the master node and then spoof commands<br />
to the slave.<br />
ScULpting<br />
The Matrix is not real. It is a virtual environment where the<br />
user only sees what the node shows her. Behind the scenes, nodes<br />
are processing huge amounts of data and performing various tasks<br />
that are not visible to the Matrix user. The virtual environment<br />
was designed to help users better grasp and process the wealth<br />
of available information. Because of this, icons in the Matrix are<br />
interchangeable. Depending on the theme or metaphor of a node,<br />
a piece of data could look like a piece of paper, a crystal block, a<br />
bubble, or even a flying pig. Furthermore, what Matrix users see<br />
depends on what they are looking for and what they are doing.<br />
Modern Analyze and Browse utilities filter irrelevant information<br />
Simon Wentworth (order #1132857) 9<br />
55<br />
Matrix topoloGy . . . . . . . . . . . . . . . . . . . . . . . . . . . . .