Pandemic Planning Coverage

Over the next few weeks, we will be presenting some blog coverage and a couple of public talks about pandemic planning. Given the current information on the H1N1 virus and the outlook from the CDC & WHO, we feel this to be prudent. I wanted to publish this post to draw your attention to the situation and to reinforce the idea that pandemic planning is the exact process to avoid PANIC.

Planning for situations is a responsible, mature act. Panic is a dangerous, and often disastrous response to a problem. Our goal, over the next few weeks is to get you thinking about pandemic planning. While the H1N1 threat may or may not immediately emerge as a significant issue, planning for such events is, in our opinion, a wise investment.

As we move forward in discussing pandemic plans, it will be in the flavor of disaster recovery and business continuity. Hopefully, you already have a basic plan, and this will serve as more of thought points for evaluation and consideration. If you do not yet have a plan, then please use this coverage as a basis for developing one.

Our framework will be around the primary 3 areas: Technology, Policy and Process and Awareness.

Here is a quick and dirty mind map of the topics we will be covering.

PandemicRough.png

Keep your eyes on the blog for events around pandemic planning and related topics. As always, feel free to let us know your thoughts and comments, as well as any helpful tips you would like to share with others.

Updated Note: Thanks to WordPress for making the above graphic unusable, even when saved. You can download the png image at full (readable) size from here.

On Black Tuesday, RDP Shines

Microsoft patched two privately reported vulnerabilities for RDP today. Yes, RDP. No, not the server, the client. One of the most widely used tools by Windows system administrators is vulnerable to remote code execution. Not good. There is good here though, in order to exploit this vulnerability the user of an RDP client must be tricked or social engineered to connect to a malicious RDP server or a specially crafted website. Also, Microsoft is not aware of an exploit for this vulnerability at the time of this writing. It shouldn’t be long though, as we all know the more popular the software, the more likely there will be an exploit for an existing vulnerability.

Users currently employing automatic updates should see this issue resolved during their next update. For those of us who cannot have automatic updates enabled, we’d recommend getting this patch in during the next maintenance window.

Book Review: VMware vSphere and Virtual Infrastructure Security

VMwarevSphereandVirtualInfrastructureSecurity
VMware vSphere and Virtual In!astructure Security: Securing the Virtual Environment (Prentice Hall) is written by Edward L. Haletky with the assistance of our friend, Tim Pierson. Another friend, Christofer Hoff, wrote the Forward. Pierson is currently working with us to integrate the power of HPSS in his security courses. (Very cool!) Hoff is a forward thinking security professional who is respected among his peers. The book immediately confronts the security issue with VMware. Chapter 2 presents the “anatomy of an attack.” Attack perspectives are from a Pentester, a hacker, a script kiddie, and a disgruntled employee.

Chapters 6, 7, and 8 focus on deployment, management, operations and virtual machine security. Some common operational issues are discussed to protect and audit your environment. Chapter 9 is especially useful, posing real-world questions discussed on the VMware VMTN Communities forums. The latter part of the book features a patch for Linux, a security hardening script, and an assessment script output. A reading list and links are included in the final section. A great addition to your IT library from Amazon for $40.56.

Your Next Security Threat May Not Involve Attackers

I was astounded when I read this article that includes a 2 BILLION estimate on the number of H1N1 cases that the WHO is expecting. Even worse, at 30% of human population on the planet, many are calling that number conservative. Some members of the medical community say that 45-50% may be likely!

In either case, the good news is that SOME vaccine is likely to be available to those in the Northern Hemisphere before Autumn arrives. The bad news is that there will likely not be an abundance of it, and that means some will not have access.

This is where the DR/BC planning comes in. By now, you probably have heard a little bit about pandemic planning and hopefully have created processes for remote working, containing illness and ensuring that you can operate with reduced staff. If you haven’t done this yet, NOW IS THE TIME to get this started.

If you do already have a plan, now might be a good time to do some rudimentary testing. Maybe declare a couple of reduced staff days, test the load on the VPN and remote access servers and such. This testing effort will likely reveal a few holes in these plans, but it is much better to learn about them and mitigate them now than when the real thing is going on.

Clearly, from the evidence presented by the WHO, this is something we should be paying attention to. Those who lack the focus or resources to take it seriously may well find themselves in troubling times when the weather turns colder and folks in the office begin to sneeze….

Book About PERL for Problem Solving

One of the essential tech skills I am always on the prowl for is a way to use technology to solve a complicated problem. Of course, one of the most useful ways to do this is to learn and apply simple programming skills. PERL is one of those scripting languages that is easy to get on a basic level, but it offers so much additional capability and complexity that it would take a literal lifetime to truly “master”.

