Looking for the most highly available, most mission critical way to run your current and future SAP applications? Tired of planned and unplanned outages, and the increasing costs and risks when your SAP applications are down? SAP and IBM have you covered with the new “SAP Zero Downtime Option.” SAP’s new reference architectures illustrate the world’s most continuous, most secure SAP services.
Make that a few mainframes for Yahoo! At least 500 million accounts were breached. In terms of number of accounts, Yahoo! has likely set a record for the biggest data breach of all time. (So far.)
If that’s not bad enough, it gets worse: Yahoo! reportedly did not tell its suitor, Verizon, about the data breach until at least two months after Yahoo!’s management found out — and only two days ago. In July Verizon agreed to acquire Yahoo! for $4.83 billion. Verizon might be able to pull out of the deal if it wishes.
Mainframes are widely recognized in the IT industry as the most securable platform. My “(Blank) Needs a Mainframe” series of periodic posts is a reminder that the IT community continues to fail at security, and that mainframes should form part of a holistic answer to fix this massive, growing, industry-wide failure.
This series of posts also reminds the mainframe community to be more vigilant than ever, not to assume that your mainframe environment is invulnerable. I recommend “healthy paranoia.” Every IBM mainframe ships with incredible security capabilities, many enabled by default, and more are optionally available. However, IT teams must know what they’re doing, must stay abreast of developments and technologies, and must competently operate their systems based on the latest information. And here’s a special reminder to CEOs, CFOs, and Chief Risk Officers: if you’re not caring for and investing in your workforce, you are significantly raising the risk of being the next victim of a security breach. “You get what you pay for,” including IT talent (or lack thereof).
Please be careful out there.
Jeff Hall argues the case for airlines to make their mainframes bigger (and the rest of their IT smaller).
I’d quibble with a couple of the finer technical points Hall made, but it’s an interesting, provocative take. I wonder how much “inside” information he has.
Paul Vallely, in one of the comments to Hall’s post, reports that, from his perspective as a distressed passenger, the only major piece of IT that was working at Delta during their outage was…their mainframe. Amidst the meltdown, Delta’s customer service agents, reachable by telephone (albeit with long waits on hold at times), had access to Delta’s mainframe-hosted applications and could handle most passenger issues (rebookings, refunds, etc.) “Based on what I saw and heard, it seems the mainframe was not the cause of the problem but it was actually a savior during the crisis,” Vallely wrote.