ever get this error in firefox?
if i accept a ssl certificate with an attack proxy (such as burp suite) in the middle, then later go back to the same site without the proxy, i get this error.
and i can’t do anything about it.
not fun.
:/
Recently I had a financial-sector client contact me regarding tools and techniques for security and reputation monitoring. The client had recently had their web site scraped and placed under a similar domain. It was apparently a simple identity theft attack (on arbitrary users), but it scared them nonetheless.
Wanting to prevent or minimize the risk of this type of thing, they were in need of some simple reputation and keyword monitoring tools, so we came up with a few immediately:
You’ll want to pick some keywords to monitor. Other folks have talked specifically about what keywords you should be monitoring. It’s also a good idea monitor your website for those specific keywords with Google’s power search operators (inurl: and site:)
Then we started thinking about monitoring for more direct IT security issues. Several things came to mind immedately, such as:
You should also be monitoring your domain to ensure you don’t have any google dorks showing up within the domain. You can do that by setting up google alerts such as:
You’ll definitely want to get analytics on your website, and monitor where your users are sourcing from. This will provide additional lists of sites that are linking to you. There are definitely some IRC and forums it would be handy to keep an eye on. we’ll save that for the commercial version of this article 
Thinking a bit more in-depth about what classes of things you’d want to monitor, i come up with a couple classes:
Thoughts? Other sources which should be monitored?
notice anything conspicuous about those serial #’s?
that’s okay, a vanity phone number will do. google voice now allows you to search for numbers when you sign up. it’s the little things.
and you can find me at: http://www.facebook.com/jonathan.cran. 
i currently have the worst bio i’ve ever seen. must fix that.
fyi, wordpress has issues:
http://seclists.org/fulldisclosure/2009/Jul/0057.html (thank you, core)
A vulnerability was found in the way that WordPress handles some URL
requests. This results in unprivileged users viewing the content of
plugins configuration pages, and also in some plugins modifying plugin
options and injecting JavaScript code. Arbitrary native code may be run
by a malicious attacker if the blog administrator runs injected
JavasScript code that edits blog PHP code. Many WordPress-powered blogs,
hosted outside ‘wordpress.com’, allow any person to create unprivileged
users called subscribers. Other sensitive username information
disclosures were found in WordPress.
Google Voice turns out to be really handy for phishing attacks. When you send out a phishing email, it’s useful to include a phone number, in case of any issues with the attachment, link or other payload.
Google voice gives you a (new, anonymous) number which you can route wherever you’d like (cell, office, etc). Additionally, you can configure your voicemail to quickly impersonate the local admin, or security officer.
The killer feature, however, is the voicemail recording and transcription. Never again do you have to wade through a voice-driven mail system. Now, it simply dumps into your inbox for easy inclusion into a report. Additionally, you can download, email and share (via unique URI) voice messages.
Good for demonstrating that you can’t trust links AND phone numbers.
Twitter (jcran)
