There is already a law on the books called Protected Critical Infrastructure
Information (PCII). It has stiff penalties for leaking the information. The
reporting critical infrastructure company has to request the information or
report be protected under PCII. In most cases the companies also
Another possibility is the use of this tool as well:
http://www.sensepost.com/labs/tools/pentest/reduh (Reduh)
Jerry
je...@jdixon.com
On Fri, Jan 13, 2012 at 12:02 PM, Mark Keymer wrote:
> Hi,
>
> We have had 2 of the below hit us this week. First time was apx 11:20am
> 1/10/2012 (PST). The 2
It's more of a strategy to centralize protection efforts versus using a
de-centralized approach. I want go into the scalability issues and also
"scope" creep aspects however, as Chris points out, it would be far better
to share indications & warnings with organizations that can leverage their
own
Jared nailed it on the head. It is absolutely critical to get to know who
your State JFO POC is, State EOC POC, and have the National Communication
Systems Hotline on speed dial or at least in your cell. They can help
facilitate needs such as getting human resources from your company or mutual
ai
If you can make it they can tax it :/
Article in today's Wall Street Journal:
"WASHINGTON -- Federal regulators are considering whether the government
should take greater control of the Internet and ask consumers to pay higher
phone charges in order to provide all Americans with cheaper access to
placed copper cable in the middle of the winter last
> year, it would have made more sense to just use the conduit they were
> replacing and put fiber in.
>
> But the fiber union guys != copper union guys so that is harder to do.
>
> Oh well, stuck in the 70's with my ISDN.
>
&
6 matches
Mail list logo
