Comparison Overview

Pacific Research Institute

VS

The Perryman Group

Pacific Research Institute

P.O. Box 60485, Pasadena, California, 91116, US
Last Update: 2025-12-02

The Pacific Research Institute promotes the principles of individual freedom and personal responsibility. PRI believes these principles are best encouraged through policies that emphasize a free economy, private initiative, and limited government. By focusing on public policy issues such as education, the environment, health care, entrepreneurship, regulation, and technology, the Institute strives to foster a better understanding of the principles of a free society among leaders in government, academia, the media, and the business community.

NAICS: 541
NAICS Definition:
Employees: 34
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

The Perryman Group

510 North Valley Mills Dr., Suite 300, Waco, TX, US, 76710
Last Update: 2025-12-02
Between 750 and 799

The Perryman Group is a team of highly skilled and focused analysts who stand ready to tackle any economic information task. Our in-house professionals bring expertise in finance, statistics, economics, mathematics, real estate, database management, valuation, programming, systems analysis, engineering, technical communications, and marketing. Dr. Ray Perryman, President and CEO, has almost 40 years of experience in developing systems, analyzing complex problems, and communicating effectively.

NAICS: 54172
NAICS Definition: Research and Development in the Social Sciences and Humanities
Employees: 18
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/pacific-research-institute.jpeg
Pacific Research Institute
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/the-perryman-group.jpeg
The Perryman Group
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
Pacific Research Institute
100%
Compliance Rate
0/4 Standards Verified
The Perryman Group
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Think Tanks Industry Average (This Year)

No incidents recorded for Pacific Research Institute in 2025.

Incidents vs Think Tanks Industry Average (This Year)

No incidents recorded for The Perryman Group in 2025.

Incident History — Pacific Research Institute (X = Date, Y = Severity)

Pacific Research Institute cyber incidents detection timeline including parent company and subsidiaries

Incident History — The Perryman Group (X = Date, Y = Severity)

The Perryman Group cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pacific-research-institute.jpeg
Pacific Research Institute
Incidents

No Incident

https://images.rankiteo.com/companyimages/the-perryman-group.jpeg
The Perryman Group
Incidents

No Incident

FAQ

Both Pacific Research Institute company and The Perryman Group company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, The Perryman Group company has disclosed a higher number of cyber incidents compared to Pacific Research Institute company.

In the current year, The Perryman Group company and Pacific Research Institute company have not reported any cyber incidents.

Neither The Perryman Group company nor Pacific Research Institute company has reported experiencing a ransomware attack publicly.

Neither The Perryman Group company nor Pacific Research Institute company has reported experiencing a data breach publicly.

Neither The Perryman Group company nor Pacific Research Institute company has reported experiencing targeted cyberattacks publicly.

Neither Pacific Research Institute company nor The Perryman Group company has reported experiencing or disclosing vulnerabilities publicly.

Neither Pacific Research Institute nor The Perryman Group holds any compliance certifications.

Neither company holds any compliance certifications.

Pacific Research Institute company has more subsidiaries worldwide compared to The Perryman Group company.

Pacific Research Institute company employs more people globally than The Perryman Group company, reflecting its scale as a Think Tanks.

Neither Pacific Research Institute nor The Perryman Group holds SOC 2 Type 1 certification.

Neither Pacific Research Institute nor The Perryman Group holds SOC 2 Type 2 certification.

Neither Pacific Research Institute nor The Perryman Group holds ISO 27001 certification.

Neither Pacific Research Institute nor The Perryman Group holds PCI DSS certification.

Neither Pacific Research Institute nor The Perryman Group holds HIPAA certification.

Neither Pacific Research Institute nor The Perryman Group holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string. As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.

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

Monkeytype is a minimalistic and customizable typing test. In 25.49.0 and earlier, there is improper handling of user input which allows an attacker to execute malicious javascript on anyone viewing a malicious quote submission. quote.text and quote.source are user input, and they're inserted straight into the DOM. If they contain HTML tags, they will be rendered (after some escaping using quotes and textarea tags).

Risk Information
cvss4
Base: 7.1
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/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

SysReptor is a fully customizable pentest reporting platform. Prior to 2025.102, there is a Stored Cross-Site Scripting (XSS) vulnerability allows authenticated users to execute malicious JavaScript in the context of other logged-in users by uploading malicious JavaScript files in the web UI. This vulnerability is fixed in 2025.102.

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

Taiko Alethia is an Ethereum-equivalent, permissionless, based rollup designed to scale Ethereum without compromising its fundamental properties. In 2.3.1 and earlier, TaikoInbox._verifyBatches (packages/protocol/contracts/layer1/based/TaikoInbox.sol:627-678) advanced the local tid to whatever transition matched the current blockHash before knowing whether that batch would actually be verified. When the loop later broke (e.g., cooldown window not yet passed or transition invalidated), the function still wrote that newer tid into batches[lastVerifiedBatchId].verifiedTransitionId after decrementing batchId. Result: the last verified batch could end up pointing at a transition index from the next batch (often zeroed), corrupting the verified chain pointer.

Risk Information
cvss4
Base: 8.0
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U/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

A flaw has been found in youlaitech youlai-mall 1.0.0/2.0.0. Affected is the function getById/updateAddress/deleteAddress of the file /mall-ums/app-api/v1/addresses/. Executing manipulation can lead to improper control of dynamically-identified variables. The attack can be executed remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Risk Information
cvss2
Base: 6.5
Severity: LOW
AV:N/AC:L/Au:S/C:P/I:P/A:P
cvss3
Base: 6.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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