All Posts Next

Java4Shell exploitation attempts have begun against CVE-2026-114938, a Java memory corruption bug that can allow unauthenticated remote code execution in widely used enterprise applications.

SecurityWeek reported the story on November 19, drawing on disclosures from Calif, the researcher who found and reported the flaw, and on telemetry from GreyNoise, WatchTowr, Cloudflare's Cloudforce One, Previdian, Cisco, VulnCheck and Immersive. The window between disclosure, exploitation and complete vendor fixes is exactly where compliance obligations and real-world risk collide, and this vulnerability sits squarely in that window.

Key Takeaways

  • CVE-2026-114938, nicknamed Java4Shell, is a memory corruption bug in how OpenJDK 17.0.6 and newer handle Base64 data. Exploitation requires an x86-64 processor supporting AVX-512 VBMI, a feature on newer Intel and AMD CPUs. ARM-based systems are not affected.
  • Calif disclosed the bug on November 17, the same day Oracle and the OpenJDK project released patches, and demonstrated unauthenticated remote code execution against the default configurations of Jira, Confluence, Jenkins, Keycloak and other enterprise applications. No single exploit works against all of them; each needs a tailored attack chain.
  • As of early November 19, GreyNoise had recorded over 150 requests matching the shape of a Java4Shell attack from five IP addresses, with no successful intrusions observed on its sensors. Previdian's sensors logged nine exploitation attempts from six IPs on November 18 and 19.
  • Vendor impact is broad and fixes are uneven. Cisco has confirmed more than a dozen affected products with no fixes or workarounds yet. Red Hat rated the issue Critical for RHEL 8, 9 and 10. Atlassian recommends disabling AVX-512 support as a workaround for several Data Center products until patches arrive.
  • Full remote code execution exploit code already exists in restricted circulation: VulnCheck has made a full RCE exploit available to its customers, and Immersive's Kevin Breen has reported developing a working exploit. The public PoC from Calif only triggers the memory corruption.

What Happened: The Facts in Detail

Disclosure and coordinated patching on November 17

Calif disclosed the vulnerability on November 17. On the same day, Oracle and the OpenJDK project released patches. The flaw is tracked as CVE-2026-114938 and has been nicknamed Java4Shell. It is a memory corruption bug in the way OpenJDK 17.0.6 and newer handle Base64 data, which matters because Base64 encoding is used constantly in web applications, authentication flows and API traffic.

The hardware dependency is the most unusual feature of this bug. Exploitation requires an x86-64 processor that supports AVX-512 VBMI, an advanced vector instruction set found in newer Intel and AMD CPUs. Systems running on ARM processors are not affected.

Proof of concept and exploit availability

Calif demonstrated unauthenticated remote code execution against the default configurations of Jira, Confluence, Jenkins, Keycloak and other enterprise applications. Two important qualifications accompany that claim. First, no single exploit works against all of these targets; each application requires a tailored attack chain. Second, the proof of concept Calif released publicly only triggers the memory corruption. It does not achieve full code execution on its own.

The restricted-circulation picture is more concerning. VulnCheck has made a full remote code execution exploit available to its customers. Kevin Breen of Immersive has reported developing a working exploit. Cisco's product security team says it is aware of proof-of-concept exploit code but has no knowledge of malicious use. That statement was accurate when made; the observed attack activity described below shows intent, even if confirmed compromise has not been observed.

Early attack activity: probing, spraying and concealing

As of early November 19, GreyNoise had recorded over 150 requests matching the shape of a Java4Shell attack, coming from five IP addresses. GreyNoise has not seen any successful intrusions on its sensors. Previdian's sensors logged nine exploitation attempts from six IPs on November 18 and 19, though the firm cautioned that its sensor data cannot confirm whether any targets were compromised.

