Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

There is a hard deadline for post-quantum code signing: You sign a certificate in 2026 that may still be needed to check the certificate on a device in 2035 that you can’t re-flash. This post covers what PQC signatures are, why RSA/DSA/ECDSA doesn’t work against a CRQC, how code signing is different from SSL, and what AWS, Google, and MS shipped. Inventory paths. Select an algorithm class. Test dual-sign. Follow cert and KMS roadmaps.

Many SD-WAN refreshes start with an expiring contract or edge equipment reaching end of life. But replacing the edge should not be the measure of success. For network and infrastructure leaders, the real test is what improves after the refresh. Will the refresh put IT on another appliance cycle, or move the WAN to a cloud service? Can IT keep critical applications performing consistently? Can the WAN respond when network conditions change?

We've heard everyone talk about digital privacy, cybersecurity, and how we should set a strong password, but what most people fail to understand is the why. Why is it important to set a strong password? Why do we have to activate two-factor authentication? Why are software updates important? Even though we have a vague idea of why we need to do these things, we really don't know the future implications if we don't secure our digital information.