North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: Security v. Privacy (was Re: Is there anything that actuallygets users to fix their computers?)
Sean Donelan wrote: If it's in the campus we take their word for it the first time (local/dept IT personnel only).The difference being campus machines are null routed rather than Dialups/externals we take their word for it the first time. Second time for campus machines they are usually checked over by a member of the ITS security team. Second time for dialups/externals again take their word for it, however warn strongly about the 3rd time. Third time externals/dialups don't connect with us again. Campus machines - I have yet to have this happen. Already doing this... except we are also actively scanning (new policy) all computers connected periodically. It has taken a loooooooong time to get the train of thought that scanning is a good thing. (FYI using Nessus)Network security is high priority here and it doesn't matter whatSeems like a re-active policy. Why don't you check the computers before Should commercial service providers have the same policy when new customers connect to the network? That is still reactive here, but I see no real reason why it shouldn't be. Or is it considered a bad thing to warn customers about vulnerabilitiesPersonally I feel there are 3 problems.... 1/ Some people are already security concious and will give you merry hell over security scans (filling logs, false positives etc) 2/ Some poeple consider it an invasion of privacy - personally I'd tell these people to go else where if it was upto me. 3/ People install software after installing the machines and getting them connected. / Mat
|