WatchTowr is also seeing activity. Jake Knott, head of threat intelligence at WatchTowr, said attackers are spraying the internet and hitting the company's global honeypot network with requests decorated in "java4shell-recon" user agents, alongside blind exploitation attempts using correctly shaped requests. Knott added that what has been seen so far is not particularly functional or scary yet, but it shows a clear signal that attackers want to use the vulnerability, and that over the coming days attackers are expected to iterate product by product to refine and build more reliable target-specific exploits. That refinement, in his words, is where real exploitation starts to happen.

Cloudflare's Cloudforce One team has observed attackers concealing their tools. In one case, an IP address probed a target using a user agent that clearly referenced Java4Shell, then returned roughly 17 hours later with the exploit trigger while impersonating the Chrome browser. On November 18, Cloudforce One also saw an IP address being used for both Artex and Java4Shell activity for the first time. Artex is an open source AI penetration testing framework that threat actors have been abusing to automate intrusions.

Vendor advisories: confirmed impact, uneven fixes

The vendor response is broad but incomplete, and this is where operational risk concentrates right now.

Cisco has confirmed that more than a dozen of its products are affected, including Catalyst Center, Secure Network Analytics, Secure Workload, Smart Software Manager On-Prem, Splunk AppDynamics On-Premises Virtual Appliance, and Intersight Virtual Appliance. Cisco has yet to release fixes and says there are no workarounds. It is still investigating whether IOS XE and UCS Central are impacted.

Siemens says three of its Industrial Edge Management products are affected. The company is working on patches and, in the meantime, recommends taking these instances offline.

Elastic reports that every Elasticsearch release from 7.17.3 onward is affected. Attackers need valid credentials with read permissions or higher to achieve remote code execution, but they can trigger a denial-of-service condition without authentication. Logstash 8.6.2 and later are also affected, although exploitation requires a specific configuration and can only cause a crash. Elastic plans to address the issue in upcoming releases and has already deployed a hotfix for Elastic Cloud Serverless and a configuration change for Elastic Cloud Hosted. Only a small share of Elastic Cloud Hosted deployments run on vulnerable CPUs.

Red Hat has rated the issue Critical, saying that RHEL 8, 9 and 10 are affected, along with its own builds of OpenJDK 17, 21 and 25. Red Hat stated that no special configuration or non-default features are required: the accelerated code path is selected automatically whenever the JVM runs on a CPU reporting AVX-512 VBMI support, so affected systems are vulnerable out of the box. Patches are being fast-tracked.

The Keycloak team warned that its 26.8.2-1 and 26.8.2-2 container images bundled a vulnerable OpenJDK 21 build. On November 19 it announced updated images containing a patched Java runtime, including the 26.8.2-3 release.

Atlassian says it is working to address the issue in its cloud products and that cloud customers do not need to take any action. For Data Center products, until patches become available, Atlassian recommends disabling AVX-512 support as a workaround for the latest versions of Bamboo, Bitbucket, Confluence, Crowd, Jira and Jira Service Management Data Center in standard installations.

The Jenkins project says controllers are only at risk if they run a vulnerable Java 17, 21 or 25 release on a CPU that supports AVX-512 VBMI. It advises users to update to the November Java releases and restart Jenkins. Workarounds are also available.

Among Java distributors, Amazon, Microsoft and Azul have released patched builds of their OpenJDK distributions.

How Java4Shell Exploitation Attempts Work, and Why It Matters

Strip away the jargon and the mechanics are simple to explain. Modern Java runtimes use accelerated processor instructions to speed up common operations, including decoding Base64 data. Java4Shell is a memory corruption bug in that accelerated code path. If an attacker can get a specially crafted Base64 payload into a vulnerable application, the corrupted memory can be steered into running the attacker's code. Remote code execution is the most severe class of web application flaw because it removes every layer between the attacker and the system: no stolen password, no misconfigured firewall, no phishing email required.

