This is my inaugural post in the security Blogosphere and what better place to start than with who am I and why I'm here...
Over the past six years I have been working on information security software. My first project was on an automated certificate renewal system for Entrust. My current project, being developed for my employer Third Brigade, is an enterprise-class server and application protection system called Third Brigade Deep Security. It's a combination host-based Firewall, Deep Packet Inspection, Log Inspection, and Integrity Monitoring system. My role specifically is as the Software Architect for our Manager component, which is responsible for configuring and monitoring thousands of software agents.
To that end, you will likely find posts on this blog relating to secure development, usability, visualization, metrics, virtualization, and the security technologies I mentioned. What you're not likely to see are postings about the latest exploits, compliance, or risk management. These topics are well-covered by many of the existing security blogs.
That brings me to the question: why am I starting a blog? I'm a firm believer in a good challenge. If you're not being challenged, you're probably not growing. Posting interesting and relevant content on my areas of interest in information security is certainly a challenge. Unlike emerging exploits, topics like secure development, usability, visualization and metrics don't move nearly as rapidly, yet I believe there is still a lot to be explored. I'm also here because of people like Jeremiah Grossman, Alan Shimel, Christofer Hoff, Michael Howard, Anton Chuvakin, Joanna Rutkowska and many more of the talented security bloggers out there. They contribute so much of their valuable time educating (and sometimes entertaining) the rest of us, and I find that very inspiring.
I've chosen 'Developing Security' as the blog title because it relates to both development of security software and to the fact that security is an ever-developing topic. I hope to cover topics that not only interest software architects and engineers, but security professionals in general.
Comments