New icanhaz features: reverse DNS and traceroutes

After adding some upgrades for icanhazip.com, I wanted to go a bit further. Adding reverse DNS (PTR) lookups and traceroutes seemed like a decent idea!

Want to beta test some new features on icanhazptr.com and icanhaztrace.com? Give them a try!

Getting your reverse DNS entry is easy:

$ curl -4 icanhazptr.com
ord.icanhazip.com
$ curl -6 icanhazptr.com
ord.icanhazip.com

Traceroutes are straightforward as well:

$ curl -4 icanhaztrace.com
traceroute to 166.78.118.193 (166.78.118.193), 30 hops max, 60 byte packets
 1  212.111.33.229  20.031 ms
 2  212.111.33.233  1.011 ms
 3  149.11.30.61  107.976 ms
...
$ curl -6 icanhaztrace.com
traceroute to 2001:4801:7818:6:abc5:ba2c:ff10:275f (2001:4801:7818:6:abc5:ba2c:ff10:275f), 30 hops max, 80 byte packets
 1  2a01:7e00:ffff:0:8a43:e1ff:fea3:fa7f  2.183 ms
 2  2001:4d78:fe01:2:1:3:b90:1  1.330 ms
 3  2001:978:2:45::d:1  8.388 ms
...

While this sits in beta, here are some things to keep in mind:

  • If a PTR record doesn’t exist for your IP address, your IP address will be returned
  • Failing traceroutes will cause your IP address to be returned
  • A PTR record will be chosen at random if multiple PTR records are returned
  • PTR lookups for traceroutes are currently disabled

Let me know if you find any bugs.

Tagged , , , , , ,

drbd 8.4.2 for Fedora 18

Fedora Infinity LogoIf you use DRBD on Fedora 18, there’s a new client tools package on its way to the stable repositories. The kernel module for DRBD was bumped to 8.4.2 and the client tools have been updated to match it.

This fixes a bug that was submitted earlier this month.

Tagged ,

Thoughts on RSA Conference 2013

Moscone Center San FranciscoThis year was my first opportunity to attend the RSA Conference and I learned an unbelievable amount inside and outside the sessions. Here’s are my takeaways from the conference:

Be flexible and raise awareness
BYOD was a hot topic at this year’s conference and I was fortunate enough to sit in with a Peer2Peer session with 24 other attendees. One security team member from a large company talked about how they reduced their stress level and increased their effectiveness by focusing on securing the data rather than trying to secure every single device on their network. It seems trivial at first, but after additional thought, it really makes sense. Allowing every single device ever made onto your network might not be an option, but there are many actions we can take to make it more difficult for non-trusted machines to access sensitive company data.

Security awareness was talked about often. No matter how much a company spends on security products, a single user clicking on a phishing email can open the door for attackers. It’s critical to make security awareness real by making it personal. When users think about more of their actions before taking them, the overall security of the business increases. One of the speakers made a good point that the job of a corporate security team in 2013 is to keep the business secure while allowing employees to soar and do what they do best. The days of blocking access to everything are over.

Maintain and constantly re-evaluate focus
Securing your entire company isn’t possible so put your focus on the things that matter most. Wrap security around the most important data you have and shore up security in areas where you are threatened most often. A presenter noted that everyone has legacy baggage in their companies but the stronger companies think about the baggage they leave behind before they create it.

Follow your users
The whole idea of encouraging collaborative security between corporate security teams and the business seemed to surprise attendees the most. One of the talks pushed security departments to learn about what users within the company are doing and how their needs are evolving. This allows security teams to shift focus, modernize, and provide useful, secure alternatives for employees.

Bring outliers into corporate security
The most moving talk I attended was from Winn Schwartau titled Solving the Cyber Security Hiring Crisis – Hiring the Un-Hireable. He had a no holds barred talk about the “hiring crisis” in information security because we’re looking for the wrong types of people. Winn claimed that we’re looking for clean cut people for corporate security while we should be considering a larger applicant group. His critical point was that deception should be one of the few reasons (other than lack of skills) for not hiring someone and he offered up several questions to ask to look for deceptive behavior. Questions like “How many times have you hacked illegally?” and “Do you illegally download music or movies?” worked well in his experience.

He ended with a quote that I must emphasize:

If it’s important, you’ll find a way. If not, you’ll find an excuse.

Summary
Overall, the conference was well worth the trip. The delegate pass price was quite steep but there were tons of conference organizers and security guards who were happy to help attendees. There was rarely a time where sessions where scheduled and none of the available sessions interested me. It was an awesome experience to see Vint Cerf in person and I’d recommend taking the time to listen to him talk if you ever have the opportunity.

As a side note, I noticed that security awareness among conference attendees was extremely poor. I’ll save that for another post.

Controlling sensitive company data means losing some control of it

This year’s RSA Conference was full of very useful content but the most useful session for me was a peer to peer discussion regarding BYOD on mobile devices. The session had room for about 25 people and many companies were represented. Some companies were huge, household names, while others were very small.