The hardware condition deserves careful attention from business leaders, because it changes how you should read your own inventory. The vulnerable code path activates automatically on x86-64 CPUs that report AVX-512 VBMI support. Red Hat's advisory is explicit that no special configuration is needed and affected systems are vulnerable out of the box. In practical terms, the question is not whether your Java applications are configured dangerously. The question is what processor your servers and container hosts run, and which Java runtime version sits underneath the applications you may not even think of as "Java," such as build servers, identity platforms and monitoring appliances.

The second structural point is the gap between the applications demonstrated and the exploits available. Calif showed unauthenticated remote code execution against default configurations of Jira, Confluence, Jenkins, Keycloak and others, but each target needs its own tailored attack chain. This means exploitation will not arrive as one universal weapon. It will arrive product by product, as WatchTowr's Jake Knott predicted, with attackers iterating against each application to build reliable, target-specific exploits. For defenders, the practical consequence is a delay between disclosure and fully weaponized attacks, and that delay is the window in which patching is cheapest and most effective. The observed behavior, from "java4shell-recon" user agents to Chrome impersonation roughly 17 hours after initial probing, shows attackers using that window to map the target population.

Finally, note what the Artex connection implies. An open source AI penetration testing framework being repurposed for automated intrusion work, observed alongside Java4Shell activity from the same IP address, suggests that the labor-intensive work of tailoring exploits per product may be accelerated by automation. Organizations should not assume the product-by-product refinement period will stretch out comfortably.

What the Evidence Does and Does Not Show

Precision about the limits of the current evidence matters as much as the facts themselves, because overreaction and complacency are both expensive.

What the evidence shows: attacker intent and early reconnaissance. GreyNoise recorded over 150 requests matching the shape of a Java4Shell attack from five IP addresses as of early November 19, and WatchTowr's honeypots are receiving both recon-tagged requests and blind exploitation attempts.

What the evidence does not show: confirmed compromise. GreyNoise has not seen any successful intrusions on its sensors. Previdian explicitly cautioned that its sensor data cannot confirm whether any targets were compromised. Cisco states it has no knowledge of malicious use, only awareness of proof-of-concept code. No source cited here reports a confirmed breach attributable to CVE-2026-114938 at the time of writing.

There are also open questions that the sources do not resolve. Cisco is still investigating whether IOS XE and UCS Central are impacted, so the affected product list should be treated as a floor, not a ceiling. Cisco has released no fixes and says there are no workarounds, which leaves affected Cisco customers with exposure they cannot currently remediate by configuration. Elastic's fixes are planned for upcoming releases rather than available today for self-hosted Elasticsearch and Logstash. Atlassian's Data Center workaround of disabling AVX-512 support applies to standard installations of the latest versions; organizations running other versions or non-standard installations do not have stated guidance in these advisories and should verify their position directly with the vendor.

Finally, the full remote code execution exploit from VulnCheck is available only to its customers, and Immersive's working exploit has been reported but its circulation is not described in the sources. The public proof of concept triggers only the memory corruption. How quickly tailored, reliable exploits spread beyond restricted circles is the single most consequential unknown in this story, and it is the variable that will determine whether the current probing activity matures into the real exploitation WatchTowr expects in the coming days.

Compliance and Risk Implications for Regulated Organizations

Java4Shell is not just a technical problem. For organizations operating under regulatory obligations, it is a test of whether the controls they claim on paper actually exist in practice. The vulnerability, tracked as CVE-2026-114938, affects OpenJDK 17.0.6 and newer through a memory corruption bug in Base64 handling, and Red Hat has confirmed that no special configuration is required: the vulnerable accelerated code path is selected automatically whenever the Java virtual machine runs on a CPU reporting AVX-512 VBMI support. In other words, affected systems are vulnerable out of the box, and "we didn't configure anything unusual" is not a defense.

