Comparison Overview

Carter Intralogistics

VS

Breezy Med

Carter Intralogistics

7118 Geoffrey Way, Frederick, MD, 21704, US
Last Update: 2025-11-21

Carter Intralogistics, formerly CCS (Carter Controls Systems), is a subsidiary of the Lummus Corporation. We started our journey in 1980 providing control systems and MDR conveyor to the postal industry. Over the years we have grown to become a trusted solutions provider and integration partner throughout the material handling world. Carter Intralogistics delivers warehouse automation products and solutions to industries such as: E-commerce, food and beverage, wine and spirits, and third-party logistics. Intralogistics is not just part of our name — it’s built into the foundation of our company. We provide expertise in a full range of automation solutions from order fulfillment and robotics, to software controls and MDR conveyor systems. We take pride in manufacturing our line of MDR conveyor, CarterRoll™, in one of our three U.S. based facilities. As a trusted integrator with established partnerships throughout the industry, we have a proven ability to deliver quality products and solutions with quick turnaround times and competitive prices. Fulfill the future with Carter Intralogistics.

NAICS: None
NAICS Definition: Others
Employees: 48
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Breezy Med

317 Commercial St NE, Suite 102, Albuquerque, New Mexico, US, 87102
Last Update: 2025-11-21
Between 750 and 799

Breezy Med delivers smart, science-backed automation for hospital infection prevention. Our flagship Breezy Blue system uses EPA-registered aerosolized hydrogen peroxide (aHP) to achieve whole-room disinfection with push-button simplicity—no manual labor, no missed spots, and no UV limitations. Designed for terminal cleaning and high-risk areas, Breezy Blue outperforms legacy UV systems in efficacy, usability, and cost—at a fraction of the price. Our Breezy Cloud platform gives infection preventionists, EVS leaders, and executives real-time data for compliance, tracking, and continuous improvement. Hospitals choose Breezy Med to reduce healthcare-associated infections (HAIs), protect patients and staff, and modernize disinfection with technology that works as hard as they do.

NAICS: None
NAICS Definition: Others
Employees: 14
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/carter-control-systems-inc-.jpeg
Carter Intralogistics
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/breezy-bwr.jpeg
Breezy Med
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Carter Intralogistics
100%
Compliance Rate
0/4 Standards Verified
Breezy Med
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Carter Intralogistics in 2025.

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Breezy Med in 2025.

Incident History — Carter Intralogistics (X = Date, Y = Severity)

Carter Intralogistics cyber incidents detection timeline including parent company and subsidiaries

Incident History — Breezy Med (X = Date, Y = Severity)

Breezy Med cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/carter-control-systems-inc-.jpeg
Carter Intralogistics
Incidents

No Incident

https://images.rankiteo.com/companyimages/breezy-bwr.jpeg
Breezy Med
Incidents

No Incident

FAQ

Carter Intralogistics company demonstrates a stronger AI Cybersecurity Score compared to Breezy Med company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Breezy Med company has disclosed a higher number of cyber incidents compared to Carter Intralogistics company.

In the current year, Breezy Med company and Carter Intralogistics company have not reported any cyber incidents.

Neither Breezy Med company nor Carter Intralogistics company has reported experiencing a ransomware attack publicly.

Neither Breezy Med company nor Carter Intralogistics company has reported experiencing a data breach publicly.

Neither Breezy Med company nor Carter Intralogistics company has reported experiencing targeted cyberattacks publicly.

Neither Carter Intralogistics company nor Breezy Med company has reported experiencing or disclosing vulnerabilities publicly.

Neither Carter Intralogistics nor Breezy Med holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Carter Intralogistics company nor Breezy Med company has publicly disclosed detailed information about the number of their subsidiaries.

Carter Intralogistics company employs more people globally than Breezy Med company, reflecting its scale as a Industrial Automation.

Neither Carter Intralogistics nor Breezy Med holds SOC 2 Type 1 certification.

Neither Carter Intralogistics nor Breezy Med holds SOC 2 Type 2 certification.

Neither Carter Intralogistics nor Breezy Med holds ISO 27001 certification.

Neither Carter Intralogistics nor Breezy Med holds PCI DSS certification.

Neither Carter Intralogistics nor Breezy Med holds HIPAA certification.

Neither Carter Intralogistics nor Breezy Med holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H