Discover PerformanceHP Software's community for IT leaders // July 2012
Speed and security? Just add automation
Secure software without sacrificing the gains of agile development. Follow DevOps’ drive toward automation.Start automating
6 steps to prevent app attacks
Exploiting weakness at the app layer is the new black for black hats. Find out how to keep your risk low.Stay a step ahead
Cooking with DevOps
Author, entrepreneur and DevOps guru Gene Kim explains the key ingredients of the movement and how it can help an enterprise move “from good to great.”Get cooking
New threats, old defenses?
HP Enterprise Security’s Jay Huff talks about the changing face of cyber crime—and the ways enterprises are failing to adapt.Watch now
Most read articles
Preparing today for tomorrow’s threats.
Introduction to Enterprise 20/20
What will a successful enterprise look like in the future?
Challenges and opportunities for the CIO of the future.
Dev Center 20/20
How will we organize development centers for the apps that will power our enterprises?
Welcome to a new reality of split-second decisions and marketing by the numbers.
IT Operations 20/20
How can you achieve the data center of the future?
What the workforce of 2020 can expect from IT, and what IT can expect from the workforce.
Looking toward the era when everyone — and everything — is connected.
Data Center 20/20
The innovation and revenue engine of the enterprise.
Join thousands of IT execs, engineers, and solution experts to explore IT trends, strategies, and best practices. (Barcelona,
HP Software’s Paul Muller hosts a weekly video digging into the hottest IT issues. Check out the latest episodes.
Percentage of attacks against enterprise IT in 2011 that were not web-based.1
Percentage of companies who cited concerns about defects in the vendor's technology as a chief cloud concern (the most-frequently cited fear).2
Percentage of survey respondents that admitted to not being PCI-compliant, even though the survey data suggested that they should be.3
Q: Does DevOps need a distinct security “flavor”?
A: I've seen “SecDevOps” discussed, “Rugged DevOps” and on and on ... The only reason to explicitly call out whether we're adding security function into a movement like DevOps is if there are use-cases where security is absent. I can't think of one such case, so why would we want to have a “SecDevOps” vs. “DevOps,” where one implies the absence of security principles? … It perpetuates the notion that security principles are something that is apart from the development and deployment cycles—that security is an add-on. — Rafal Los, chief security evangelist, HP Software, on the Following the Wh1t3 Rabbit blog