Defense contractors working with covered defense information face a specific and immediate set of duties. DFARS 252.204-7012 requires reporting a cyber incident affecting covered defense information to DoD within 72 hours of discovery via dibnet.dod.mil, using a DoD-approved medium assurance certificate that must be obtained in advance. If an attacker reaches a system holding controlled unclassified information through this flaw, that clock starts at discovery, not at confirmation. NIST SP 800-171's Incident Response family also requires an operational incident handling capability, with incidents tracked, documented, and reported. A timely external report with no internal process still fails the requirement. The CMMC Program rule, 32 CFR Part 170, took effect December 16, 2024, and while the DoD CIO suspended the November 10, 2026 Phase II deadline on July 13, 2026, with Phase I self-assessments remaining in force, the underlying safeguarding expectations have not paused. A system running a vulnerable Java runtime inside a CUI boundary is a finding waiting to be written.

Healthcare organizations face parallel exposure. The HIPAA Security Rule at 45 CFR Part 164 requires a Risk Analysis under 45 CFR 164.308(a)(1)(ii)(A), and an unpatched, actively probed remote code execution flaw in an internet-facing application is exactly the kind of risk that analysis must capture. If exploitation leads to a breach of protected health information, the Breach Notification Rule at 45 CFR 164.404, 164.406, and 164.408 governs notification duties. IBM's 2026 research puts the average healthcare breach cost at $6.64 million, and HHS OCR has shown through recent enforcement actions, including an April 2026 ransomware sweep totaling $1.165 million, that unpatched and misconfigured systems draw penalties.

There is also an evidentiary dimension. Auditors and assessors under CMMC, HIPAA, PCI DSS, SOC 2, and NIST SP 800-171 do not accept "we patched eventually." They want to see that vulnerability management operated as a process: detection, prioritization, patching, verification, and documentation. The same record, showing risk-based triage within days and a documented workaround in the interim, is a strong one.

Finally, note what the evidence does not show. As of early November 19, GreyNoise had recorded over 150 requests matching the shape of a Java4Shell attack from five IP addresses, with no successful intrusions on its sensors, and Previdian's sensors logged nine exploitation attempts from six IPs on November 18 and 19 without being able to confirm any compromise. WatchTowr's threat intelligence head Jake Knott expects attackers to iterate product by product before real exploitation happens. That gap between probing and reliable exploitation is the window regulated organizations have. It will not stay open.

What This Means for Regulated Industries

Defense Contractors

Start with your CUI boundary. Java4Shell's confirmed impact list reads like a defense industrial base inventory: Atlassian's Jira, Confluence, Bamboo, Bitbucket, Crowd, and Jira Service Management Data Center, Jenkins, Keycloak, and Cisco products including Catalyst Center, Secure Network Analytics, Secure Workload, Smart Software Manager On-Prem, Splunk AppDynamics On-Premises Virtual Appliance, and Intersight Virtual Appliance. If any of these sit inside or adjacent to your CUI enclave, treat them as priority one. Atlassian recommends disabling AVX-512 support as a workaround for the latest versions of its Data Center products in standard installations until patches arrive. The Jenkins project advises updating to the November Java releases and restarting controllers. Cisco has yet to release fixes and says there are no workarounds, which means compensating controls and isolation are the only lever for those products today. Also verify your DFARS 252.204-7012 reporting certificate is in hand now, not after an incident, and remember that affected system images and monitoring data must be preserved for at least 90 days after a reported incident.

Healthcare

Elastic has confirmed that every Elasticsearch release from 7.17.3 onward is affected. Attackers need valid credentials with read permissions or higher to achieve remote code execution there, but they can trigger a denial-of-service condition without authentication, and a crashed clinical search layer is itself a patient safety and operations problem. Elastic has deployed a hotfix for Elastic Cloud Serverless and a configuration change for Elastic Cloud Hosted, and plans fixes in upcoming releases, so check which of those deployment models you run. Logstash 8.6.2 and later are also affected, though exploitation there requires a specific configuration and can only cause a crash. Beyond Elasticsearch, review any Java-based identity and access infrastructure: Keycloak's team warned that its 26.8.2-1 and 26.8.2-2 container images bundled a vulnerable OpenJDK 21 build, and released updated images including 26.8.2-3 on November 19.

