Stealth Tunnels: The Dawn of Undetectable Remote Access

In today’s world, more employees work from home, coffee shops, or satellite offices than ever before. While remote access tools like VPNs have kept us connected, they’re increasingly easy for network gatekeepers to spot—and sometimes block or slow down. Enter stealth tunnels: an innovative way to disguise secure connections so they glide past firewalls and inspection tools unnoticed. In this article, we’ll explain what makes stealth tunnels different, why they matter, and how businesses can use them to keep their remote workers safe, productive, and uninterrupted.

In this deep dive, we’ll explore how stealth tunnels work, why they outperform legacy Virtual Private Network (VPN)s, and how enterprises can deploy them securely at scale.

Why Traditional VPNs Aren’t Enough

Imagine you’re trying to drive into a city through one of its main gates. A standard VPN is like a marked delivery truck: the guards know exactly what it is and can choose to let it through, inspect it, or stop it altogether. That’s because traditional VPNs use well-known ports and protocols—digital “signatures” that deep-packet inspection (DPI) tools and firewalls easily recognize.

When a business firewall sees VPN traffic, it can slow it down or block it outright, interrupting video conferences, halting large file transfers, or preventing access to critical systems. For employees in high-security environments—financial traders, healthcare technicians, or field engineers—these interruptions mean lost time, missed opportunities, and mounting frustration.

Stealth vs. Legacy VPN: A Feature Comparison

What Makes a Tunnel “Stealth”

Stealth tunnels wrap VPN traffic inside a form that looks, to the network’s gatekeepers, like harmless web browsing or random data. Think of it as putting our delivery truck inside an unmarked van that looks like any other car on the road. 

The key techniques include:

HTTPS Wrapping: The VPN connection is hidden inside a standard web-secure (HTTPS) session. Since almost all websites use HTTPS these days, this traffic simply blends in with normal browsing.

Port Hopping & Padding: Instead of listening on one fixed port, the tunnel randomly changes its port every few minutes. Network tools can’t easily predict which port to watch. Adding a bit of “padding”—small dummy data packets—further disguises the true nature of the traffic.

Handshake Obfuscation: Most VPNs follow a predictable “handshake” when connecting. Stealth tunnels randomize the timing and structure of this handshake so it doesn’t match known VPN patterns

Combined, these methods make the encrypted tunnel look like any other benign data flow, effectively slipping past DPI and firewall scrutiny.

Benefits of Stealth Tunnels

Uninterrupted Productivity

Because network tools can’t identify stealth tunnels, remote workers enjoy smoother video calls, faster file transfers, and reliable access to enterprise applications—no matter where they connect from.

Better Security

Stealth tunnels still use strong encryption under the hood. Even if someone tried to intercept the data, they’d see only scrambled bits inside a standard web stream.

Resilience Against Censorship & Throttling

In regions where VPNs are blocked or heavily slowed down, stealth tunnels can maintain connectivity by masquerading as regular web traffic. This is critical for global teams working in restrictive environments.

Explaining with Example: 

1.Traditional VPN: You launch your VPN client, which opens a connection on UDP port 1194. The café’s network equipment spots this, slows it down by 80%, and you struggle through a choppy video call.

2.Stealth Tunnel: You toggle “Stealth Mode” in your remote-access app. Your traffic is wrapped inside HTTPS on port 443, then jumps ports and adds padding. The café’s equipment treats it like normal web traffic—your call remains crystal clear.

How Businesses Can Deploy Stealth Tunnels

1. Choose a Stealth-Ready Solution

Look for remote-access platforms that offer an easy “stealth mode” switch. This often relies on the widely supported Wire Guard or OpenVPN technologies under the hood, enhanced with obfuscation modules.

2. Setup Stealth Gateways

Deploy one or more servers—called stealth gateways—in locations your users can reach, such as cloud regions or branch offices. These gateways unwrap the disguised traffic and forward it to your corporate network.

3. Roll Out Stealth Clients

Install or update the client apps on user devices (laptops, tablets, phones). A single toggle in the app enables all obfuscation features—no manual port configuration or scripting required.

4. Monitor and Rotate

