Comparison Overview

Smith Garson

VS

G²S Corporation

Smith Garson

1150 Connecticut Ave NW, Washington, District of Columbia, 20036, US
Last Update: 2025-12-13
Between 750 and 799

Established in 1981, Smith Garson (formerly Smith Dawson & Andrews) is a full-service government relations firm that works with public and private sector clients to develop and implement effective legislative and communications strategies to advance their public policy agendas and secure needed funding for projects in the public interest. Smith Garson's diverse team of professionals provides clients with a wide range of expertise in policy areas including transportation and infrastructure, environmental regulation, public finance, local government, housing and community development, public safety and security, higher education, health, and international trade. Smith Garson offers clients cost-effective personal service with a bipartisan approach, in-depth knowledge and a record of success. Smith Garson’s reputation for integrity, candor and hard work helps clients meet the challenges they face at home and in Washington. Our in-depth substantive knowledge combined with our creativity, hard work and reputation for integrity attracts new clients at the forefront of innovation and has earned us the trust of longstanding clients, some of whom have been with us for more than twenty-five years. We offer a wide range of services to a variety of organizations across many industry sectors. These include businesses, corporations, state and local governments, nonprofits and trade associations. We’re proud that clients think of us as an integral part of their business, capable of delivering the services they need when they need them.

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

G²S Corporation

25414 MESA CREST, SAN ANTONIO, Texas, 78254, US
Last Update: 2025-12-13
Between 750 and 799

MORE THAN AN AGENCY Founded in September 2009, Global Government Solutions (G²S Corporation) is a SBA certified 8(a), Small Disadvantaged Business (SDB) and a nation award winning government workforce management solution. G²S Corporation possesses both the flexibility and the capability required to effectively staff and maintain credentialed and qualified personnel to meet the diverse and complex tasks Government agencies face. We Also Maintain a DCAA-approved accounting system. The Government has trusted G²S Corporation with over $80M in federal contracts because of our focus on cutting edge consulting, solution management, and capabilities assessment. G²S gains and utilizes best practices through global engagement and partnerships worldwide to render very specific performance results within budget and on schedule.

NAICS: None
NAICS Definition:
Employees: 33
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/smith-dawson-&-andrews.jpeg
Smith Garson
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/g2s-corporation.jpeg
G²S Corporation
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
Smith Garson
100%
Compliance Rate
0/4 Standards Verified
G²S Corporation
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Relations Industry Average (This Year)

No incidents recorded for Smith Garson in 2025.

Incidents vs Government Relations Industry Average (This Year)

No incidents recorded for G²S Corporation in 2025.

Incident History — Smith Garson (X = Date, Y = Severity)

Smith Garson cyber incidents detection timeline including parent company and subsidiaries

Incident History — G²S Corporation (X = Date, Y = Severity)

G²S Corporation cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/smith-dawson-&-andrews.jpeg
Smith Garson
Incidents

No Incident

https://images.rankiteo.com/companyimages/g2s-corporation.jpeg
G²S Corporation
Incidents

No Incident

FAQ

G²S Corporation company demonstrates a stronger AI Cybersecurity Score compared to Smith Garson company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, G²S Corporation company has disclosed a higher number of cyber incidents compared to Smith Garson company.

In the current year, G²S Corporation company and Smith Garson company have not reported any cyber incidents.

Neither G²S Corporation company nor Smith Garson company has reported experiencing a ransomware attack publicly.

Neither G²S Corporation company nor Smith Garson company has reported experiencing a data breach publicly.

Neither G²S Corporation company nor Smith Garson company has reported experiencing targeted cyberattacks publicly.

Neither Smith Garson company nor G²S Corporation company has reported experiencing or disclosing vulnerabilities publicly.

Neither Smith Garson nor G²S Corporation holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Smith Garson company nor G²S Corporation company has publicly disclosed detailed information about the number of their subsidiaries.

G²S Corporation company employs more people globally than Smith Garson company, reflecting its scale as a Government Relations.

Neither Smith Garson nor G²S Corporation holds SOC 2 Type 1 certification.

Neither Smith Garson nor G²S Corporation holds SOC 2 Type 2 certification.

Neither Smith Garson nor G²S Corporation holds ISO 27001 certification.

Neither Smith Garson nor G²S Corporation holds PCI DSS certification.

Neither Smith Garson nor G²S Corporation holds HIPAA certification.

Neither Smith Garson nor G²S Corporation holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Zerobyte is a backup automation tool Zerobyte versions prior to 0.18.5 and 0.19.0 contain an authentication bypass vulnerability where authentication middleware is not properly applied to API endpoints. This results in certain API endpoints being accessible without valid session credentials. This is dangerous for those who have exposed Zerobyte to be used outside of their internal network. A fix has been applied in both version 0.19.0 and 0.18.5. If immediate upgrade is not possible, restrict network access to the Zerobyte instance to trusted networks only using firewall rules or network segmentation. This is only a temporary mitigation; upgrading is strongly recommended.

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

Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter framework. Starting in version 3.4.0 and prior to version 3.4.2, a Cross-Site Request Forgery (CSRF) vulnerability exists in the application's filter configuration. The CSRF protection mechanism was **explicitly disabled**, allowing the application to process state-changing requests (POST) without verifying a valid CSRF token. An unauthenticated remote attacker can exploit this by hosting a malicious web page. If a logged-in administrator visits this page, their browser is forced to send unauthorized requests to the application. A successful exploit allows the attacker to silently create a new Administrator account with full privileges, leading to a complete takeover of the system and loss of confidentiality, integrity, and availability. The vulnerability has been patched in version 3.4.2. The fix re-enables the CSRF filter in `app/Config/Filters.php` and resolves associated AJAX race conditions by adjusting token regeneration settings. As a workaround, administrators can manually re-enable the CSRF filter in `app/Config/Filters.php` by uncommenting the protection line. However, this is not recommended without applying the full patch, as it may cause functionality breakage in the Sales module due to token synchronization issues.

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

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Model Context Protocol (MCP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious MCP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered automatically without any user interaction besides opening the project in the IDE. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

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

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Language Server Protocol (LSP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious LSP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered when a user opens project file for which there is an LSP entry. A concerted effort by an attacker to seed a project settings file (`./zed/settings.json`) with malicious language server configurations could result in arbitrary code execution with the user's privileges if the user opens the project in Zed without reviewing the contents. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

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

Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10 relates to Storybook’s handling of environment variables defined in a `.env` file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the `storybook build` command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly) in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than `.env` files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible. Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, either prefix the variables with `STORYBOOK_` or use the `env` property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

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