STE WILLIAMS

NSA: No we weren’t hacked, we just broke our website

The official NSA website NSA.gov was offline for several hours on Friday, prompting immediate wild speculation that it had been taken down by a DDoS campaign.

But the NSA itself eventually squashed the rumours, announcing officially that the issue was “an internal error that occurred during a scheduled update”.

The site was apparently down for up to six hours on Friday afternoon and evening, indicating either a pretty serious error or some rather sluggish efforts at restoring normality.

The NSA has been increasingly beleaguered of late, with the ever-mushrooming Snowden leaks heaping embarrassment upon embarrassment.

With growing public distrust and distaste for the agency, it was inevitable that many would assume the outage was down to some sort of revenge attack by the internet community.

The incident also coincided nicely with a major rally in Washington D.C. over the weekend to protest against the NSA’s snooping activities.

But of course, as the satirical science and technology cartoon XKCD pointed out in 2012, a public-facing website may be an easy target, but it’s not really a particularly vital asset to a top-secret government agency.

It’s unlikely that any of the NSA’s spies were uploading deviously-obtained data to the site and ended up blocked from reporting Angela Merkel’s latest text messages back to base.

On the other hand, the accidental outage seems to run counter to recent impressions that the NSA is overloaded with super-elite computer geniuses who can do just about anything, including breaking the most advanced cryptography.

At least, if those people are there, they’re not working on the public website.

It also serves as a reminder that while updates are of course important, they should always be properly tested before being implemented in live environments, and proper known-working backups should always be available to fall back on in case of disaster.


Article source: http://feedproxy.google.com/~r/nakedsecurity/~3/9lXJV0dCFk0/

NSA: No we weren’t hacked, we just broke our website

The official NSA website NSA.gov was offline for several hours on Friday, prompting immediate wild speculation that it had been taken down by a DDoS campaign.

But the NSA itself eventually squashed the rumours, announcing officially that the issue was “an internal error that occurred during a scheduled update”.

The site was apparently down for up to six hours on Friday afternoon and evening, indicating either a pretty serious error or some rather sluggish efforts at restoring normality.

The NSA has been increasingly beleaguered of late, with the ever-mushrooming Snowden leaks heaping embarrassment upon embarrassment.

With growing public distrust and distaste for the agency, it was inevitable that many would assume the outage was down to some sort of revenge attack by the internet community.

The incident also coincided nicely with a major rally in Washington D.C. over the weekend to protest against the NSA’s snooping activities.

But of course, as the satirical science and technology cartoon XKCD pointed out in 2012, a public-facing website may be an easy target, but it’s not really a particularly vital asset to a top-secret government agency.

It’s unlikely that any of the NSA’s spies were uploading deviously-obtained data to the site and ended up blocked from reporting Angela Merkel’s latest text messages back to base.

On the other hand, the accidental outage seems to run counter to recent impressions that the NSA is overloaded with super-elite computer geniuses who can do just about anything, including breaking the most advanced cryptography.

At least, if those people are there, they’re not working on the public website.

It also serves as a reminder that while updates are of course important, they should always be properly tested before being implemented in live environments, and proper known-working backups should always be available to fall back on in case of disaster.


Article source: http://feedproxy.google.com/~r/nakedsecurity/~3/9lXJV0dCFk0/

NSA.gov goes down after ‘error during scheduled update’

Supercharge your infrastructure

The USA’s National Security Agency (NSA), lately the source of near-endless controversy for spying on just about the entire internet, has itself hit trouble online after its website went down.

The agency has ‘fessed up to some website wobbles last Friday, but has issued a statement to all and sundry that says “an internal error that occurred during a scheduled update” was the source of the outage. The statement went on to say “The issue will be resolved this evening. Claims that the outage was caused by a distributed denial of service attack are not true.”


The last statement looks correct: online agitators aren’t claiming to have taken down the agency’s site and are instead making light of the situation with Tweets such as the one below.

As The Reg researched this story, the site was down again for a period of about half an hour. We’ve no way of knowing if that outage is related to Friday’s outage. But we’re sure the NSA will read this story and try to figure out just what went wrong.®

ioControl – hybrid storage performance leadership

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2013/10/28/nsagov_goes_down_after_error_during_scheduled_update/

IBM Storwize arrays at risk of complete deletion

Supercharge your infrastructure