Regularly update handshake parameters, encryption keys, and port ranges. A central management console can automate this, ensuring the tunnels remain undiscoverable over time.

Looking Ahead

As DPI and network monitoring tools become more powerful, stealth tunnels will continue to evolve. Future enhancements may include machine-learning to adapt obfuscation on the fly, quantum-safe encryption for extra peace of mind, and deeper integration with software-defined networks. Businesses that adopt stealth-capable remote access today will gain a crucial edge—keeping their distributed workforces connected, productive, and secure, no matter where they roam.

___

 

About the Author

Vikram Gupta is the Founder and CEO of Fibmesh, a trailblazer in software-defined mesh networks and secure remote-access solutions. With an experience in network engineering and a passion for democratizing connectivity, he leads the development of next-generation systems that empower organizations to build their own secure, adaptive infrastructures.

 

The post Stealth Tunnels: The Dawn of Undetectable Remote Access first appeared on Cybersecurity Insiders.

The post Stealth Tunnels: The Dawn of Undetectable Remote Access appeared first on Cybersecurity Insiders.

from Cybersecurity Insiders https://ift.tt/1s6AJ4f
via IFTTT

AWS Weekly Roundup: Amazon Nova Premier, Amazon Q Developer, Amazon Q CLI, Amazon CloudFront, AWS Outposts, and more (May 5, 2025)

Last week I went to Thailand to attend the AWS Summit Bangkok. It was an energizing and exciting event. We hosted the Developer Lounge, where developers can meet, discuss ideas, enjoy lightning talks, win SWAGs at AWS Builder ID Prize Wheel, take a challenge at Amazon Q Developer Coding Challenge, or learn Generative AI at Learn Amazon Bedrock booth.

Here’s a quick look:

Thank you to AWS Heroes, AWS Community Builders, AWS User Group leaders and developers for your collaboration.

Coming up next in ASEAN is AWS Summit Singapore—make sure you don’t miss it by registering now.

Last Week’s Launches
Here are some launches last week that caught my attention:

  • Amazon Nova Premier Now Generally Available — Amazon Nova Premier, our most capable model for complex tasks and teacher for model distillation, is now generally available in Amazon Bedrock. It excels at complex tasks requiring deep context understanding and multistep planning, while processing text, images, and videos with a 1M token context length. With Nova Premier and Amazon Bedrock Model Distillation, you can create highly capable, cost-effective, and low-latency versions of Nova Pro, Lite, and Micro, for your specific needs.

  • Amazon Q Developer elevates the IDE experience with new agentic coding experience — This new interactive, agentic coding experience for Visual Studio Code allows Q Developer to intelligently take actions on behalf of the developer. Amazon Q Developer introduces an interactive coding experience in Visual Studio Code, offering real-time collaboration for coding, documentation, and testing. It provides transparent reasoning, and supports automated or step-by-step changes in multiple languages.

  • New Foundation Models in Amazon Bedrock — Amazon Bedrock expands its model offerings with two significant additions:
    • Writer’s Palmyra X5 and X4 models feature extensive context windows (1M and 128K tokens respectively) and excel in complex reasoning for enterprise applications. They support multistep tool-calling and adaptive thinking with high reliability standards.
    • Meta’s Llama 4 Scout 17B and Maverick 17B models offer natively multimodal capabilities using mixture-of-experts architecture for enhanced reasoning and image understanding. They support multiple languages and extended context processing, with simplified integration through the Bedrock Converse API.
  • Second-Generation AWS Outposts Racks Released AWS announces the general availability of second-generation Outposts racks with significant enhancements including the latest x86 EC2 instances, simplified networking, and accelerated networking options. These improvements deliver doubled vCPU, memory, and network bandwidth, 40% better performance, and support for ultra-low latency workloads, making them ideal for demanding on-premises deployments.
  • Amazon CloudFront SaaS Manager Launches — Amazon CloudFront SaaS Manager helps SaaS providers and web hosting platforms efficiently manage content delivery across multiple customer domains. The service dramatically reduces operational complexity while providing high-performance content delivery and enterprise-grade security for every customer domain.

  • Amazon Aurora Now Supports PostgreSQL 17 — Amazon Aurora now supports PostgreSQL 17.4, offering community improvements and Aurora-specific enhancements like optimized memory management and faster failovers. The release includes new features for Babelfish, security fixes, and updated extensions, available in all AWS Regions.
  • CloudWatch Introduces Tiered Pricing for Lambda Logs — Amazon CloudWatch launches tiered pricing for AWS Lambda logs and new delivery destinations. Pricing in US East starts at $0.50/GB for CloudWatch and $0.25/GB for S3 and Firehose, both tiering down to $0.05/GB. This update enhances flexibility in log management across all supporting Regions.
  • RDS for MySQL Updates Minor VersionsAmazon RDS for MySQL now supports minor versions 8.0.42 and 8.4.5, delivering security fixes, bug fixes, and performance improvements. Users can upgrade automatically during maintenance windows or use Blue/Green deployments for safer updates.
  • Amazon Bedrock Model Distillation Generally AvailableAmazon Bedrock Model Distillation is now generally available, supporting new models like Amazon Nova and Claude 3.5. It enables smaller models to accurately predict function calling for Agents, delivering up to 500% faster responses and 75% lower costs with minimal accuracy loss for RAG use cases. The service includes automated workflows for data synthesis and student model training.
  • AI Search Flow Builder for Amazon OpenSearch Service Amazon OpenSearch Service now offers an AI search flow builder for OpenSearch 2.19+ domains. This low-code designer enables creation of sophisticated AI-enhanced search flows using AWS and third-party services, supporting use cases like RAG, query rewriting, and semantic encoding.

