Comparison Overview

The Fred D. Pfening Company

VS

GRC ENGINEERING LIMITED

The Fred D. Pfening Company

1075 W 5TH AVE, COLUMBUS, Ohio, 43212, US
Last Update: 2025-11-27
Between 750 and 799

We are the Fred D. Pfening Company. A fourth-generation and family-owned business. We have been proudly serving the baking and food industries since 1919, with equipment and systems to support our customers’ growth and success. Always adhering to our Customer First philosophy has made Pfening a valued partner and is why many of our customers have been with us for several decades. We actively listen to fully understand their vision and plan. By seeing the big picture, we can deliver a comprehensive, customized solution for every budget and need – large and small.

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

GRC ENGINEERING LIMITED

Plumbe Street , Burnley , Lancashire, BB11 3AB, GB
Last Update: 2025-11-27

Established in 1990, we provide sub contract engineering services to a wide range of industries. With constant investment in our people, equipment and facilities, the services we offer are wide ranging and can be split into the following 2 areas of business; Mechanical Site Services  Machinery and plant installations  Machinery and plant refurbishments  Machinery and plant improvements and modifications  Machinery and plant relocations  Contract engineering maintenance  Engineering maintenance shift cover  Pipework system installation  Confined space engineering  Ducting and HVAC system installations  On-site welding and fabrications  Lifting equipment inspection, testing and certificating Manufacturing Engineering Services  3D Design Software – Autodesk Inventor  CNC steel profiling  CNC steel forming  Large quantity of traditional steel working machinery  Highly skilled workforce – sheet metal workers, steel fabricators, coded welders  1 off prototypes / large scale batch work  Small components / 10t assemblies

NAICS: None
NAICS Definition:
Employees: 16
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/the-fred-d.-pfening-company.jpeg
The Fred D. Pfening Company
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/grc-engineering-limited.jpeg
GRC ENGINEERING LIMITED
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
The Fred D. Pfening Company
100%
Compliance Rate
0/4 Standards Verified
GRC ENGINEERING LIMITED
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Mechanical Or Industrial Engineering Industry Average (This Year)

No incidents recorded for The Fred D. Pfening Company in 2025.

Incidents vs Mechanical Or Industrial Engineering Industry Average (This Year)

No incidents recorded for GRC ENGINEERING LIMITED in 2025.

Incident History — The Fred D. Pfening Company (X = Date, Y = Severity)

The Fred D. Pfening Company cyber incidents detection timeline including parent company and subsidiaries

Incident History — GRC ENGINEERING LIMITED (X = Date, Y = Severity)

GRC ENGINEERING LIMITED cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/the-fred-d.-pfening-company.jpeg
The Fred D. Pfening Company
Incidents

No Incident

https://images.rankiteo.com/companyimages/grc-engineering-limited.jpeg
GRC ENGINEERING LIMITED
Incidents

No Incident

FAQ

The Fred D. Pfening Company company demonstrates a stronger AI Cybersecurity Score compared to GRC ENGINEERING LIMITED company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, GRC ENGINEERING LIMITED company has disclosed a higher number of cyber incidents compared to The Fred D. Pfening Company company.

In the current year, GRC ENGINEERING LIMITED company and The Fred D. Pfening Company company have not reported any cyber incidents.

Neither GRC ENGINEERING LIMITED company nor The Fred D. Pfening Company company has reported experiencing a ransomware attack publicly.

Neither GRC ENGINEERING LIMITED company nor The Fred D. Pfening Company company has reported experiencing a data breach publicly.

Neither GRC ENGINEERING LIMITED company nor The Fred D. Pfening Company company has reported experiencing targeted cyberattacks publicly.

Neither The Fred D. Pfening Company company nor GRC ENGINEERING LIMITED company has reported experiencing or disclosing vulnerabilities publicly.

Neither The Fred D. Pfening Company nor GRC ENGINEERING LIMITED holds any compliance certifications.

Neither company holds any compliance certifications.

Neither The Fred D. Pfening Company company nor GRC ENGINEERING LIMITED company has publicly disclosed detailed information about the number of their subsidiaries.

The Fred D. Pfening Company company employs more people globally than GRC ENGINEERING LIMITED company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither The Fred D. Pfening Company nor GRC ENGINEERING LIMITED holds SOC 2 Type 1 certification.

Neither The Fred D. Pfening Company nor GRC ENGINEERING LIMITED holds SOC 2 Type 2 certification.

Neither The Fred D. Pfening Company nor GRC ENGINEERING LIMITED holds ISO 27001 certification.

Neither The Fred D. Pfening Company nor GRC ENGINEERING LIMITED holds PCI DSS certification.

Neither The Fred D. Pfening Company nor GRC ENGINEERING LIMITED holds HIPAA certification.

Neither The Fred D. Pfening Company nor GRC ENGINEERING LIMITED 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