IBM has issued a warning to owners of its Storwize arrays, SAN Volume Controller and Flex System V7000, because all are at risk of having their contents erased.

Big Blue’s warning about the problem is blunt: “Administrative access to the system via the IP interface may be obtained without authentication.”


That’s bad news because “The vulnerabilities can be exploited by a user with access to the system’s management IP interface using vulnerabilities in the Apache Struts component. If successful, the user can gain access with superuser privilege which will allow any modification to the configuration, including complete deletion.”

The fix sounds simple: upgrade Storwize appliances to version 7.1.0.5 of their operating system. We’ve qualified that statement with “sounds” because version 7.1.0.5 was released at the beginning of October. Plenty of storage administrators may have had good reason not to make the upgrade.

One piece of silver lining: IBM notes that the web interface is likely not exposed to the internet. That means an insider is the most likely threat, yet another reason for storage admins to keep those pesky network admins away from their beloved boxen. ®

5 ways to reduce advertising network latency

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2013/10/28/ibm_storwize_arrays_at_risk_of_complete_deletion/

Breach At PHP.net Causes Site To Serve Malware

PHP.net, one of the Web’s most popular application development sites, was breached last week, causing it to serve malware to a number of its users.

In a series of blogs issued Thursday, the operators of PHP.net disclosed that two of the site’s servers had been compromised. The operators say they still don’t know how the breach happened.

The blogs were posted shortly after researchers at Barracuda Labs, Google, AlienVault, and Websense reported JavaScript malware emanating from PHP.net Web servers. PHP.net says that the malware was served “to a small percentage of PHP.net users” from Oct. 22 to Oct. 24.

“All affected services have been migrated off those servers,” PHP.net says in its latest blog. “We have verified that our Git repository was not compromised, and it remains in read only mode as services are brought back up in full.

“As it’s possible that the attackers may have accessed the private key of the php.net SSL certificate, we have revoked it immediately,” the blog says. The site has gotten a new certificate and has restored access to PHP.net sites that require SSL.

All PHP.net users will have their passwords reset in the next few days, the blog says. Users of PHP software “are unaffected by this: this is solely for people committing code to projects hosted on svn.php.net or git.php.net,” the organization states.

Have a comment on this story? Please click “Add a Comment” below. If you’d like to contact Dark Reading’s editors directly, send us a message.

Article source: http://www.darkreading.com/applications/breach-at-phpnet-causes-site-to-serve-ma/240163167

Breach at PHP.net Causes Site To Serve Malware

PHP.net, one of the Web’s most popular application development sites, was breached last week, causing it to serve malware to a number of its users.

In a series of blogs issued Thursday, the operators of PHP.net disclosed that two of the sites servers had been compromised. The operators say they still don’t know how the breach happened.

The blogs were posted shortly after researchers at Barracuda Labs, Google, AlienVault, and Websense reported JavaScript malware emanating from PHP.net Web servers. PHP.net says that the malware was server “to a small percentage of PHP.net users” from Oct. 22 to Oct. 24.

“All affected services have been migrated off those servers,” PHP.net says in its latest blog. “We have verified that our Git repository was not compromised, and it remains in read only mode as services are brought back up in full.

“As it’s possible that the attackers may have accessed the private key of the php.net SSL certificate, we have revoked it immediately,” the blog says. The site has gotten a new certificate and has restored access to PHP.net sites that require SSL.

All PHP.net users will have their passwords reset in the next few days, the blog says. Users of PHP software “are unaffected by this: this is solely for people committing code to projects hosted on svn.php.net or git.php.net,” the organization states.

Have a comment on this story? Please click “Add a Comment” below. If you’d like to contact Dark Reading’s editors directly, send us a message.

Article source: http://www.darkreading.com/applications/breach-at-phpnet-causes-site-to-serve-ma/240163167

Tech Insight: Enterprise Security’s Overlooked Factor — The End User’s Age

[Todd Fitzgerald is the global director of information security for Grant Thornton International, Ltd. His content is contributed through the auspices of the (ISC)2 Executive Writers Bureau.]

When it comes to security policy, most enterprises treat all users the same way. But perhaps this is a mistake. When you take a closer look at the age of your end users — their “generational identities” — you may find that users of different generations have very different attitudes and practices with regard to online privacy and security.

