Tracking Drivers' (Users') Violations
I personally can't recall a policeman looking at my driver's
license in the past 10 years. I'm sure that's not because I have never sped on
the way to work in 10 years; I just haven't gotten caught. Really. So some of
this, I can only speculate about, but I hear that when the police do catch you
doing something wrong on the road, they tend to write it down. These days, that
information ends up in a database so that the police department can notice
trends. For instance, the police might pull someone over for speeding. They
write down the driver's license number and call it in to check whether that
person has had any other violations. It can really help the law-enforcement
guys: "Uhh, Mr. Jones, you've been caught speeding every Friday morning for the
past month. I think we need to take your driver's license away!"
The last "A" in AAA is accounting. The same
servers that perform authentication and authorization services can keep a record
of each request to authenticate or authorize a user.
The most obvious, and probably most important, feature for
accounting is to record and report when users type the wrong password. Although
an occasional typo might be expected, seeing several consecutive attempts by
Fred to connect to a server, but with an invalid password each time, might
signal that someone is trying to guess Fred's password. Accounting features can
record individual attempts, generate reports, and notify personnel if too many
invalid attempts happen in a short timeframe.
Sections
Comments (0 posted)
Syndication
