Cybersecurity

Attackers can remotely execute code with System privileges by exploiting a vulnerability in the source code of the open-source container management system.

Just because Google has put in the work to quantum-proof Chrome doesn't mean post-quantum security is all set.

Boards of directors don't care about the minute technical details of the security program. They want to see how key performance indicators are tracked and utilized.

This month's patches are oddly "light". We have patches for 60 vulnerabilities and 4 Chromium patches affecting Microsoft Edge. But only two of the vulnerabilities are rated as "Critical":

CVE-2024-21408: Windows Hyper-V Denial of Service Vulnerability CVE-2024-21407: Windows Hyper-V Remote Code Execution Vulnerability

Oddly, Microsoft considers a DoS vulnerability "critical". However, a DoS against Hyper-V could have a significant impact, which may justify the rating. The code execution vulnerability justifies a rating of critical. However, exploitation requires an attacker to first gain a foothold inside a virtual machine.

Other vulnerabilities of interest:

CVE-2024-26198: A remote code execution vulnerability for Exchange Server. This is a DLL loading issue that is typically more difficult to exploit. Authentication is required to exploit the vulnerability.

Overall, this Patch Tuesday doesn't look too bad. Follow your normal patch management process. There is no need to get all worked up; tomorrow morning: Have some coffee, test... and later deploy once the tests are completed successfully.

Join us for an interview with Darren Thomson, Field Chief Technology Officer at Commvault, as we delve into the dynamic

So I've been trying to create more secured passwords now that I have employment where I have responsibility. They require us to change our passwords every 3 months. I used to use the same passwords for multiple sites. Then I used a password manager and got rid of those memory passwords. With this job I don't want to mix my personal password manager with my work computer and I also don't want to remember a complicated 15 character long password to log in every day.

That brings me to my question. I've been using Yubikeys for years. I store a challenge response, use it for 2FA on all sites that allow, and I use it for TOTP on most sites (there's a limit to how many entries in the Yubikey 5). You can also store a password in one of it's two slots. My thinking is this: Is it secure to store a base password that is long and complicated, say 40 characters long with all the characters, and use a different "prefix" for each application? Example: On my banking site I type in "bank" then press the Yubikey to type the rest. Same thing with social media and other accounts. Each one has a prefix and I don't know the actual password. Of course I store all passwords, including the Yubikey, in a password manager that's backed up in the cloud (I use KeePassXC).

Your thoughts? Is this secure or stupid?

Nothing fancy or new on this article, but the basics should prevent tears:

1. Regularly checking and updating access control policies to prevent orphaned accounts from becoming security vulnerabilities.
2. Consistently reviewing delegations and managing permissions to ensure no individual has too much control and to reduce the risk of cybersecurity issues.
3. Maintaining control over the cloud environment with cloud governance solutions to enforce stringent security policies and streamline management processes.

French Government Services Hit by Intense Cyberattacks: Anonymous Sudan Claims Responsibility for the Denial-of-Service Assaults with Significant Online Disruption

Here are three other sites not listed in this article that you can also use to learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Interesting view on this situation.

Memory-safe languages let programmers focus on quality code, avoiding risks of low-level memory management.

Microsoft reported a breach by Russian group 'Midnight Blizzard,' which accessed internal systems and source code using stolen authentication secrets from a January cyberattack. The unauthorized access was facilitated by a compromised non-production test account lacking multi-factor authentication and linked to an OAuth app with elevated privileges. Microsoft is contacting affected customers and has ramped up security measures to counter the persistent threat.