Comparison Overview

Arcosa Specialty Materials

VS

Kazatomprom

Arcosa Specialty Materials

1550 Double Drive, Norman, Ok, 73072, US
Last Update: 2025-03-07 (UTC)

Strong

Arcosa Specialty Materials is the result of a long and successful history of doing one thing and one thing only. Treating people right. Our customers, our employees, our partners, and vendors. We believe when you take care of the people that matter most, everything else will take care of itself. Our roots go back to 1955 when the Harrison Gypsum Company originally began as a small family operation supplying gypsum to the family farm and neighbors. Originally named the Cement Gypsum Company, Harrison Mine No. 1 was opened near Cement, OK, and underwent the name change to Harrison Gypsum Company in 1956. Over the years the company developed the mining business by supplying raw gypsum rock to nearby manufacturers of Portland cement. As the market area for Harrison Gypsum expanded, gypsum reserves and production capacity also expanded. With business growing, capital investments were made to upgrade to modern mining equipment and improve infrastructure. In 1994, Harrison Gypsumโ€™s mine #2 was named the largest single gypsum mine in the United States by the U.S. Department of the Interior Publication. Today, the total gypsum reserves of Harrison Gypsum Company is estimated to be in excess of a quarter of a billion tons. In 2012, HIG Capital, a leading global private equity investment firm, completed a recapitalization of Harrison Gypsum. This provided Harrison Gypsum with financial and operating resources that will enable us to further capitalize on our significant growth potential. 2015 marked a new chapter in the history of the company when Harrison Gypsum became ACG Materials. This new name gives a strong nod to our history as a company, but also to our future opportunities.

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

Kazatomprom

17/12, Syganak Street. Z05T1X3 Astana, KZ
Last Update: 2025-06-21 (UTC)

Strong

Between 800 and 900

NAC Kazatomprom JSC is the national operator of the Republic of Kazakhstan for the import and export of uranium, rare metals, nuclear fuel for nuclear power plants. Since 2009, Kazakhstan has been the world leader in natural uranium mining, and Kazatomprom has priority rights to the countryโ€™s extensive reserves. National atomic company assets include the entire complex of Kazakh enterprises involved in the front-end of the nuclear fuel cycle - from geological exploration, uranium mining, and production of nuclear fuel cycle, through to scientific research and development of patented technologies.

NAICS: 212
NAICS Definition: Mining (except Oil and Gas)
Employees: 10,001+
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/arcosa-specialty-materials.jpeg
Arcosa Specialty Materials
โ€”
ISO 27001
Not verified
โ€”
SOC 2
Not verified
โ€”
GDPR
No public badge
โ€”
PCI DSS
No public badge
https://images.rankiteo.com/companyimages/js-nac-kazatomprom-.jpeg
Kazatomprom
โ€”
ISO 27001
Not verified
โ€”
SOC 2
Not verified
โ€”
GDPR
No public badge
โ€”
PCI DSS
No public badge
Compliance Summary
Arcosa Specialty Materials
100%
Compliance Rate
0/4 Standards Verified
Kazatomprom
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Mining Industry Average (This Year)

No incidents recorded for Arcosa Specialty Materials in 2025.

Incidents vs Mining Industry Average (This Year)

No incidents recorded for Kazatomprom in 2025.

Incident History โ€” Arcosa Specialty Materials (X = Date, Y = Severity)

Arcosa Specialty Materials cyber incidents detection timeline including parent company and subsidiaries

Incident History โ€” Kazatomprom (X = Date, Y = Severity)

Kazatomprom cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/arcosa-specialty-materials.jpeg
Arcosa Specialty Materials
Incidents

No Incident

https://images.rankiteo.com/companyimages/js-nac-kazatomprom-.jpeg
Kazatomprom
Incidents

No Incident

FAQ

Both Arcosa Specialty Materials company and Kazatomprom company demonstrate a comparable AI risk posture, with strong governance and monitoring frameworks in place.

Historically, Kazatomprom company has disclosed a higher number of cyber incidents compared to Arcosa Specialty Materials company.

In the current year, Kazatomprom company and Arcosa Specialty Materials company have not reported any cyber incidents.

Neither Kazatomprom company nor Arcosa Specialty Materials company has reported experiencing a ransomware attack publicly.

Neither Kazatomprom company nor Arcosa Specialty Materials company has reported experiencing a data breach publicly.

Neither Kazatomprom company nor Arcosa Specialty Materials company has reported experiencing targeted cyberattacks publicly.

