Comparison Overview

AIM Companies

VS

Sorting Robotics

AIM Companies

3804 Nona St, North Little Rock, Arkansas, US, 72118
Last Update: 2025-11-21
Between 750 and 799

For more than 40 years AIM, a Tavoron company, has been distributing high quality Air, Gas, and Liquid Handling and Treatment Equipment. We specialize in innovative engineering solutions for our customer’s problems across a wide range of industries. AIM has modern facilities in our four strategic locations and our full line of products is the finest available. We are committed to providing quality service to you, now and for years to come. Our mission is to provide sales and service of equipment used for the treatment and moving of air, liquids, and gases. Our success depends on meeting or exceeding our customers' needs and expectations.

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

Sorting Robotics

6837 Hayvenhurst Ave, Los Angeles, California, 91406, US
Last Update: 2025-11-25

Sorting Robotics is the premier technology company currently innovating the cannabis industry. Specializing in robotics, computer vision, and A.I. we provide cannabis brands and processors valuable solutions; reducing costs and enhancing profitability. Whether you’re a cannabis brand, grower, or co-packer, let us help you increase your production efficiencies and reduce labor costs. We bring extensive experience and professionalism to solve your toughest bottlenecks and customize our support to your company’s individual needs and concerns.

NAICS: None
NAICS Definition:
Employees: 22
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/aimcompanies.jpeg
AIM Companies
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/sortingrobotics.jpeg
Sorting Robotics
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
AIM Companies
100%
Compliance Rate
0/4 Standards Verified
Sorting Robotics
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for AIM Companies in 2025.

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Sorting Robotics in 2025.

Incident History — AIM Companies (X = Date, Y = Severity)

AIM Companies cyber incidents detection timeline including parent company and subsidiaries

Incident History — Sorting Robotics (X = Date, Y = Severity)

Sorting Robotics cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/aimcompanies.jpeg
AIM Companies
Incidents

No Incident

https://images.rankiteo.com/companyimages/sortingrobotics.jpeg
Sorting Robotics
Incidents

No Incident

FAQ

AIM Companies company demonstrates a stronger AI Cybersecurity Score compared to Sorting Robotics company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Sorting Robotics company has disclosed a higher number of cyber incidents compared to AIM Companies company.

In the current year, Sorting Robotics company and AIM Companies company have not reported any cyber incidents.

Neither Sorting Robotics company nor AIM Companies company has reported experiencing a ransomware attack publicly.

Neither Sorting Robotics company nor AIM Companies company has reported experiencing a data breach publicly.

Neither Sorting Robotics company nor AIM Companies company has reported experiencing targeted cyberattacks publicly.

Neither AIM Companies company nor Sorting Robotics company has reported experiencing or disclosing vulnerabilities publicly.

Neither AIM Companies nor Sorting Robotics holds any compliance certifications.

Neither company holds any compliance certifications.

Neither AIM Companies company nor Sorting Robotics company has publicly disclosed detailed information about the number of their subsidiaries.

AIM Companies company employs more people globally than Sorting Robotics company, reflecting its scale as a Industrial Automation.

Neither AIM Companies nor Sorting Robotics holds SOC 2 Type 1 certification.

Neither AIM Companies nor Sorting Robotics holds SOC 2 Type 2 certification.

Neither AIM Companies nor Sorting Robotics holds ISO 27001 certification.

Neither AIM Companies nor Sorting Robotics holds PCI DSS certification.

Neither AIM Companies nor Sorting Robotics holds HIPAA certification.

Neither AIM Companies nor Sorting Robotics 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