Knowing the difference between the two types of technical challenges is the key to smarter decisions

Thomas Jefferson famously proclaimed that all men are created equal, but he would agree that today’s technical problems are not. Some are tied to the quirks of a specific product or vendor, while others are rooted in the static, immutable realities of technology itself. Knowing which is which can help you avoid frustration, wasted time, and even lapses in cybersecurity.

Before gearing up to solve a technical problem, understand the difference between those that are vendor-related, like getting a security patch to work on mixed operating systems, and technology-related, such as the limitations of wireless and radio frequencies networking traversing dense concrete walls.  

Buckle up as we delve into approaches for solving the two types of problems and cover a real-world case study ‌straddling both: ‌SSL inspection and the‌ insurmountable certificate-pinned applications.

Vendor shortcomings 

Imagine buying a car that looks great on paper but ends up always needing repairs. That’s what vendor platform and product challenges can feel like. These hiccups arise from limitations in a specific vendor’s offering, whether they be intentional or unintentional. They can be frustrating, but are usually fixable. Here’s how they show up:

• Missing features: Need a feature? Sorry, this product doesn’t have it yet.
• Performance issues: It works…but only if you don’t push it too hard.
• Integration nightmares: Connecting it to other vendor tools is like fitting a square peg into a round hole.
• Confusing workflows: Using the product feels like solving a Rubik’s cube blindfolded.

The good news: vendors can address these problems with updates, patches, or redesigns. Or you can switch to a better solution.

When the laws of tech just say ‘no”

Now, let’s talk about the tougher sibling: technology problems. These are ‌universal hurdles that no vendor or provider, no matter how good, can overcome, at least today. These types of problems are baked right into ‌technology itself, governed by fundamental rules, standards, and even physics. Here are some common ones:

• Encryption standards: Without the key, good luck decrypting.
• Protocol limitations: TCP/IP can’t bend to your will, no matter how much you wish it would.
• Physical constraints: The speed of light isn’t speeding up anytime soon, so latency is here to stay.

When you’re up against a technology problem or challenge, there’s no quick fix. You need innovation, clever workarounds, or a complete rethink before you can declare victory.

The table below summarizes the two types of challenges:

SSL inspection

Let’s bring this to life with SSL inspection. For the uninitiated, SSL inspection is the process of intercepting and reviewing SSL-encrypted internet communication between the client and the server. Since the vast majority of internet traffic is SSL encrypted, including malicious content, it is important. However, it’s a poster child for both platform/product and technology challenges. 

Some vendors overpromise and underdeliver with their SSL inspection capabilities, which can:

• Choke under pressure: Struggle with performance at scale
• Leave gaps: Fail to support newer encryption protocols
• Confuse admins: Make rule-setting unnecessarily complex

These vendor-caused issues can make life harder for you and your team. Address them by switching to a more capable solution or upgrading your infrastructure.

Now for the technology challenge of SSL inspection: certificate pinning. This is a process in where a non-browser desktop/mobile application validates that the TLS certificates presented by the application's backend TLS web servers match a known set of certificates pinned or hardcoded in the application. If it doesn’t match, the app says, “Nope!,” and rejects the connection. Here’s why no product can solve this:

• Encryption principles: SSL/TLS encryption is designed to be unbreakable without the private key.
• Pinning mechanisms: Apps with certificate pinning block any intermediaries—like your SSL inspection tool—to protect against man-in-the-middle attacks.

It’s not a bug; it’s a feature. And it’s why this challenge is universal. But you can adapt and work around it:

• Bypass trusted apps: Simply skip SSL inspection for the certificate-pinned apps you trust. It’s not perfect, but it works.
• Work with vendors: Encourage providers to implement secure alternatives that play nice with inspection tools.
• Use behavioral analytics: Turn to AI tools to ‌monitor app behavior without decrypting traffic

Applying the problem dichotomy to your technology decisions

Before you select a new product or platform, take a step back and consider the challenges that it may pose alongside the benefits. Ask your stakeholders: 

Is there a technical aspect that will pose a problem, and if so, is it a vendor issue? Can another product solve the problem? Will this offering fix another ongoing problem?

Is there a technical aspect that will pose a problem? Is there a tech limitation? If yes, what workarounds can we implement?

You can ask similar questions when choosing new offerings because of the need to adopt new standards like Wi-Fi 7 or operating systems that support IPv6 as an example.  

Crafting better solutions 

Understanding the difference between platform/product and technology challenges is more than a nice-to-have—it’s essential. Whether you’re dealing with SSL inspection or any other tech situation, knowing what you’re up against helps you craft smarter, more effective solutions.

In the world of tech, there’s no shame in facing challenges. The key is to recognize what kind of challenge you’re dealing with—and tackle it head-on.