Legal

Law firms and legal technology platforms hold client confidences that carry contractual and, in many matters, regulatory weight. The practical exposure here is the same enterprise collaboration and CI/CD stack: Confluence for knowledge management, Jira for matter workflow, Jenkins for build systems supporting e-discovery and legal engineering tools. Calif demonstrated unauthenticated remote code execution against the default configurations of Jira, Confluence, Jenkins, Keycloak and other enterprise applications, though no single exploit works against all of them and each needs a tailored attack chain. Assume the tailored chains are coming; WatchTowr expects exactly that. Inventory which of these products you run, on which hardware, and apply Atlassian's AVX-512 workaround where patches are not yet available.

Financial Services

Financial institutions run dense Java estates: application servers, message queues, identity providers, and internal developer platforms. PCI DSS v4.0.1 covers 12 control areas across cardholder data environments, and timely patching of actively exploited vulnerabilities in systems touching cardholder data is squarely within that scope. The Cisco product list deserves particular attention from network and security teams, since Catalyst Center, Secure Network Analytics, and Secure Workload are often the very tools providing visibility and segmentation, and Cisco has confirmed more than a dozen affected products with no fixes and no workarounds yet. Also note that Red Hat has rated the issue Critical across RHEL 8, 9, and 10 and its own builds of OpenJDK 17, 21, and 25, and is fast-tracking patches, so your Linux patch cadence matters as much as your application patch cadence.

An Action Plan for This Month

  1. Inventory your Java exposure. Identify every system running OpenJDK 17, 21, or 25, and every product on the confirmed affected lists from Cisco, Atlassian, Elastic, Siemens, and the Keycloak and Jenkins projects. Pay special attention to anything internet-facing.
  2. Check the hardware. Java4Shell exploitation requires an x86-64 processor supporting AVX-512 VBMI, found in newer Intel and AMD CPUs. ARM-based systems are not affected. A CPU inventory tells you which of your Java systems are actually exploitable, which is the difference between a critical and a moderate finding.
  3. Patch the Java runtime first where fixes exist. Amazon, Microsoft, and Azul have released patched builds of their OpenJDK distributions, and Oracle and the OpenJDK project released patches the day of disclosure. Update to the November Java releases and restart dependent applications, as the Jenkins project advises.
  4. Apply vendor workarounds where patches are not ready. For Atlassian Data Center products in standard installations, disable AVX-512 support as recommended. For Siemens' three affected Industrial Edge Management products, take instances offline as Siemens recommends. For Cisco products with no fixes and no workarounds, restrict network access and increase monitoring.
  5. Rebuild container images. If you use Keycloak, verify you are not running the 26.8.2-1 or 26.8.2-2 container images, which bundled a vulnerable OpenJDK 21 build. Move to 26.8.2-3 or later. Audit other images for bundled Java runtimes while you are at it.
  6. Tune detection for Java4Shell reconnaissance. WatchTowr has observed attackers spraying the internet with requests using "java4shell-recon" User-Agents alongside blind exploitation attempts. Cloudforce One observed an attacker returning roughly 17 hours after initial probing, impersonating the Chrome browser, and another IP used for both Artex and Java4Shell activity. Alert on these patterns and on anomalous User-Agent switches.
  7. Verify your incident reporting readiness. Defense contractors: confirm your DoD-approved medium assurance certificate for DFARS 252.204-7012 reporting is obtained and tested. All regulated organizations: confirm who declares an incident, who notifies regulators, and that the 72-hour and breach notification clocks are understood before they start.
  8. Assume compromise until verified. Because the flaw enables unauthenticated remote code execution on default configurations of widely deployed applications, review authentication logs, new account creation, and outbound traffic from affected systems for the period since November 17. Sensor data from threat firms cannot confirm whether any targets were compromised; only your own logs can.
  9. Document everything for the auditor. Record your triage decisions, workaround implementations, patch dates, and verification steps. This record is your evidence under NIST SP 800-171, HIPAA, PCI DSS, and SOC 2 that vulnerability management operated as a real process.
  10. Close the loop with a post-incident review of your patch pipeline.