From Community.AWS
Here’s my personal favorites posts from community.aws:

Upcoming AWS events
Check your calendars and sign up for these upcoming AWS events:

  • AWS Summit — Join free online and in-person events that bring the cloud computing community together to connect, collaborate, and learn about AWS. Register in your nearest city: Poland (6 May), Bengaluru (May 7 – 8), Hong Kong (May 8), Seoul (May 14-15), Singapore (May 29), and Sydney (June 4–5).
  • AWS re:Inforce – Mark your calendars for AWS re:Inforce (June 16–18) in Philadelphia, PA. AWS re:Inforce is a learning conference focused on AWS security solutions, cloud security, compliance, and identity. You can subscribe for event updates now!
  • AWS Partners Events – You’ll find a variety of AWS Partner events that will inspire and educate you, whether you are just getting started on your cloud journey or you are looking to solve new business challenges.
  • AWS Community Days – Join community-led conferences that feature technical discussions, workshops, and hands-on labs led by expert AWS users and industry leaders from around the world: Yerevan, Armenia (May 24), Zurich, Switzerland (May 25), and Bengaluru, India (May 25).

You can browse all upcoming in-person and virtual events.

That’s all for this week. Check back next Monday for another Weekly Roundup!


How is the News Blog doing? Take this 1 minute survey!

(This survey is hosted by an external company. AWS handles your information as described in the AWS Privacy Notice. AWS will own the data gathered via this survey and will not share the information collected with survey respondents.)

from AWS News Blog https://ift.tt/g8ioX5k
via IFTTT

Amazon Q Developer in GitHub (in preview) accelerates code generation

Starting today, you can now use Amazon Q Developer in GitHub in preview! This is fantastic news for the millions of developers who use GitHub on a daily basis, whether at work or for personal projects. They can now use Amazon Q Developer for feature development, code reviews, and Java code migration directly within the GitHub interface.

To demonstrate, I’m going to use Amazon Q Developer to help me create an application from zero called StoryBook Teller. I want this to be an ASP.Core website using .NET 9 that takes three images from the user and uses Amazon Bedrock with Anthropic’s Claude to generate a story based on them.

Let me show you how this works.

Installation

The first thing you need to do is install the Amazon Q Developer application in GitHub, and you can begin using it immediately without connecting to an AWS account.

You’ll then be presented with a choice to add it to all your repositories or select specific ones. In this case, I want to add it to my storybook-teller-demo repo, so I choose Only selected repositories and type in the name to find it.

