Comparison Overview

WORKMED

VS

Take Control Initiative

WORKMED

Manuel Montt 427 , Santiago de Chile, Metropolitana, undefined, CL
Last Update: 2025-11-26
Between 750 and 799

¡Somos líderes en salud y bienestar para tus colaboradores! Con más de 13 años de experiencia, nos especializamos en Seleccionar 🔍, examinar 🩺 y capacitar 📚a candidatos aptos para tu empresa. Nuestros programas de calidad de vida y bienestar laboral garantizan un ambiente óptimo para el desarrollo de tus colaboradores. 💼 Somos los más rápidos del mercado, entregando resultados en solo 8 horas. 👉🏻Ofrecemos agenda abierta, Análisis de NO aptos, presencia en 12 regiones a lo largo de Chile y mucho más. ¡Conócenos! 🚀

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

Take Control Initiative

907 S Detroit Ave, Tulsa, Oklahoma, 74120, US
Last Update: 2025-11-26

Since 2010, TCI has worked to ensure individuals have the resources and information to decide if and when they want to become pregnant in an effort to honor and support their autonomy and safety. In coalition with a strong network of partners, TCI builds sustainable bridges between community and health centers. To create this reality, TCI promotes the following conditions for Tulsa: – Everyone has access to all birth control options and are supported in self-advocating for their patient rights – Health centers and community-based organizations are supported in implementing practices that affirm dignity, trust, and respect – Systemic barriers, including financial, transportation, language, and logistical barriers to health center access are removed

NAICS: 923
NAICS Definition:
Employees: 17
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/workmed-ltda.jpeg
WORKMED
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/take-control-initiative.jpeg
Take Control Initiative
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
WORKMED
100%
Compliance Rate
0/4 Standards Verified
Take Control Initiative
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Health and Human Services Industry Average (This Year)

No incidents recorded for WORKMED in 2025.

Incidents vs Health and Human Services Industry Average (This Year)

No incidents recorded for Take Control Initiative in 2025.

Incident History — WORKMED (X = Date, Y = Severity)

WORKMED cyber incidents detection timeline including parent company and subsidiaries

Incident History — Take Control Initiative (X = Date, Y = Severity)

Take Control Initiative cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/workmed-ltda.jpeg
WORKMED
Incidents

No Incident

https://images.rankiteo.com/companyimages/take-control-initiative.jpeg
Take Control Initiative
Incidents

No Incident

FAQ

WORKMED company demonstrates a stronger AI Cybersecurity Score compared to Take Control Initiative company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Take Control Initiative company has disclosed a higher number of cyber incidents compared to WORKMED company.

In the current year, Take Control Initiative company and WORKMED company have not reported any cyber incidents.

Neither Take Control Initiative company nor WORKMED company has reported experiencing a ransomware attack publicly.

Neither Take Control Initiative company nor WORKMED company has reported experiencing a data breach publicly.

Neither Take Control Initiative company nor WORKMED company has reported experiencing targeted cyberattacks publicly.

Neither WORKMED company nor Take Control Initiative company has reported experiencing or disclosing vulnerabilities publicly.

Neither WORKMED nor Take Control Initiative holds any compliance certifications.

Neither company holds any compliance certifications.

Neither WORKMED company nor Take Control Initiative company has publicly disclosed detailed information about the number of their subsidiaries.

WORKMED company employs more people globally than Take Control Initiative company, reflecting its scale as a Health and Human Services.

Neither WORKMED nor Take Control Initiative holds SOC 2 Type 1 certification.

Neither WORKMED nor Take Control Initiative holds SOC 2 Type 2 certification.

Neither WORKMED nor Take Control Initiative holds ISO 27001 certification.

Neither WORKMED nor Take Control Initiative holds PCI DSS certification.

Neither WORKMED nor Take Control Initiative holds HIPAA certification.

Neither WORKMED nor Take Control Initiative 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