For the second time this year, Java has been in the headlines for the wrong reasons. In late August, security researchers spotted attackers exploiting a brand-new flaw in Java 7 through booby-trapped websites. Visiting one of those pages with Java turned on was enough to get a computer infected. At the time, there was no fix. Oracle, which makes Java, released an emergency update on August 30, earlier than its normal schedule.
That is the definition of a "zero-day": a flaw attackers are using before the maker has a patch. And it has pushed a lot of security experts and incident response teams toward some blunt advice: unless you truly need Java in your web browser, disable it. For a small office, that raises a practical question. How do you know whether you need it, and how do you manage it across a dozen computers?
Why Java keeps showing up in these stories
Java is two things that people often confuse. It is a programming language used to build all kinds of software, much of which has nothing to do with the web. It is also a browser plug-in that lets small programs called applets run inside a web page. That plug-in is the problem.
Because the Java plug-in is installed on an enormous number of computers, often without the owner knowing why, it is an attractive target. Criminals package attacks against it into ready-made "exploit kits" that get planted on hacked websites. You do not have to download anything or click anything suspicious; the web page does the work. You may remember the Flashback infections on Macs this spring, which spread the same way; see our post on the Flashback Mac malware.
Does your office actually need Java?
For most people, the honest answer is no. A few years ago plenty of websites used Java applets. Today, far fewer do. But some business tools still depend on it, and those are the ones to find before you flip any switches. Common examples include:
- Some online banking and payroll portals, particularly for business accounts.
- Certain government and court filing websites.
- Older web-based line-of-business applications, including some industry-specific software.
- Management screens for some network equipment, phone systems, and security cameras.
- Some web conferencing and remote support tools.
A good test is simple: disable Java on one or two computers for a week and see if anyone notices. If nobody does, you have your answer.
If you do not know why Java is on a computer, it probably does not need to be in the browser.
Your options, from simplest to most flexible
Uninstall it completely
If nothing on a computer uses Java, remove it through the Control Panel. No Java, no Java vulnerabilities. This is the cleanest option.
Keep Java, but disable the browser plug-in
Some desktop programs need Java installed but never use the browser plug-in. In that case, you can leave Java on the machine and turn off just the plug-in: through Manage Add-ons in Internet Explorer, the Plugins list in Firefox, or the plug-ins settings page in Chrome. Chrome also has a "click to play" option so plug-ins only run when you allow them.
Use one browser for Java, another for everything else
If a staff member needs a Java-based banking site, one workable approach is to enable Java in a single browser used only for that site, and do all other browsing in a second browser with Java off. It takes a little discipline, but it greatly reduces exposure.
If you must keep it, keep it current
Any computer that keeps Java enabled needs to be on the latest version, promptly, every time. Java's own updater is easy to ignore, and old versions often stick around after new ones are installed. Uninstall the old versions.
Managing it across an office
Doing this on one PC is easy. Doing it on fifteen, and keeping it that way, is where small offices struggle. Settings drift, a new employee installs something that brings Java back, or an update quietly re-enables the plug-in.
This is where central management pays off. With the right tools, an IT team can see which computers have Java installed and which version, push updates to all of them at once, and apply browser settings across the office rather than one desk at a time. In a Windows domain, Group Policy can control a good deal of this for Internet Explorer. That kind of ongoing watchfulness is exactly what our managed IT services are built to handle, so a warning like this one becomes a scheduled task instead of a scramble.
What to do now
- Take inventory. Which computers have Java, and which version?
- Ask staff which websites and programs they rely on and check whether any of them need Java.
- Uninstall Java from computers that do not need it.
- Disable the browser plug-in on computers that need Java only for desktop software.
- Update Java immediately on any computer that still uses it in the browser, and remove older versions.
- Keep Windows, browsers, Flash, and Adobe Reader updated too; they are targeted in the same way.
The bottom line
Java in the browser has become one of the most common ways computers get infected, and new flaws keep turning up. Turning it off where it is not needed is one of the easiest security improvements a small office can make this month. If you would like help sorting out which of your computers need Java and locking down the rest, email us at info@pinellasit.com.