But, the wonderful thing about PERL is its amazing capability in simplicity. You can take a few basic PERL legos and really make some wonderful things to increase the ease of your life and work. This book, <a href=”http://www.secguru.com/books/wicked_cool_perl_scripts_useful_perl_scripts_solve_difficult_problems” target=”_blank”>Wicked Cool Perl Scripts</a>, is chocked full of examples of just how to apply some basic PERL to real world problems. Check it out if you are a fan of PERL and want to automate things from work, to your news and RSS feeds to your World of Warcraft gaming. PERL is not only easy and cool, but also fun!

Egress Filtering 101

Egress filtering is one of the most often underestimated defenses today. We continue to see organizations that have not yet deployed strong egress filtering, which is one of the most effective controls in defending against and detecting bot-nets. Without it, outbound connections are usually a mystery to the security team and identification and interception of malware outbound command and control channels are unlikely.

To add fuel to the fire, egress filtering is cheap (you probably already have a firewall or router that can do it) and easily managed once configured. Sure, establishing the political will to see it through it can be tough, but given the threat levels and attacker techniques in play today, it is a highly critical effort. You start by examining what outbound ports you allow today, then close all ports outbound and allow only the ones that have a true business case. Once you have choked down the traffic, consider implementing application proxies where possible to further strengthen the egress traffic and rules.

Once you have appropriate proxies in place, don’t allow any outbound web traffic or the like from any host but the proxies. No outbound DNS, chat protocols or the like from the desktop world to the Internet. The more you choke this down, the easier it is to protect the desktop world from simple issues.

Egress filtering is just too easy to ignore. The level of protection and the capability to monitor outbound attempts to break the rules once in place are powerful tools in identifying compromised internal hosts. Best practices today truly includes this requirement and those interested in truly securing information should embrace egress filtering as soon as possible.

If you want help with such a project or want to learn more about scoping egress filtering in your network, let us know. We would be happy to help you!

HoneyPoint Appliance and Virtual Appliance Growing

I was so pleased with the news from my team yesterday that we are just about ready for the formal release of the HoneyPoint physical appliance. We are putting the final polish on the devices and they will be ready for release by the end of next week.

The virtual appliance is now going into its 2.0 architecture. The appliance has been rebuilt from scratch, hardened and reconfigured. It is also ready for shipment.

Special thanks to Adam for his work on completing these “decoy hosts” for folks that don’t want to put HoneyPoints on their production servers. His work is pushing HoneyPoint to the next stage of evolution and is much appreciated!

You can get both the virtual appliance and the physical appliance as a part of HoneyPoint Security Server and through the Managed HoneyPoint service as well. Drop us a line or give us a call to learn more about either of these programs!

New HITECH Law Expands HIPAA Requirements

j0321057

A new law was enacted on February 17th of this year that expands the HIPAA privacy rule to include “business associates” of health care providers. This law also sets a new requirement for notifying individuals in the event that their private health information (PHI) has been compromised and gives State Attorneys General new powers to prosecute persons or organizations that fail to comply with HIPAA privacy and security requirements. This law is called the Health Information Technology for Economic and Clinical Health Act (HITECH), and is a part of the new American Recovery and Reinvestment Act of 2009.

What this means is that a number of different organizations that process or use PHI on behalf of a HIPAA “covered entity” must now also comply with the HIPAA security rule just as the covered entity is required to. This includes the need to develop or alter policy and procedural documents, conduct risk assessments and gap analyses, apply appropriate encryption and secure transmission methods to PHI and more. And the security breach notification rule comes into effect just one month from today on August 16th!

Now, this gets a little complicated, so first let’s look at what “covered entity” and “business associate” means in terms of HIPAA and HITECH. A “covered entity” is basically defined as:

  • A health care provider that conducts certain transactions in electronic form
  • A health care clearinghouse
  • A health care plan

A “business associate” is basically defined as a third party that performs or assists in the performance of: A function or activity involving the use or disclosure of individually identifiable PHI, including claims processing or administration, data analysis, processing or administration, utilization review, quality assurance, billing, benefit management, practice management and repricing and more.

A third party person or organization that provides legal, actuarial, accounting, consulting, data aggregation, management, administrative, accreditation or financial services for a covered entity or wherever the provision of services involves disclosure of individually identifiable PHI to a business associate.

In other words if you process or have access to PHI from a covered entity, then you can be pretty sure that this law applies to you! So what do you need to do if you find that this new law does indeed apply to you or your organization? Well, the best thing you can do is encrypt all of your PHI data for both transmission and storage. This has to be done according to Department of Health and Human Services requirements which in turn means that it has to be done according to standards found in NIST 800-111 and FIPS 140-2 (Also see 45 CFR Parts 160 & 164). If you do meet these standards, you have suitably rendered PHI information “Unusable, Unreadable or Indecipherable to Unauthorized Individuals” and therefore do not need to develop the elaborate information security breach notification measures that are specified in the new law.