The discussion started around how to authenticate and manage mobile devices, but it soon ended up covering the handling of data on personal and company-issued devices. A corporate security leader for a large company said the healthiest shift for them was when they stopped focusing on the devices themselves and moved their focus to the data they wanted to protect. They found that they could lock down all the devices in the world, but their employees would mishandle the data no matter what actions they took to protect the endpoint.

That led me to start a ruckus on Twitter:

Which I soon followed with this:

The responses started piling up in a hurry. (To see the verbatim responses for yourself, click the date on one the embedded tweets above.) Here’s a quick summary of the suggested ways to attack the problem from the tweets I received:

  • Education & awareness – Ensure that users not only understand where they should keep confidential data but also ensure they understand how to classify the data they’re handling.
  • Provide alternatives – If users like the functionality of a particular product, try to purchase an enterprise version of the product or re-create the product internally. Users will be more likely to use the approved version of the product and the company will have a bit more control over the data.
  • Top-down policies & enforcement – Make policies that define where data can and cannot go and follow that up with enforcement and accountability.
  • Deny access – Set firewall or DLP policies to disallow access to certain products while on the corporate network. This doesn’t cover situations where employees are off the corporate network.

Many people suggested a blend between educating, providing alternatives, and enforcement. This is a real change for corporate IT and security departments that would normally opt for denying access to unapproved applications entirely. This quickly turns into a game of cat-and-mouse in which there are no clear winners.

Take an example like Evernote. If I was blocked from accessing it at work, I could VPN into another location and send Evernote over the VPN. If VPN access was blocked, I could start an ssh proxy and send the Evernote traffic through it. If ssh was blocked, I could remotely access another system via RDP or VNC where Evernote was installed and use it there. The truly frustrated user might invest in a 3G/4G device and use that in the office instead. That’s even worse for the security department since none of their traffic would be passing through the corporate network.

Here are my suggestions for protecting data at a modern company:

  1. Listen to your users – Find out why users like a particular third party application and why they don’t like the current tools provided by the company. Learn about the types of data they’re storing on that third party application.
  2. Regain some control of your data through alternatives – If your users prefer a particular application, try to purchase an enterprise or self-hosted version of the application. Your users will be pleased since they get the functionality they expect and the security teams can gain a little more control over the data stored in the application.
  3. Make a solid data classification policy – Creating an easy to use data classification policy is the first step to securing your data through awareness. Employees need to identify the sensitivity of the data they’re handling before they can know what they can and can’t do with it. Make the data classifications easy to identify and ensure that users have an escalation point they can use when they have questions or they need to release sensitive data.
  4. Create enforcement policies – If a user deliberately disobeys corporate policy, this where the rubber meets the road. Ensure that the policy is fair to users of various technical levels within the company and vet it thoroughly with your legal and HR departments. These enforcement policies may be required by various compliance programs, so check to see if they’re on paper but not enforced.
  5. Educate users about sensitive data – Humanize your data classification policy and help users understand how to identify and handle sensitive data. Remind employees about the importance of company data and what can happen if it was misplaced or stolen. There will be a significant amount of questions coming from this process so be sure that you’re ready to tackle them. If you do this right, you’ll get employees policing themselves and their peers.
  6. Rinse and repeat – Regularly check in with users to verify that the internal applications are meeting their needs. Go through the awareness work on a regular basis. When policies become dormant or ineffective, revise them to meet the current needs.

This problem isn’t going away anytime soon and it’s rapidly evolving. Your corporate security department must evolve with it. A coworker of mine hit the nail on the head with this:

The best thing about this approach is that it scales better and is more effective than denying access. It takes a significant amount of work up front for a corporate security department, but it pays off in the end. Employees soon call out other employees for poor security hygiene and they become informal delegates of the corporate security team. Security can go viral in your organization just like the usage of third party tools.

The key to success is driving security innovation within your company that equals or outpaces the innovation coming from third party applications.

New tools and services may appear on a daily basis, but if your employees know what belongs there and what doesn’t, they’ll do your work for you.

Tagged ,

I’m recruiting at the RSA Conference in San Francisco

Rackspace HQ - The Castle - San Antonio, TX

Rackspace’s HQ in San Antonio, “The Castle”

RSA: Recruiting Security Architects — that’s what I’m doing! (See what I did there?)

Are you planning to attend the RSA Conference in San Francisco this year? Are you looking for a new career with a security team that strives to break the mold of traditional security? If so, apply for the open position and let’s meet at the conference. I’ll be glad to answer questions about what makes security at Rackspace so unique.

We’re looking for enthusiastic Security Architects who think that securing a company as dynamic as Rackspace is more than just a job. Our team constantly finds new ways to do the traditional work of securing the business. We still do much of the traditional security work, like assessments, compliance programs, and incident response, but we take an entirely different approach. Imagine a security environment where policy creation is collaborative with less friction when it comes time for implementation. That’s just the tip of the iceberg.

Interested? Get in touch with me to learn more.

Tagged , ,