This is all you need to do to make the Amazon Q Developer app ready to use inside your selected repos. You can verify that the app is installed by navigating to your GitHub account Settings and the app should be listed in the Applications page.

You can choose Configure to view permissions and add Amazon Q Developer to repositories or remove it at any time.

Now let’s use Amazon Q Developer to help us build our application.

Feature development
When Amazon Q Developer is installed into a repository, you can assign GitHub issues to the Amazon Q development agent to develop features for you. It will then generate code using the whole codebase in your repository as context as well as the issue’s description. This is why it’s important to list your requirements as accurately and clearly as possible in your GitHub issues, the same way that you should always strive for anyway.

I have created five issues in my StoryBook Teller repository that cover all my requirements for this app, from creating a skeleton .NET 9 project to implementing frontend and backend.

Let’s use Amazon Q Developer to develop the application from scratch and help us implement all these features!

To begin with, I want Amazon Q Developer to help me create the .NET project. To do this, I open the first issue, and in the Labels section, I find and select Amazon Q development agent.

That’s all there is to it! The issue is now assigned to Amazon Q Developer. After the label is added, the Amazon Q development agent automatically starts working behind the scenes providing progress updates through the comments, starting with one saying, I'm working on it.

As you might expect, the amount of time it takes will depend on the complexity of the feature. When it’s done, it will automatically create a pull request with all the changes.

The next thing I want to do is make sure that the generated code works, so I’m going to download the code changes and run the app locally on my computer.

I go to my terminal and type git fetch origin pull/6/head:pr-6 to get the code for the pull request it created. I double-check the contents and I can see that I do indeed have an ASP.Core project generated using .NET 9, as I expected.

I then run dotnet run and open the app with the URL given in the output.

Brilliant, it works! Amazon Q Developer took care of implementing this one exactly as I wanted based on the requirements I provided in the GitHub issue. Now that I have tested that the app works, I want to review the code itself before I accept the changes.

Code review
I go back to GitHub and open the pull request. The first thing I notice is that Amazon Q Developer has performed some automatic checks on the generated code.

This is great! It has already done quite a bit of the work for me. However, I want to review it before I merge the pull request. To do that, I navigate to the Files changed tab.

I review the code, and I like what I see! However, looking at the contents of .gitignore, I notice something that I want to change. I can see that Amazon Q Developer made good assumptions and added exclusion rules for Visual Studio (VS) Code files. However, JetBrains Rider is my favorite integrated development environment (IDE) for .NET development, so I want to add rules for it, too.

You can ask Amazon Q Developer to reiterate and make changes by using the normal code review flow in the GitHub interface. In this case, I add a comment to the .gitignore code saying, add patterns to ignore Rider IDE files. I then choose Start a review, which will queue the change in the review.

I select Finish your review and Request changes.

Soon after I submit the review, I’m redirected to the Conversation tab. Amazon Q Developer starts working on it, resuming the same feedback loop and encouraging me to continue with the review process until I’m satisfied.

Every time Q Developer makes changes, it will run the automated checks on the generated code. In this case, the code was somewhat straightforward, so it was expected that the automatic code review wouldn’t raise any issues. But what happens if we have more complex code?

Let’s take another example and use Amazon Q Developer to implement the feature for enabling image uploads on the website. I use the same flow I described in the previous section. However, I notice that the automated checks on the pull request flagged a warning this time, stating that the API generated to support image uploads on the backend is missing authorization checks effectively allowing direct public access. It explains the security risk in detail and provides useful links.

It then automatically generates a suggested code fix.

When it’s done, you can review the code and choose to Commit changes if you’re happy with the changes.

After fixing this and testing it, I’m happy with the code for this issue and move on applying the same process to other ones. I assign the Amazon Q development agent to each one of my remaining issues, wait for it to generate the code, and go through the iterative review process asking it to fix any issues for me along the way. I then test my application at the end of that software cycle and am very pleased to see that Amazon Q Developer managed to handle all issues, from project setup, to boilerplate code, to more complex backend and frontend. A true full-stack developer!

