How to survey Dmarc to network room (via YouTube Capture.)
Agari Customer Video - DMARC presented at FS-ISAC Spring 2013 Conference
Agari customers describe why and how they adopted DMARC to protect customers and prevent brand abuse.
Tempest Little Big Band - I've Grown Accustomed to Her Face @ DMARC Cafe - Sun Mar/8/2015
I've Grown Accustomed to Her Face Tempest Little Big Band @ DMARC Cafe, Tucker, GA Sun Mar/8/2015 James Rozzi - bari sax Vinnie D'Agostino - alto sax ...
Telecommunications Expert Andy Kauffman talks about T1 cable, Shielded Twisted Pair cable, and CAT 5 cable as methods of extending the T1 Smart jack (also ...
Yes, CAT 6 is fine, In fact, CAT 3 or better will work fine (is there any CAT 3 still out there?). I still recommend using two runs, one for TX and the other for RX and stay away from anything that generates high amounts of RF interference.
Java Vulnerable to Attacks - Threat Wire
Your weekly round-up of cyber security and hacking news. On today's episode, a website that can fill your entire hardrive, Java is vulnerable, and the new ...
Commonly, there is a culture whereby people in places of authority believe
that if you don't talk about a problem, that it must not exist. This is the
reason we have the security issues we do. If the interest is in actually
solving the problem, that culture must be held to account. Therefore, it's
reasonable, even imperceptive that all exploits are exploited, and machines
compromised. The more public these exploits are, the more they will be
brought into the light. Hiding is not security.
I honestly prefer keeping it to myself. At least until system admins and
politicians get their heads on straight. If someone comes up to you and
says "I found a vulnerability in your code", that should be returned with a
"thank you" and not a "you're under arrest". They had the decency to TELL
YOU ABOUT IT so you can fix it, rather than continue to get exploited until
the end of time. Once people can hit that level, I'd be fine with personal
disclosure. Public is just too embarrassing.
I would usually lean towards public and responsible disclosures. The
problem with responsible disclosure, as is commonly known, is that vendors
are not in any hurry to ship out a patch if they are the only people who
know about the exploit. Public disclosure is a bit more effective at
getting patches out, since it puts more pressure on the vendor, but gives
bad guys more material to make malware. A good combination of the two
disclosures might be good.
If you disclose and the vendor is not ready to roll out a patch or
statement then it is like giving malware makers free ammo. I don't
understand how security firms make money off of controlling disclosure, and
I would really appreciate if someone could explain that.
You don't need to talk like mindless traditional news reporters, add more
natural'ness to your dialogue. It becomes boring when punch lines sound
like being read from a board..
CRACKED, not HACKED, god dammit! It's shit like this that gives real
hackers a bad name. There's a huge difference between hacking and cracking.
Learn it.
Uh yeah, Cisco, Microsoft, java, and other certs just don't teach us what
seagals are, he is not qualified enough to diagnose those birds as a
seagals.