Comparison Overview

Logicworks

VS

Huawei Enterprise

Logicworks

155 Avenue of the Americas, New York, NY, 10013, US
Last Update: 2025-05-05 (UTC)
Between 900 and 1000
https://www.rapidscale.net

Excellent

In today’s market, technology can define a company’s ability to compete and win. But innovation is moving so fast, most organizations struggle to manage what they have and can’t evolve quick enough to move the needle for their business. The modern cloud can help you automate manual tasks, scale capacity and modernize applications to drive revenue growth. But 90% of technology leaders say they have underestimated the complexity of the cloud. RapidScale is the managed cloud partner that turns technology into your biggest competitive advantage. Our comprehensive portfolio of private and public cloud solutions is tailored to your needs and backed by one of the deepest benches of certified experts in the industry. We make innovation easy, by bringing you the latest solutions to keep your technology platforms responsive and delivering the consistent results your business deserves.

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

Huawei Enterprise

None
Last Update: 2025-03-14 (UTC)

Excellent

Between 900 and 1000
https://lnkd.in

Huawei Enterprise Business Group (EBG) is committed to bring digital to every organization for a fully connected, intelligent world, including government and public sectors, financial services, energy, transportation, and manufacturing, and other sectors. Huawei focus on ICT infrastructure and utilize our technological strengths in the areas of cloud computing, big data, connectivity, the Internet of Things (IoT), and Artificial Intelligence (AI), offers a wide range of products and solutions. Huawei is dedicated to build symbiotic relationships with our ecosystem partners and achieve shared success. To achieve this, we have made every effort to open up our ICT platforms, global marketing platforms, and training and service platforms to our partners, and work together to ensure success in the market. We have also worked to facilitate the development of industry standards and enabling digitalization. Through these activities, we aim to jointly create value for customers, grow the industries, and achieve sustainable development. Currently, 267 of Fortune Globe 500, and a total of more than 700 cities all over the world, have chosen Huawei as their partner in digital transformation. Explore e.huawei.com for more information, or join our LinkedIn Group: LinkedIn https://lnkd.in/g9WU2Bu

NAICS: None
NAICS Definition:
Employees: 10,001+
Subsidiaries: 14
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/logicworks.jpeg
Logicworks
—
ISO 27001
Not verified
—
SOC 2
Not verified
—
GDPR
No public badge
—
PCI DSS
No public badge
https://images.rankiteo.com/companyimages/huawei-enterprise.jpeg
Huawei Enterprise
—
ISO 27001
Not verified
—
SOC 2
Not verified
—
GDPR
No public badge
—
PCI DSS
No public badge
Compliance Summary
Logicworks
100%
Compliance Rate
0/4 Standards Verified
Huawei Enterprise
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Information Technology & Services Industry Average (This Year)

No incidents recorded for Logicworks in 2025.

Incidents vs Information Technology & Services Industry Average (This Year)

No incidents recorded for Huawei Enterprise in 2025.

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

Logicworks cyber incidents detection timeline including parent company and subsidiaries

Incident History — Huawei Enterprise (X = Date, Y = Severity)

Huawei Enterprise cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/logicworks.jpeg
Logicworks
Incidents

Date Detected: 5/2019
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/huawei-enterprise.jpeg
Huawei Enterprise
Incidents

No Incident

FAQ

Both Logicworks company and Huawei Enterprise company demonstrate a comparable AI risk posture, with strong governance and monitoring frameworks in place.

Logicworks company has historically faced a number of disclosed cyber incidents, whereas Huawei Enterprise company has not reported any.

In the current year, Huawei Enterprise company and Logicworks company have not reported any cyber incidents.

Neither Huawei Enterprise company nor Logicworks company has reported experiencing a ransomware attack publicly.

Logicworks company has disclosed at least one data breach, while the other Huawei Enterprise company has not reported such incidents publicly.

Neither Huawei Enterprise company nor Logicworks company has reported experiencing targeted cyberattacks publicly.

Neither Logicworks company nor Huawei Enterprise company has reported experiencing or disclosing vulnerabilities publicly.

Huawei Enterprise company has more subsidiaries worldwide compared to Logicworks company.

Logicworks company employs more people globally than Huawei Enterprise company, reflecting its scale as a Information Technology & Services.

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.

Published
Date
2025-10-04
Updated
Date
2025-10-04
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
References
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.

Published
Date
2025-10-04
Updated
Date
2025-10-04
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
References
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.

Published
Date
2025-10-04
Updated
Date
2025-10-04
References
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.

Published
Date
2025-10-04
Updated
Date
2025-10-04
References
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.

Published
Date
2025-10-04
Updated
Date
2025-10-04
References