Currently, there are four clear-cut generations of end users in the workforce: Traditionalists, Baby Boomers, Generation X, and Gen Y, sometimes called Millennials. A fifth generation — let’s call them Gen Z for now — is about to enter. Let’s look at the profile of each generation of users, and discuss how the history and background of each generation might shape its attitude towared online security. Interestingly, studies have shown that the events that were occurring during the teen years of each generation have the most influence on its attitudes and expectations.

Traditionalists (born 1925-1945) are shaped in part by the early days of the cold war, the growth of the suburbs, and rapid economic growth following WW II. This generation generally respects authority, having worked to build many of the hierarchical organization structures today. This is a hard-working generation that tends to obey the rules and behave in a way that is more reserved and cautious.

Baby Boomers (born 1946-1964) experienced the assassinations of major political figures, an unpopular Vietnam War televised nightly, and major movements such as civil rights and women’s liberation. It is a generation defined by change. Many Boomers are competitive and define themselves by their work. Other generations may view them as workaholics without work/life balance.

Generation X (born 1965-1979) grew up with a rising divorce rate, more women entering the workforce, more blended families, and greater autonomy at home. As teenagers, Gen X also witnessed they layoffs of Boomers and Traditionalists due to economic shifts and changes in business practices. As a result, this generation tends to be more skeptical and distrustful about organizations and more focused on independent thinking and skills. Gen X tends to be more adaptable, flexible, and resilient.

Generation Y (born 1980-2000) spent its impressionable teenage years watching terrorism such as the World Trade Center bombing, 9/11, and the Oklahoma City bombing. Many Gen Y members were raised in a pro-child culture that favored “self esteem” and rewarded all children equally. Raised primarily by Boomer parents, many members of Gen Y have been taught that they could do anything they set their minds to and to question authority. Perhaps the largest generation currently in the workforce, Gen Y is also the first generation to grow up on technology, including instant messaging, texting, smartphones, and social media. Gen Y tends to be technically savvy, collaborative, multi-tasking, and always connected. Gen Y also tends to be confident, optimistic, and may often take risks to get a job done.

Generation Z (born 2001-2013) isn’t in the workforce yet, but its attitudes are being shaped as we speak. Time will tell if the impact of political gridlock, difficult recessionary times, and ubiquitous technology will create an entirely new generation of attitudes toward information security.

In our organizations today, we have a tendency to use a one-size-fits-all approach toward security, but the attitudes of the users who must comply with those policies may be very different. What may seem to be a logical security policy for one generation may be met with resistance by another, depending upon its unique world view. Your policies and strategies toward enforcing security may have to be tweaked to address these differences. Here are some examples:

1. Information Security Policy. Where Traditionalists generally respect authority, Boomers tend to challenge directives unless they are logical. Gen Xer’s and Millennials will question the authority of the security policy, particularly if that policy makes it harder for them to do their jobs.

2. Security Awareness Training. Traditionalists tend to learn by rote memorization and extensive study. Boomers learn by classroom lectures, books, and PowerPoints. Gen X learns best through play/games, role playing, e-learning and videos; Millennials learn through social media, blogs, podcasts, video, mobile technology, and collaboration with others. A dry, 45-minute PowerPoint presentation describing the enterprise’s security policy may satisfy a compliance auditor, but it may not actually teach some of your users to comply.

3. Logon IDs and Passwords. With almost as many smartphones as people on the planet, the idea of using such a device for two-factor, near-field authentication may now become a valid alternative to the password. Which generation will drive this integration? Most likely the Millennials, who have a greater needfor flexibility and to save time for other activities.

4. Secure File Transfer/Sharing. – Boomers are more likely to stay at the office and work on their deliverables or use the company-issued laptop at home. Gen X is adaptable and resilient, and would not hesitate to transfer files to a USB drive or cloud storage solution and then to the home computer. Millennials may transfer work files to the latest technology they just purchased — or access that data via their smartphone or tablet at 3 a.m.

5. Social Media. Traditionalists and Boomers are the predominant users of LinkedIn — they are proud of their histories and have a tendency to reveal more than they should. Gen X and Gen Y users tend to use Facebook, and Gen Y tends to post frequent updates, illustrating a significantly lower regard for privacy. Collaborative Millennials may inadvertently share company information while asking a friend about a project.

6. Bring Your Own Device (BYOD). All generations appear to want the flexibility of having the newest equipment and carrying one phone, but the millennials are the primary driver behind this trend. Millennials come from a consumer-driven economy and believe that the employer should provide these devices for them — or they will bring their own. For Gen Y, there is a “cool factor” behind having the latest devices and the most current applications.

