Grzegorz Adamowicz’s Post

Robust #authentication is a must. If you can’t determine who your users are, you can’t then use that information throughout your infrastructure to control access. Learn how to implement authentication with Edge Stack API Gateway as the start of a #ZeroTrust framework. https://bit.ly/49XK0pT

Good #DigitalSecurity News: The Developing ECH for OpenSSL (DEfO) project’s first external security audit from Open Technology Fund's Red Team Lab vendor 7ASecurity revealed zero directly exploitable vulnerabilities! This result is unusual for any audit, but especially a first audit.

🔥 Last week, we announced Rad Security! The goal of the RAD security standard is to reverse the balance of power in software supply chain security. If development teams can compare a verified, clean runtime fingerprint against the same image running in their environment, they have a real chance in defending against the next zero day attack! ☠ Sign up for early access here: https://lnkd.in/e7-F3Zad #zeroday #runtime # #softwaresupplychainsecurity

🔐✨ Enhancing container security in cloud computing! InitVerse implements robust measures: 1️⃣ Auth & Auth: Users undergo identity verification and permission-based authorization before accessing container services, ensuring secure interactions. 2️⃣ Image Verification: Container images undergo thorough checks to reject any with malicious code or vulnerabilities, safeguarding user containers from potential threats. 3️⃣ Isolation & Monitoring: Illegal providers are thwarted through container isolation, preventing unauthorized access. Continuous monitoring ensures timely detection and resolution of security issues. 4️⃣ Backup & Recovery: InitVerse prioritizes disaster recovery with regular container backups stored in multiple locations. In case of unforeseen events, swift restoration maintains data security. 🚀⚙️ Providing users with a secure cloud computing experience! #CloudSecurity #ContainerTechnology #InitVerse #DataProtection

It's hard to believe that people design DNS protocol extensions (and implementations of the same) that allow for arbitrarily large computational costs for processing a simple query. But here we are. Suicide by DDOS. The first DNS resolver had a countdown for every query processed to guard against this or code errors that might create infinite loops.

What happened on 19th July 2024. A null pointer in laymen terms, when your application tries to access an address in this case memory pointer which does not exists. IMO, it’s a lack of thorough testing of a software deployed globally. There must be some serious organisational / procesural flaws in rolling out such critical deployments. Read more on it in below article. https://lnkd.in/dHY74_7Q

Enterprises continue to run insecure protocols across their WAN, with 62% of all web application traffic being HTTP, 54% of all traffic being telnet, and 46% of all traffic being SMB v1 or v2 instead of SMBv3.

New Post: SSL Overhead: What It Is and How to Reduce It?

"If an error as input creates an error as output, and a second system behaves the same, these two systems will keep sending error messages back and forth indefinitely." That is why integration testing coupled with proper Architecture design are key requirements for successful operations. very interesting article.. check this new attack method. #cyberattacks

Affected product OpenSSH: Versions before 4.4p1 Versions 8.5p1 to 9.8p1 https://lnkd.in/gR4WFagq Can try it yourself, POC : https://lnkd.in/gDqWtn-S