And not having to deal with breach notification is something most people and organizations should definitely want to avoid! Not only does it just make good sense to properly encrypt and protect private information from a best practices standpoint, a breach could do you or your organization real harm. For example, under the new law if you have a security breach that reveals the PHI of 500 individuals or more, there is a MANDATORY requirement to notify the news media! What affect would THAT have on your reputation and bottom line!? And remember, even if you do suitably protect PHI in motion, at rest, while in use and when being disposed of, you need to have a suitable written information security program in place that details the administrative, physical and technical security measures you will use to protect PHI. And these measures must be strong enough to meet HIPAA Security Rule requirements. If your organization does not meet the specified data encryption standards, then you also need to develop written policies and procedures around the new Security Breach Notification Requirements found in HITECH.

In a nutshell, here are some of the steps you or your organization should be taking to ensure compliance with HITECH:

  • Find out if you or your organization is a covered entity or business associate under the new law
  • Perform risk assessments and/or gap analyses as needed to see if you meet HIPAA Security Rule and HITECH standards or not. (If not, you will need to develop a roadmap detailing what you will do to meet these standards in the future)
  • Update or develop your information security, privacy and HIPAA policies and procedures as needed to meet the HIPAA Security Rule
  • Update any relevant Notice of Privacy Practices documents you have in order to meet the new standards
  • Develop or update your Breach Notification Policies and Procedures to comply with HITECH and any State counterpart law
  • Update and/or expand your business associate agreements to include the new security and notification requirements

Remember, if your organization willfully or through ignorance or inattention does not meet these new requirements, the penalties have been strengthened against you. Civil monetary penalties have been increased and for the first time, this law authorizes State Attorneys General to begin pursuing civil actions for HIPAA privacy and security violations that have threatened or adversely affected residents of their respective States. Also, starting early next year, entities using electronic health records will be required to track any disclosures of patients’ medical information, including disclosures made for treatment and payment.

So, don’t get caught short by HITECH! Consider implementing proper encryption and information protection measures now. Strengthen and update all of your information security policies and procedures. The need to do so will only increase in the future anyway. And if you need help developing policies and procedures or performing risk assessment and gap analyses, MicroSolved has the experience and expertise needed to get the job done. Give us a call!

Get Ready, Here Comes the MS Web Office Bot-Nets!

Just as we expected, the exploit for the Web Office 0-day has been integrated into existing bot-net spread attacks. SANS and other folks began reporting that SQL injection compromises have now been tuned to include defacements with the embedded Web Office exploit.

These SQL injection attacks that lead to defacement, along with the recent spate of Cold Fusion defacements have been leveraged to spread malware for some time. However, this new “upgrade” to the malicious javascript the defacements leverage to infect browsers is likely to be much more effective with the Web Office exploit in place, given that no real patch is available and that the exploit code is so easy to use, stable and effective.

If you have not yet deployed the kill bit solution referenced in this article: https://stateofsecurity.com/?p=709, you should do so immediately. Mass, wide-scale, exploitation of this issue is likely beginning and will continue for some time.

It would also be very wise to educate your staff about this issue since they will need to activate the kill bits on home systems as well until a patch becomes available.

Please note that you must reboot systems before they become immune to the exploit once the kill bits are installed in the registry.

Let us know if you have any questions or desire any assistance with the kill bit solution.

Risk Assessment and Mitigation for the MS Web Office Issue

Here is a PDF of the risk assessment and review of this emerging vulnerability. Please check it out if you are working on mitigating this issue.

While the corporate risk is identified as an overall medium, there is a high risk of workstation infection from this problem.

Check out the document here.

Vuln RA 071409 – MS Web Office 0-day

If you would like to follow the emerging threat, the SANS Internet Storm Center is the best place to get current news about the outbreaks and exploitation. You can also follow me (@lbhuston) on Twitter for more information as it comes in.

UPDATES:

7/14 – 2:17pm Eastern –

SANS has gone back to green status and is posting that they hope awareness has been raised.

Nick Brown wrote in to tell us that the exploit in MetaSploit is easy to use and very effective against most XP workstations. He also warns home users to be on the lookout as this is very likely to turn into a worm or automated bot-net attack very soon. He agreed that the MetaSploit exploit is unlikely to affect servers as we expressed in our assessment. Lastly, he wanted us to remind everyone that using the kill bits, REQUIRES A REBOOT OF THE SYSTEM BEFORE IT IS IMMUNE.

Adam Hostetler also found this site, which has some interesting ways of identifying vulnerable hosts: http://blogs.technet.com/srd/archive/2009/07/13/more-information-about-the-office-web-components-activex-vulnerability.aspx

We have scheduled a FLASH Campfire chat for a threat update and discussion at 4pm Eastern today. The URL for that chat is: https://microsolved.campfirenow.com/ccf03

Thanks for reading and for all of the excellent feedback!

Update2: Here is the transcript from the public chat. Thanks to all who attended. Hopefully, it will be helpful for folks who are working on the issue.

Transcript