Earlier this year, Quantum computing took another big step out of the laboratory and toward commercial viability with the release of the IBM Q System One. Last year Google announced its ‘Bristlecone’ Quantum Computing Chip.
While the U.S. Federal government is running (for now) again, there remains a concern that the partial shutdown will have a long-term impact on the cybersecurity readiness of the nation.
The promise was that cloud computing would simplify enterprise business-technology. Enterprise users would be able to focus on their applications and services while leaving the deeper security issues associated with infrastructure and secure delivery and management of applications to the cloud provider. It didn’t exactly turn out that way.
In the modern enterprise, APIs are both the keys that unlockdata and the glue that makes system integration possible. But how steep are the associated security concerns APIs create?
Privileged accounts are those accounts you most definitely never want to lose control over. These accounts include what used to be commonly called “superuser” accounts, those accounts that provide the highest level of access to a system, such as a server, local endpoints, and others. You can consider privileged accounts to be like administrative accounts that provide a higher level of access, typically to configure, manage and otherwise support a system. These types of accounts are often unrestricted, or lightly restricted.
When it comes to securing a public cloud infrastructure, many organizations are under the impression that the workloads they run are secured by their cloud services provider. This just isn’t so, and the lackadaisical attitude has resulted in a number of high-profile breaches, including the exposure of 1.8 million records pertaining to U.S. voters.
Despite regulatory mandates and years of costly data breaches in the healthcare industry, a recent survey found that less than one-third of healthcare organizations say they have a comprehensive cybersecurity program in place.
First the good news: according to a published report there were more than 16,000 software vulnerabilities disclosed during the first nine months of this year. Now, that’s quite a few vulnerabilities that could enable attackers, exploits, and malware to scurry onto an enterprise environment. However, it is 7 percent fewer vulnerabilities than 2017.
If your organization has a healthy cybersecurity culture, consider yourself lucky — less than five percent of organizations do.
DevOps has come a long way since it got underway in full force nearly ten years ago. As was recently made clear at this year’s DevOps Enterprise Summit (DOES) in Las Vegas, DevOps organizations have been successful when it comes to knocking down organizational silos, optimizing the delivery of software services and functionality, and shortening the time it takes to deliver digital value to customers. DevOps organizations are delivering better business outcomes.
While many had hoped that along with the rise of cloud computing would come a more simple era of enterprise computing. In some ways, it has. With software as a service enterprise no longer have to contend with managing the infrastructure to support so many applications. With infrastructure as a service enterprises can cut the amount of infrastructure they must manage. It’s reduced the amount of infrastructure and applications that must be directly protected, patched, and maintained. But the era of more simple computing never arose.
The Center for Medicare and Medicaid Services (CMS) announced that it has detected anomalous activity in its Federally Facilitated Exchanges (FFEs) Direct Enrollment pathway for agents and brokers. This is the system that enables agents and brokers to help consumers with their coverage applications to the FFEs. One can imagine the type and quantity of sensitive information shared on these systems.
