Home page logo

fulldisclosure logo Full Disclosure mailing list archives

Re: Addressing Cisco Security Issues
From: "Micheal Patterson" <micheal () tsgincorporated com>
Date: Mon, 29 Mar 2004 14:45:18 -0600

----- Original Message ----- 
From: "Jason Dodson" <mindchild () yahoo com>
To: "Geo." <geoincident1 () getinfo org>; <full-disclosure () lists netsys com>;
<bugtraq () securityfocus com>
Sent: Monday, March 29, 2004 1:35 PM
Subject: Re: Addressing Cisco Security Issues

I have had a similar run-around with AT&T Broadband and Sprint a while
back, pertaining to a DoS
attack my organization was experiencing. Not to dive into details, to
resolve the issue, I got
them both on the line in a 3-way conversation, and it was taken care of in
less then 5 minutes.
They didn't seem to eager to shrug off the responsibility to someone else,
when that someone else
was right there on the phone.

Jason Dodson

I've had similar situations between former Brooks Telecom (now
WorldComm/MCI) and SBC for pri and DS3 circuit issues. Once I was able to
get both NOC's on the line, they couldn't point the blame at anyone else.
When one side would try, the other would say, well, no it can't be that
because of ... and they started working together to get the problem
resolved. When you're on the line with only one party, it's easy for them to
point to the distant end as a problem.


Micheal Patterson
TSG Network Administration

Confidentiality Notice:  This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original

Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]