Oracle: Automated security would have prevented Equifax breach
Larry Ellison reveals self-patching database, as Oracle steps into machine learning
Oracle founder Larry Ellison claimed yesterday that Equifax's huge data breach would never have happened had the company used Oracle's upcoming self-patching database.
Equifax's CEO, CIO and CSO all retired in the aftermath of the incident, which exposed 143 million US customers' data records, and the details of 400,000 UK customers, to hackers, though the company only revealed the July hack last month.
It emerged that Equifax had been hacked through an unpatched Apache Struts flaw, which the Apache Foundation had released a fix for back in March - Equifax had simply failed to apply it.
"The worst data thefts in history have occurred after a patch was available to prevent a theft," Ellison told approximately 60,000 delegates at Oracle OpenWorld in San Francisco.
"The database system has to be able to immediately patch itself, automatically patch itself, not wait for a human being to schedule downtime where there's an opportunity to implement a patch in a month or two - by the way which normally happens."
He suggested the Equifax breach was a result of unwillingness to bring the system offline to patch it efficiently.
"To apply a patch typically you have to bring your systems down - nobody likes to bring their systems down," Ellison said. "There's a lot of approvals up and down that need to occur. That doesn't work. Didn't work at Equifax, didn't work at the [US] Office of Personnel Management - doesn't work."
While Oracle is still "moving to" a fully autonomous security system - which Ellison promised more details on come Tuesday - he did show off a fully automated database, Oracle 18c, coming in December, which he said includes the ability to automatically patch flaws.
On Oracle's security system, he explained it relies on machine learning to identify anomalies in patterns of behaviour, to allow companies to spot potential malicious behaviour before they are impacted.
"You have to know in the [hacker's] reconnaissance phase when someone's nosing around in your computer systems trying to steal a password, trying to steal an identity," he said. "You better detect that happening during the reconnaissance phase.
"After your database's been notified by your security system it has to be able to patch itself immediately while running," he explained. "No delay, no human intervention, it has to happen immediately."
The cost of getting it wrong is too high to pay, Ellison argued, not to consider the advantages of automated security.
"How many cents did it costs Equifax to not do an online patch? What if a human being just misses a patch, what's the cost of that?" he asked.
"There was a patch available for Equifax [but] somebody didn't apply it. It's a clean sweep; directors aren't safe, nobody's safe when something like that happens. People are going to get better at stealing data and we have to get a lot better at protecting it."
Picture: Larry Ellison
Unlocking collaboration: Making software work better together
How to improve collaboration and agility with the right techDownload now
Four steps to field service excellence
How to thrive in the experience economyDownload now
Six things a developer should know about Postgres
Why enterprises are choosing PostgreSQLDownload now
The path to CX excellence for B2B services
The four stages to thrive in the experience economyDownload now