I did notice some things that I wanted to change along the way. For example, it defaulted to using the Invoke API to send the uploaded images to Amazon Bedrock instead of the Converse API. However, because I didn’t state this in my requirements, it had no way of knowing. This highlights the importance of being as precise as possible in your issue’s titles and descriptions to give Q Developer the necessary context and make the development process as efficient as possible.

Having said that, it’s still straightforward to review the generated code on the pull requests, add comments, and let the Amazon Q Developer agent keep working on changes until you’re happy with the final result. Alternatively, you can accept the changes in the pull request and create separate issues that you can assign to Q Developer later when you’re ready to develop them.

Code transformation
You can also transform legacy Java codebases to modern versions with Q Developer. Currently, it can update applications from Java 8 or Java 11 to Java 17, with more options coming in future releases.

The process is very similar to the one I demonstrated earlier in this post, except for a few things.

First, you need to create an issue within a GitHub repository containing a Java 8 or Java 11 application. The title and description don’t really matter in this case. It might even be a short title such as “Migration,” leaving the description empty. Then, on Labels, you assign the Amazon Q transform agent label to the issue.

Much like before, Amazon Q Developer will start working immediately behind the scenes before generating the code on a pull request that you can review. This time, however, it’s the Amazon Q transform agent doing the work which is specialized in code migration and will take all the necessary steps to analyze and migrate the code from Java 8 to Java 17.

Notice that it also needs a workflow to be created, as per the documentation. If you don’t have it enabled yet, it will display clear instructions to help you get everything set up before trying again.

As expected, the amount of time needed to perform a migration depends on the size and complexity of your application.

Conclusion
Using Amazon Q Developer in GitHub is like having a full-stack developer that you can collaborate with to develop new features, accelerate the code review process, and rely on to enhance the security posture and quality of your code. You can also use it to automate migration from Java 8 and 11 applications to Java 17 making it much easier to get started on that migration project that you might have been postponing for a while. Best of all, you can do all this from the comfort of your own GitHub environment.

Now available
You can now start using Amazon Q Developer today for free in GitHub, no AWS account setup needed.

Amazon Q Developer in GitHub is currently in preview.

Matheus Guimaraes | codingmatheus


How is the News Blog doing? Take this 1 minute survey!

(This survey is hosted by an external company. AWS handles your information as described in the AWS Privacy Notice. AWS will own the data gathered via this survey and will not share the information collected with survey respondents.)

from AWS News Blog https://ift.tt/n1wPod2
via IFTTT

The Paramount Importance of Strong Passwords and Credential Hygiene

“This World Password Day is a timely reminder that strong passwords are more than just a best practice, they are critical to safeguarding our personal and professional digital lives. In a world where our data is stored, processed, and accessed online, the strength and security of our credentials can determine whether we remain protected or become vulnerable to cyber threats.

Strong passwords serve as the frontline defence against unauthorised access. They protect not only emails and personal files, but also critical infrastructure, cloud platforms, and autonomous systems that run in the background, such as service accounts, APIs, and automated workflows. As these digital agents increasingly interact without human oversight, securing their credentials becomes just as vital as protecting user logins.

Using complex, unique passwords—blending uppercase and lowercase letters, numbers, and symbols—significantly reduces the risk of brute-force attacks. However, password strength alone is not enough. Each credential should be unique and managed carefully, especially for software accounts with elevated privileges or persistent access.

Weak password practices can lead to devastating consequences: data breaches, identity theft, financial loss, and reputational harm. For organisations, compromised credentials—especially those tied to automation or backend systems can trigger widespread service disruptions, intellectual property theft, and costly compliance violations.

Organisations must adopt a layered approach to password security to combat these risks. This includes implementing multi-factor authentication (MFA), enforcing password complexity and rotation policies, and using secure credential management solutions to protect both human and machine accounts. Regular security training, audits, and awareness campaigns ensure that employees understand the stakes and uphold best practices.

Ultimately, securing our digital world means protecting every entry point—human or machine—with diligence and care.”

 

The post The Paramount Importance of Strong Passwords and Credential Hygiene first appeared on Cybersecurity Insiders.