7. Cloud Applications. Boomers are adapting to cloud models as a way to reduce costs. Gen X may worrythat moving all applications to the cloud will also move the work offshore. Millennials appreciate theflexibility of being able to access their work from anywhere via the cloud. Millennials are likely to “just try it” and put data in the cloud, even if there is no policy. Boomers often want some assurance as to where the data is and whether it be recovered if lost.

8. Security As a Career. Millennials who are working in information security today may not stay there indefinitely. Millennials embrace multiple career paths and may hold more than one job at the same time. To retain these individuals, enterprises must provide a work environment that is challenging, provides meaning and frequent feedback, and is socially responsible.

With each generation, the technology opportunities increase and new uses are created. This article outlines some tendencies, but we must be careful not to pigeonhole or stereotype users based upon the generation to which they were born. A Boomer might be quite technically savvy and behave like a Gen Xer in the field. A Millennial may adopt the values of a Boomer and use the Web primarily to “Google” information, rather than for socializing with others.

It’s worth considering whether your security policies, training programs, and other security initiatives are well-tuned for the users they are intended for. Consider generational and attitude factors when developing your programs, and do the best you can to match your priorities and capabilities with those who are most likely to use them.

Have a comment on this story? Please click “Add a Comment” below. If you’d like to contact Dark Reading’s editors directly, send us a message.

Article source: http://www.darkreading.com/privacy/tech-insight-enterprise-securitys-overlo/240163181

Is that a GUN, or are you just upgrading the printer? – 60 Sec Security [VIDEO]

Is that a GUN, or are you just upgrading the printer?

WordPress 3.7 with automatic security updating is out now

Wordpress 3.7Automattic have announced the release of WordPress 3.7 “Basie” so if you have a website that runs on WordPress it’s time to upgrade.

We don’t always trumpet software releases on Naked Security but I think WordPress 3.7 is very important.

It’s not important because it fixes any particularly devilish vulnerabilities but because, for the first time, it will automatically update itself with the latest maintenance and security releases – something that could change the security of the whole WordPress ecosystem.

The signature feature of this latest version of the hugely popular blogging platform is automatic background security updates.

Next time WordPress.org issues an urgent security point release – such as the recent version 3.6.1 which came with the exhortation to update your sites immediately – it will be deployed automatically to site owners using 3.7 or above.

We’ve all become quite used to the idea of the software on our desktops, tablets, laptops and smartphones silently patching itself in the background and it’s good to see popular web software catching up – it’s long overdue.

What makes background updates for WordPress such a significant step is the software’s sheer popularity. Nobody is quite sure how many of the world’s websites are running on WordPress but the consensus seems to be that it’s about 15 – 20%.

Needless to say that’s a very, very, very large number of websites – so large that criminals looking to build botnets are prepared to invest in large-scale automated attacks that scan for and target known WordPress vulnerabilities.

The best defence against such attacks and the first rule of WordPress security is always run the latest version of WordPress.

As Andrew Nacin put it on the Make WordPress Core blog:

If you don’t keep your site up to date, you are making the web a less safe place for you and everyone who visits your website.

The trouble is that it seems a lot of people don’t bother. Some researchers believe that as many as 73% of the WordPress sites out there are vulnerable to attack purely because they aren’t running the latest version.

So automatic updates for WordPress could do more than simply ensure fewer websites are vulnerable to attacks, it could ultimately provide a kind of ‘herd immunity’ that will make the entire population a less attractive target.

The automatic updater also supports themes and plugins – the software skins and add-ons that allow users to customise their WordPress websites. Some plugins are so widely used that they are popular enough to be targetted in their own right.

Although auto update support for themes and plugins is on an opt-in basis for now I fully expect that to change in future, and to quote Nacin one more time, “That’s a huge win for a safer web”.

The software is available to download from WordPress.org. If you want to know more about what’s in 3.7 take a look at the release announcement on the WordPress blog. There is also a very long and detailed post about disabling automatic updates on the Make WordPress Core blog.

If you’d like to know a more about WordPress security then take a minute or two to read our article on How to avoid being one of the “73%” of WordPress sites vulnerable to attack.


Article source: http://feedproxy.google.com/~r/nakedsecurity/~3/BQweWT38P-c/