Comparison Overview

March 4th, Inc. (formerly Little Pickle Press, Inc.)

VS

Pediment Publishing

March 4th, Inc. (formerly Little Pickle Press, Inc.)

3701 Sacramento Street #494, San Francisco, CA, 94118, US
Last Update: 2025-11-27
Between 750 and 799

March 4th, Inc. (M4) is dedicated to creating media and products that foster kindness in young people—and doing so in a manner congruent with that mission. M4 is creating a universe of content comprised of characters who come alive through digital, social, and print media, merchandise, and interactive engagement with formative minds. Striving to be the change it seeks in the world, M4 is proud to be a Certified B Corporation.

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

Pediment Publishing

1417 SE Rasmussen Blvd, Battle Ground, WA, 98604, US
Last Update: 2025-11-26
Between 750 and 799

Founded by a former newspaper publisher, we at Pediment are publishers of fine things like books, calendars and post cards, and developers of cool things like web sites and book apps who primarily work with newspapers, television stations and other organizations. Folks often ask, “what’s a pediment?” so you might be wondering that very thing. Let us explain. As Wikipedia puts it, a pediment is an element of classical, neoclassical and baroque architecture. See, we are big fans of art, especially architecture, and even bigger fans of history. So “pediment” is a great term to showcase a union of art and history. In fact, if you want to think of us as an “art and history” publisher, that’d be just fine! Publishers of art and history sounds pretty ambitious, especially for a small business like us, but we don’t have such lofty ambitions on our own. Really, our world-class clients—or partners, as we like to call them—are the reason we can aim for world-class projects (books, web sites and so on), and consistently deliver impeccable quality while adhering to the highest standard of customer support and service. In other words, our partners help us make great books, calendars and web sites, and we’re confident you’ll love them!

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 15
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/little-pickle-press.jpeg
March 4th, Inc. (formerly Little Pickle Press, Inc.)
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/pediment-publishing.jpeg
Pediment Publishing
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
March 4th, Inc. (formerly Little Pickle Press, Inc.)
100%
Compliance Rate
0/4 Standards Verified
Pediment Publishing
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for March 4th, Inc. (formerly Little Pickle Press, Inc.) in 2025.

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Pediment Publishing in 2025.

Incident History — March 4th, Inc. (formerly Little Pickle Press, Inc.) (X = Date, Y = Severity)

March 4th, Inc. (formerly Little Pickle Press, Inc.) cyber incidents detection timeline including parent company and subsidiaries

Incident History — Pediment Publishing (X = Date, Y = Severity)

Pediment Publishing cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/little-pickle-press.jpeg
March 4th, Inc. (formerly Little Pickle Press, Inc.)
Incidents

No Incident

https://images.rankiteo.com/companyimages/pediment-publishing.jpeg
Pediment Publishing
Incidents

No Incident

FAQ

Both March 4th, Inc. (formerly Little Pickle Press, Inc.) company and Pediment Publishing company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Pediment Publishing company has disclosed a higher number of cyber incidents compared to March 4th, Inc. (formerly Little Pickle Press, Inc.) company.

In the current year, Pediment Publishing company and March 4th, Inc. (formerly Little Pickle Press, Inc.) company have not reported any cyber incidents.

Neither Pediment Publishing company nor March 4th, Inc. (formerly Little Pickle Press, Inc.) company has reported experiencing a ransomware attack publicly.

Neither Pediment Publishing company nor March 4th, Inc. (formerly Little Pickle Press, Inc.) company has reported experiencing a data breach publicly.

Neither Pediment Publishing company nor March 4th, Inc. (formerly Little Pickle Press, Inc.) company has reported experiencing targeted cyberattacks publicly.

Neither March 4th, Inc. (formerly Little Pickle Press, Inc.) company nor Pediment Publishing company has reported experiencing or disclosing vulnerabilities publicly.

Neither March 4th, Inc. (formerly Little Pickle Press, Inc.) nor Pediment Publishing holds any compliance certifications.

Neither company holds any compliance certifications.

Neither March 4th, Inc. (formerly Little Pickle Press, Inc.) company nor Pediment Publishing company has publicly disclosed detailed information about the number of their subsidiaries.

Pediment Publishing company employs more people globally than March 4th, Inc. (formerly Little Pickle Press, Inc.) company, reflecting its scale as a Book and Periodical Publishing.

Neither March 4th, Inc. (formerly Little Pickle Press, Inc.) nor Pediment Publishing holds SOC 2 Type 1 certification.

Neither March 4th, Inc. (formerly Little Pickle Press, Inc.) nor Pediment Publishing holds SOC 2 Type 2 certification.

Neither March 4th, Inc. (formerly Little Pickle Press, Inc.) nor Pediment Publishing holds ISO 27001 certification.

Neither March 4th, Inc. (formerly Little Pickle Press, Inc.) nor Pediment Publishing holds PCI DSS certification.

Neither March 4th, Inc. (formerly Little Pickle Press, Inc.) nor Pediment Publishing holds HIPAA certification.

Neither March 4th, Inc. (formerly Little Pickle Press, Inc.) nor Pediment Publishing holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

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

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.