The post The Paramount Importance of Strong Passwords and Credential Hygiene appeared first on Cybersecurity Insiders.

from Cybersecurity Insiders https://ift.tt/Q6PIwj9
via IFTTT

Amazon Q Developer elevates the IDE experience with new agentic coding experience

Today, Amazon Q Developer introduces a new, interactive, agentic coding experience that is now available in the integrated development environments (IDE) for Visual Studio Code. This experience brings interactive coding capabilities, building upon existing prompt-based features. You now have a natural, real-time collaborative partner working alongside you while writing code, creating documentation, running tests, and reviewing changes.

Amazon Q Developer transforms how you write and maintain code by providing transparent reasoning for its suggestions and giving you the choice between automated modifications or step-by-step confirmation of changes. As a daily user of Amazon Q Developer command line interface (CLI) agent, I’ve experienced firsthand how Amazon Q Developer chat interface makes software development a more efficient and intuitive process. Having an AI-powered assistant only a q chat away in CLI has streamlined my daily development workflow, enhancing the coding process.

The new agentic coding experience in Amazon Q Developer in the IDE seamlessly interacts with your local development environment. You can read and write files directly, execute bash commands, and engage in natural conversations about your code. Amazon Q Developer comprehends your codebase context and helps complete complex tasks through natural dialog, maintaining your workflow momentum while increasing development speed.

Let’s see it in action
To begin using Amazon Q Developer for the first time, follow the steps in the Getting Started with Amazon Q Developer guide to access Amazon Q Developer. When using Amazon Q Developer, you can choose between Amazon Q Developer Pro, a paid subscription service, or Amazon Q Developer Free tier with AWS Builder ID user authentication.

For existing users, update to the new version. Refer to Using Amazon Q Developer in the IDE for activation instructions.

To start, I select the Amazon Q icon in my IDE to open the chat interface. For this demonstration, I’ll create a web application that transforms Jupiter notebooks from the Amazon Nova sample repository into interactive applications.

I send the following prompt: In a new folder, create a web application for video and image generation that uses the notebooks from multimodal-generation/workshop-sample as examples to create the applications. Adapt the code in the notebooks to interact with models. Use existing model IDs

Amazon Q Developer then examines the files: the README file, notebooks, notes, and everything that is in the folder where the conversation is positioned. In our case it’s at the root of the repository.

After completing the repository analysis, Amazon Q Developer initiates the application creation process. Following the prompt requirements, it requests permission to execute the bash command for creating necessary folders and files.

With the folder structure in place, Amazon Q Developer proceeds to build the complete web application.

In a few minutes, the application is complete. Amazon Q Developer provides the application structure and deployment instructions, which can be converted into a README file upon request in the chat.

During my initial attempt to run the application, I encountered an error. I described it in Spanish using Amazon Q chat.

Amazon Q Developer responded in Spanish and gave me the solutions and code modifications in Spanish! I loved it!

After implementing the suggested fixes, the application ran successfully. Now I can create, modify, and analyze images and videos using Amazon Nova through this newly created interface.

The preceding images showcase my application’s output capabilities. Because I asked to modify the video generation code in Spanish, it gave me the message in Spanish.

Things to know
Chatting in natural languages – Amazon Q Developer IDE supports many languages, including English, Mandarin, French, German, Italian, Japanese, Spanish, Korean, Hindi, and Portuguese. For detailed information, visit the Amazon Q Developer User Guide page.

Collaboration and understanding – The system examines your repository structure, files, and documentation while giving you the flexibility to interact seamlessly through natural dialog with your local development environment. This deep comprehension allows for more accurate and contextual assistance during development tasks.

Control and transparency – Amazon Q Developer provides continuous status updates as it works through tasks and lets you choose between automated code modifications or step-by-step review, giving you complete control over the development process.

Availability – Amazon Q Developer interactive, agentic coding experience is now available in the IDE for Visual Studio Code.

Pricing – Amazon Q Developer agentic chat is available in the IDE at no additional cost to both Amazon Q Developer Pro Tier and Amazon Q Developer Free tier users. For detailed pricing information, visit the Amazon Q Developer pricing page.