Neither Arcosa Specialty Materials company nor Kazatomprom company has reported experiencing or disclosing vulnerabilities publicly.

Arcosa Specialty Materials company has more subsidiaries worldwide compared to Kazatomprom company.

Neither Arcosa Specialty Materials company nor Kazatomprom company has publicly disclosed the exact number of their employees.

Latest Global CVEs (Not Company-Specific)

Description

A vulnerability was found in LaChatterie Verger up to 1.2.10. This impacts the function redirectToAuthorization of the file /src/main/services/mcp/oauth/provider.ts. The manipulation of the argument URL results in deserialization. The attack can be executed remotely. The exploit has been made public and could 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
Description

A vulnerability has been found in SeriaWei ZKEACMS up to 4.3. This affects the function Delete of the file src/ZKEACMS.Redirection/Controllers/UrlRedirectionController.cs of the component POST Request Handler. The manipulation leads to improper authorization. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Risk Information
cvss2
Base: 5.5
Severity: LOW
AV:N/AC:L/Au:S/C:N/I:P/A:P
cvss3
Base: 5.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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
Description

In the Linux kernel, the following vulnerability has been resolved: jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount syzbot found an invalid-free in diUnmount: BUG: KASAN: double-free in slab_free mm/slub.c:3661 [inline] BUG: KASAN: double-free in __kmem_cache_free+0x71/0x110 mm/slub.c:3674 Free of addr ffff88806f410000 by task syz-executor131/3632 CPU: 0 PID: 3632 Comm: syz-executor131 Not tainted 6.1.0-rc7-syzkaller-00012-gca57f02295f1 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report_invalid_free+0xac/0xd0 mm/kasan/report.c:460 ____kasan_slab_free+0xfb/0x120 kasan_slab_free include/linux/kasan.h:177 [inline] slab_free_hook mm/slub.c:1724 [inline] slab_free_freelist_hook+0x12e/0x1a0 mm/slub.c:1750 slab_free mm/slub.c:3661 [inline] __kmem_cache_free+0x71/0x110 mm/slub.c:3674 diUnmount+0xef/0x100 fs/jfs/jfs_imap.c:195 jfs_umount+0x108/0x370 fs/jfs/jfs_umount.c:63 jfs_put_super+0x86/0x190 fs/jfs/super.c:194 generic_shutdown_super+0x130/0x310 fs/super.c:492 kill_block_super+0x79/0xd0 fs/super.c:1428 deactivate_locked_super+0xa7/0xf0 fs/super.c:332 cleanup_mnt+0x494/0x520 fs/namespace.c:1186 task_work_run+0x243/0x300 kernel/task_work.c:179 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0x664/0x2070 kernel/exit.c:820 do_group_exit+0x1fd/0x2b0 kernel/exit.c:950 __do_sys_exit_group kernel/exit.c:961 [inline] __se_sys_exit_group kernel/exit.c:959 [inline] __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:959 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd [...] JFS_IP(ipimap)->i_imap is not setting to NULL after free in diUnmount. If jfs_remount() free JFS_IP(ipimap)->i_imap but then failed at diMount(). JFS_IP(ipimap)->i_imap will be freed once again. Fix this problem by setting JFS_IP(ipimap)->i_imap to NULL after free.

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix deletion race condition System crash when using debug kernel due to link list corruption. The cause of the link list corruption is due to session deletion was allowed to queue up twice. Here's the internal trace that show the same port was allowed to double queue for deletion on different cpu. 20808683956 015 qla2xxx [0000:13:00.1]-e801:4: Scheduling sess ffff93ebf9306800 for deletion 50:06:0e:80:12:48:ff:50 fc4_type 1 20808683957 027 qla2xxx [0000:13:00.1]-e801:4: Scheduling sess ffff93ebf9306800 for deletion 50:06:0e:80:12:48:ff:50 fc4_type 1 Move the clearing/setting of deleted flag lock.

Description

In the Linux kernel, the following vulnerability has been resolved: mm/ksm: fix race with VMA iteration and mm_struct teardown exit_mmap() will tear down the VMAs and maple tree with the mmap_lock held in write mode. Ensure that the maple tree is still valid by checking ksm_test_exit() after taking the mmap_lock in read mode, but before the for_each_vma() iterator dereferences a destroyed maple tree. Since the maple tree is destroyed, the flags telling lockdep to check an external lock has been cleared. Skip the for_each_vma() iterator to avoid dereferencing a maple tree without the external lock flag, which would create a lockdep warning.