How Petronella Technology Group, Inc. Helps

Petronella Technology Group, Inc. works with regulated businesses and defense contractors that cannot treat a vulnerability like this as an ordinary patch Tuesday. Our managed detection and response service provides 24/7 threat monitoring, AI-powered analytics, and human-led investigation, replacing the need for an in-house security operations center. The AI-augmented hybrid SOC runs ten-plus production AI agents on the company's private AI cluster, which matters here because defense industrial base and healthcare clients that cannot send CUI or PHI to a public-cloud SOC still need round-the-clock detection of the reconnaissance and exploitation attempts this story describes. Human analysts hold CMMC-RP credentials, a Digital Forensics Examiner is on staff, and every action is logged for CMMC and HIPAA audit. MDR reporting is designed to provide the evidence auditors need for HIPAA, CMMC, PCI DSS, SOC 2, and NIST 800-171 verification.

On the compliance side, our compliance services and vCISO practice map exposure like this to your framework obligations, rank gaps by priority, and produce remediation roadmaps written for the executive reader. For defense contractors, our CMMC readiness work includes an SSP covering all 110 NIST SP 800-171 controls, a live POA&M, and mock assessment using the Cyber AB CMMC Assessment Process, and every practitioner on the compliance team holds the CMMC-RP designation. The firm is a Cyber AB Registered Provider Organization, RPO #1449. Broader security architecture support is available through our cybersecurity services, and additional guidance lives in our Resources Library. For a related recent case of active exploitation against enterprise software, see our analysis of active exploitation attempts targeting WSO2 API Manager.

Related reading

Sources

Frequently Asked Questions

Is Java4Shell being actively exploited?

Exploitation attempts have begun, but there is no confirmed evidence of successful intrusions yet. As of early November 19, GreyNoise had recorded over 150 requests matching the shape of a Java4Shell attack from five IP addresses with no successful intrusions on its sensors, Previdian logged nine exploitation attempts from six IPs on November 18 and 19, and WatchTowr observed reconnaissance and blind exploitation attempts against its global honeypot network. Threat intelligence firms caution that sensor data cannot confirm whether any targets were compromised.

Which systems are vulnerable to CVE-2026-114938?

Systems running OpenJDK 17.0.6 and newer on x86-64 processors that support AVX-512 VBMI, a feature found in newer Intel and AMD CPUs. ARM-based systems are not affected. Confirmed affected products include more than a dozen Cisco products, three Siemens Industrial Edge Management products, every Elasticsearch release from 7.17.3 onward, Logstash 8.6.2 and later, RHEL 8, 9, and 10, Atlassian Data Center products, and Jenkins controllers running vulnerable Java releases on capable CPUs.

What should I do if a patch is not available for my product?

Apply the vendor's recommended workaround and compensate with isolation and monitoring. Atlassian recommends disabling AVX-512 support for the latest versions of its Data Center products in standard installations, and Siemens recommends taking affected Industrial Edge Management instances offline. Cisco has confirmed affected products but has released no fixes and says there are no workarounds, so for those, restricting network access and intensifying monitoring are the practical options until patches arrive.

Does Java4Shell affect cloud services?

It depends on the provider and the deployment model. Atlassian says it is working to address the issue in its cloud products and that cloud customers do not need to take any action. Elastic has already deployed a hotfix for Elastic Cloud Serverless and a configuration change for Elastic Cloud Hosted, noting that only a small share of Elastic Cloud Hosted deployments run on vulnerable CPUs. Self-hosted and Data Center deployments remain the customer's responsibility.

Why does the CPU requirement matter for compliance?