To learn more about getting started visit the Amazon Q Developer product web page.

— Eli


How is the News Blog doing? Take this 1 minute survey!

(This survey is hosted by an external company. AWS handles your information as described in the AWS Privacy Notice. AWS will own the data gathered via this survey and will not share the information collected with survey respondents.)

from AWS News Blog https://ift.tt/xUWYh8w
via IFTTT

Quantum computer threat spurring quiet overhaul of internet security

SAN FRANCISCO — Cryptography experts say the race to fend off future quantum-computer attacks has entered a decisive but measured phase, with companies quietly replacing the internet plumbing that the majority of the industry once considered unbreakable.

Speaking at Cloudflare’s Trust Forward Summit on Wednesday, encryption leaders at IBM Research, Amazon Web Services and Cloudflare outlined how organizations are refitting cryptographic tools that safeguard online banking, medical data and government communications. The aim is to stay ahead of quantum machines that, once powerful enough, could decode the math protecting today’s digital traffic.

“Over the next five to 10 years you’re going to see a Cambrian explosion of different cryptographic systems,” said Wesley Evans, a product manager for Cloudflare’s research team, referring to an evolutionary period with a rapid diversification of animal life that occurred roughly 540 million years ago. 

“Whether it’s nationalized cryptography out of South Korea [or] new standards from [the National Institute of Standards and Technology], this is a time to think about not just, ‘how am I doing my post-quantum migration?’ but ‘how am I doing my whole crypto-agility platform?’ and ‘how am I thinking through my audits and inventory?’” he said. 

“Harvest-now, decrypt-later” attacks already target data that must remain secret for decades, panelists said. Adversaries are stealing data like encrypted medical records or defense contracts and storing it on cheap cloud servers in hopes of unlocking them once quantum code-breaking matures.

Cloudflare, which routes roughly 20% of global web traffic, said it has spent eight years weaving post-quantum algorithms into its backbone. The company now secures more than 40% of its daily HTTPS requests with so-called hybrid handshakes that combine traditional RSA keys and newer lattice-based methods.

Executives described the rollout as intentionally low-profile. “Trillions of requests per day are already running across Cloudflare’s network in a post-quantum secure manner,” Evans said. “We did it without users noticing a speed decrease, performance impact or incurring any additional cost.”

IBM researchers, who develop quantum hardware as well as defensive tools, cautioned that this change could possibly take a decade before it’s the norm. 

“Moving to a new generation of cryptography, quantum-safe or otherwise, will take us roughly seven to 10 years, maybe longer,” said John Buselli, a business development executive and offering manager for IBM Quantum Safe, additionally pointing out that relics of older code, such as SHA-1, linger long after formal retirement.

NIST is finalizing a first batch of post-quantum algorithms, including the key-encapsulation mechanism known as ML-KEM. Cloudflare and browser makers have already adopted preliminary versions while awaiting NIST’s final parameters. Developers also wrap new keys inside legacy RSA exchanges to guard against unforeseen side-channel flaws.

Beyond mathematics, panelists emphasized logistics. Enterprises must inventory where encryption lives, from custom apps to vendor appliances, then gauge how quickly each layer can swap libraries. Much of that code is “black box,” owned by suppliers that set their own schedules.

“The rate of change is going to be determined by the least agile piece of infrastructure you have,” Buselli said, likening the process to mapping out all the connections in an infrastructure upgrade instead of addressing just a single security issue.

The panel also urged companies to fold cryptography into broader modernization budgets. Boards may balk at paying solely for an invisible security upgrade, they said, but will authorize spending tied to performance gains such as those seen with the newest TLS 1.3 protocol.

No panelist offered a firm deadline for full retirement of RSA and elliptic-curve keys. Instead they described “a long journey” marked by quiet iterations and cooperative testing across browsers, servers and chipmakers.

“Cryptography is a multi-party game,” Evans said. “You’ve got to work with everybody to make sure it’s secure for everyone.”

The post Quantum computer threat spurring quiet overhaul of internet security appeared first on CyberScoop.

from CyberScoop https://ift.tt/VdihU2J
via IFTTT