7. Complete zeroing of zero-day vulnerabilities

[rakhirhif8963]

The Cloud Security Alliance (CSA) has identified several risk groups related to images, orchestrators, registries, containers themselves, host operating systems, and hardware. Here are some of the key risks that we expect to be increasingly exploited in the future:

Orchestrator risks: Increased attacks at the orchestration layer — Kubernetes and related APIs, primarily due to configuration errors;
Image or registry risks: Increased use of malicious or surreptitiously implanted images due to ineffective vulnerability checks;
Container risks. Increased attacks on vulnerable applications.
Increased exploitation of these vulnerabilities in 2022 could lead to resource abuse using cryptomining malware, data theft, support for persistent attacks, and host system penetration using containers.

How can you protect yourself? As a risk colombia mobile database measure, it is recommended to “build” security into the DevOps process by continuously monitoring for configuration errors, image integrity, and administrator privileges. Use the Mitre ATT&CK Matrix for Containers to identify weaknesses in your cloud security architecture.

Developing exploits for vulnerabilities now takes hours and there is nothing you can do about it... The only solution is patches.

When 17,000 SolarWinds customers had their data stolen in 2020, and about 40 of them were subsequently hacked, many were shocked by the scale of the breach. Unfortunately, the total number of compromised users has increased significantly in 2021, amid the slow response of companies to the cybercriminals. Case in point: two weeks after Microsoft released a patch for ProxyLogon, 30,000 Exchange servers were still vulnerable (other estimates put the number at 60,000).

That same year, a second major problem was discovered in Exchange: ProxyShell. In August, the day after Blackhat's presentation on Exchange Server vulnerabilities, a proof-of-concept exploit (POC exploit) was released for all the holes patched by Microsoft in April and May. According to a Shodan report, a week after the exploit appeared, more than 30,000 Exchange servers remained unprotected - and this data does not provide a complete picture of what was happening (Shodan specialists did not have time to scan the entire Internet). In short, the patches were released in the spring, but the corresponding vulnerabilities could be exploited in the fall.