RECENT BLOG NEWS

So, what’s new at wolfSSL? Take a look below to check out the most recent news, or sign up to receive weekly email notifications containing the latest news from wolfSSL. wolfSSL also has a support-specific blog page dedicated to answering some of the more commonly received support questions.

wolfSSL 5.9.1 release blog

wolfSSL 5.9.1 is available with new features, post-quantum cryptography improvements, broad bug fixes, and a number of vulnerability fixes. Users are always recommended to stay up to date with wolfSSL releases. In this release, use cases that are affected by high severity reports are: PKCS7 with ORI callback set or AuthEnvelopedData with AES-GCM (–enable-pkcs7), ECDSA […]

Read MoreMore Tag

Difference between TLS Session ID and Tickets

TLS session resumption reuses previously negotiated keying material to shorten handshakes and reduce CPU and network overhead. Resumption saves latency and power on constrained devices by avoiding a full handshake when a safe cached session is available.—–Understanding Session IDs and Tickets Session IDs are a server-issued identifier used by TLS ? 1.2 where the server […]

Read MoreMore Tag

How to Leverage FIPS to Meet Common Criteria Requirements

Does your project require meeting Common Criteria standards? Using wolfSSL’s FIPS-validated module (or FIPS-ready which is tailored towards FIPS requirements) helps a lot with meeting CC (Common Criteria) because it gives strong, reusable evidence for the crypto portion through independent validation of crypto algorithms and validation evidence with ACVP workflows. Having the ACVP tests and […]

Read MoreMore Tag

Stopping Ransomware at the Device Level

Ransomware now targets medical devices, not just IT systems. Once malicious code runs on a device, it can disrupt patient care. The best defense is preventing execution. wolfSSL blocks ransomware before it runs: wolfBoot – Prevents unauthorized firmware from executing at startup wolfCrypt – Encrypts storage and secures firmware updates to prevent tampering wolfSentry – […]

Read MoreMore Tag

FIPS 140-3 Encryption for Connected Medical Devices

Medical devices need encryption, but government and healthcare buyers often require FIPS 140-3 validated cryptography to meet compliance standards. wolfCrypt FIPS 140-3 provides validated encryption for embedded medical devices with lower memory and processing requirements than standard crypto libraries. It protects stored data and data in transit. wolfSSL FIPS extends this validation to TLS connections […]

Read MoreMore Tag

Why Secure Boot Is Now an FDA Expectation

The FDA now expects medical devices to use a secure boot. Without it, devices can run unauthorized firmware, including malware or compromised code from supply chain attacks. wolfBoot is a secure bootloader for embedded medical devices. It uses wolfCrypt to verify firmware signatures before allowing code to run. Only authenticated firmware executes. For additional security: […]

Read MoreMore Tag

Securing Medical Devices From Device to Cloud

Medical devices send patient data from bedside monitors and wearables to cloud systems. That data needs protection at every step. wolfSSL secures the full path: wolfSSL/wolfCrypt – Encrypted communication ((D)TLS 1.3) between devices and servers wolfMQTT – Secure messaging for device-to-cloud data transfer wolfSSH – Encrypted remote access for maintenance and diagnostics wolfTPM – Hardware […]

Read MoreMore Tag

No Medical Safety Without Security

Connected medical devices create new risks. A compromised device can expose patient data, fail during treatment, or be manipulated to cause harm. wolfSSL provides security tools built for medical device constraints: wolfCrypt – Lightweight encryption to protect data and device functions wolfEntropy – NIST-compliant random number generation for strong cryptographic keys wolfSentry – Firewall that […]

Read MoreMore Tag

Posts navigation

1 2 3 4 … 233 234 235

Weekly updates

Archives