| From: | Mike Elkins <MikeE@*********.COM> |
|---|---|
| Subject: | Re: Weird Campaigns -Reply -Reply |
| Date: | Tue, 19 May 1998 16:35:42 -0500 |
>> > Alert status can be worked around; the alert is sounded
>> > universally, but security tallies for each decker are SEPERATE
>> > (otherwise, IC would jump EVERYBODY, even legit users).
>>
>> No, legit users have valid passcodes and attempt "suspicious"
actions
>> infrequently. Tallies are global, which is why the first few entries on
a
>> security sheath are things like probe or white ice--otherwise the first
>> dweeb who forgets his passcode and asks for the wrong file gets
>> phychotropically altered.
>>
<then MCP wrote:>
>But what happens when there is a decker in the system who has
> upped the tally to a dangerous level (say one or two points short of
>black ICE), and the VP of Engineering tries to log on, and types his
>password wrong?
Well, what happens is the system kicks off the back ice, which then
figures out what it should attack. Most of the tally came from the
decker, and just a little came from the VP. The ICE decieds to kill the
decker first, then locks out the VP's session, preventing future log in
attempts. VP fumes, but when shown the system logs indicating that
the ICE encountered a decker, has to admit that it was "just doing it's
job". Note that to get the Black ICE, the previous security sheaves found
something wrong and flaged it, so the ICE has a pretty good idea of
where the decker is (subject to Masking and Evasion, of course).
System designers who put Black ICE in early sheaves deserve what
they get (occasional toasted employees).
Double-Domed Mike
