QUOTE (UmaroVI @ May 22 2012, 04:19 PM)

3) Okay, so that thing you are slaving stuff to? Strong Encrypt it. That will slow hacking attempts down. However, Firewall/Analyze, on its own, is not going to catch a decently equipped hacker with a Stealth program. Seriously, Firewall 6, Analyze 6 is only 12 dice, Stealth 6 requires 18 dice on average to catch. However, against Matrix Perception Tests made by an icon, it's Hacking+Stealth vs. Computer+Analyze, which is much better. This means you need something sitting on your node, spamming Analyze on anything and everything it sees. Something like a Paladin sprite or another hacker or a technomancer would be ideal, but if not, use an Agent. Make sure to optimize it's MPT: that means in particular Optimization (Analyze) and the Home Ground autosoft.
Optimise the node for Firewall, and it's 13 dice.
Also, where are you getting that Stealth is going to need eighteen dice to catch?
If you're Hacking on the Fly, the node gets to roll it's Firewall+Analyze as an extended test with an interval of 1 Combat turn, against a threshold equal to your Stealth program - so, 5 or 6. Meanwhile, you're using Hacking + Exploit, same interval, against a threshold of the node's Firewall. +3 for Security, +6 for Admin. So the hacker's threshold is likely to be 12, the node's threshold is usually going to be 5 or 6 (against PC-scale hackers). When the node detects the hack attempt, a Restircted Alert is triggered - giving the node a +4 die pool bonus against the hacker. Suddenly, 12 dice (Firewall 6, System 5, optimised) becomes 16 dice, to try and simply disconnect the hacker.
If the hacker takes a slow-and-careful approach, the Node gets only one check to see if it notices you ... using Firewall+Analyze, against a threshold of the hacker's Stealth. But, you see,
that step is why there's an Agent running on the node, or an adjacent one, running Analyze
constantly.

Meanwhile, with the same thresholds of 6, 9, or 12 ... and intervals of 1 hour or 1 day? Getting in will take a serious amount of time. Time during which a scripted, scheduled
reboot might happen.
...
Hacking isn't all that easy, when the system architect has half a clue.