Because it lets you prioritize accurately. Red Hat noted that the accelerated code path is selected automatically whenever the JVM runs on a CPU reporting AVX-512 VBMI support, so affected systems are vulnerable out of the box, but systems on ARM or on CPUs without that feature are not exploitable through this flaw. Documenting which systems meet the hardware condition turns an enterprise-wide emergency into a targeted, defensible remediation effort, which is exactly the kind of risk-based decision an auditor under NIST SP 800-171 or HIPAA expects to see recorded.

How fast do I need to report an incident if exploitation is confirmed?

For defense contractors, DFARS 252.204-7012 requires reporting a cyber incident affecting covered defense information to DoD within 72 hours of discovery via dibnet.dod.mil, using a DoD-approved medium assurance certificate obtained in advance, and affected system images and monitoring data must be preserved for at least 90 days afterward. Healthcare organizations must follow the HIPAA Breach Notification Rule at 45 CFR 164.404, 164.406, and 164.408 if protected health information is involved. Other contractual and regulatory notification duties vary, so confirm your specific windows now.

If you need help assessing your exposure to Java4Shell or proving your response to an auditor, call Penny, our AI assistant, at 919-348-4912 to book a consultation, or reach Petronella Technology Group, Inc. through our contact form.

Free online course from the Petronella Technology Group, Inc. Training Academy

Unhackable and Compliant

Free crash course: 5 practical steps to protect your data and meet HIPAA, CMMC, PCI-DSS, and FTC Safeguards compliance standards.

Price: Free

Start the free course Cybercrime and Identity Theft Defense Mastery ($997)

Get the 2026 Cybersecurity Survival Guide

Free, practical, and specific to regulated environments. We will email it to you.

No spam. Unsubscribe anytime.

Need help implementing these strategies? Our cybersecurity experts can assess your environment and build a tailored plan. Prefer to write? Send us a message.
Call Penny 919-348-4912

About the Author

Craig Petronella, CEO and Founder of Petronella Technology Group
CEO, Founder & AI Architect, Petronella Technology Group

Craig Petronella founded Petronella Technology Group in 2002 and has spent 30+ years professionally at the intersection of cybersecurity, AI, compliance, and digital forensics. He holds the CMMC Registered Practitioner credential issued by the Cyber AB and leads Petronella as a Cyber AB Registered Provider Organization (RPO #1449). Craig is an NC Licensed Digital Forensics Examiner (License #604180-DFE) and completed MIT Professional Education programs in AI, Blockchain, and Cybersecurity. He also holds CompTIA Security+, CCNA, and Hyperledger certifications.

He is an Amazon #1 Best-Selling Author of 15+ books on cybersecurity and compliance, host of the Encrypted Ambition podcast (95+ episodes on Apple Podcasts, Spotify, and Amazon), and a cybersecurity keynote speaker with 200+ engagements at conferences, law firms, and corporate boardrooms. Craig serves as Contributing Editor for Cybersecurity at NC Triangle Attorney at Law Magazine and is a guest lecturer at NCCU School of Law. He serves as a digital forensics expert witness for law firms on matters involving cybercrime, cryptocurrency fraud, SIM-swap attacks, and data breaches.

Under his leadership, Petronella Technology Group has served hundreds of regulated SMB clients across NC and the southeast since 2002, earned a BBB A+ rating every year since 2003, and been featured as a cybersecurity authority on CBS, ABC, NBC, FOX, and WRAL. The company leverages SOC 2 Type II certified platforms and specializes in AI implementation, managed cybersecurity, CMMC/HIPAA/SOC 2 compliance, and digital forensics for businesses across the United States.

CMMC-RP NC Licensed DFE MIT Certified CompTIA Security+ Expert Witness 15+ Books
Related Service
Protect Your Business with Our Cybersecurity Services

Our proprietary 39-layer ZeroHack cybersecurity stack defends your organization 24/7.

Explore Cybersecurity Services
All Posts Next
Questions about this topic? Talk to our team. Call Penny 919-348-4912 Message us