CatchPulse Protection Against GigaWiper: Benefits, Configuration and Limitations
Quick Answer CatchPulse can be a useful preventive layer against GigaWiper because its application allowlisting can block an untrusted executable before it r...
Quick Answer
CatchPulse can be a useful preventive layer against GigaWiper because its application allowlisting can block an untrusted executable before it runs. This approach is relevant to destructive malware: preventing execution can avoid damage that malware removal cannot reverse.
However, the documentation and testing reviewed for this article do not establish a GigaWiper-specific protection guarantee. Its effectiveness depends on the installed edition, active protection mode, trust rules, endpoint health and the attack path. CatchPulse should therefore be deployed alongside restricted administrator access, security monitoring and recoverable backups.
This guide explains the documented capabilities, their practical relevance and the limitations. Product documentation and public research were checked on 20 November 2026.
What Is GigaWiper?
Microsoft Threat Intelligence describes GigaWiper as a backdoor written in Go that combines remote-control functions with destructive capabilities. Microsoft first observed related wiping activity in October 2025 and published its analysis in July 2026. The malware is also tracked as BLUERABBIT.
Its documented capabilities include:
- Disk destruction: overwriting physical disks and removing partition information.
- System sabotage: damaging essential Windows components and disabling recovery.
- Destructive encryption: a ransomware-like operation that does not retain the keys needed to decrypt affected files.
- Remote operation: receiving commands and maintaining access through backdoor functionality.
The destructive encryption function should not be confused with every encryption feature in the backdoor; Microsoft also describes a separate encryption utility with different key handling.
For technical analysis and published indicators of compromise, consult Microsoft’s GigaWiper research.
What CatchPulse Contributes to Protection
CatchPulse is SecureAge’s Windows endpoint protection product. Its documented approach combines application control, AI-assisted malware detection and cloud antivirus scanning.
The most relevant component for this threat is application allowlisting: controlling which programs are permitted to execute. An unknown program can be blocked because it lacks permission to run, even when a scanner has not identified its malware family.
This differs from relying entirely on a malicious-file verdict. It does not mean competing endpoint products use signatures alone; many combine several prevention and detection methods.
SecureAge also describes centralized approval and policy capabilities through SecureAge Central. Availability varies by plan. See the official CatchPulse product overview and edition comparison.
Why blocking execution matters
Consider an illustrative scenario: an attacker places an unfamiliar executable on a protected workstation. The executable is not trusted, the allowlisting policy is enforced, and no exception authorizes it.
If application control prevents that executable from starting, the destructive instructions inside it cannot execute through that launch attempt.
This is a technical inference from the protection mechanism, not a reported CatchPulse-versus-GigaWiper laboratory result. The conclusion changes if the payload is already running, has been trusted, or reaches execution through a path outside the effective policy.
Which CatchPulse Settings Matter Most?
1. Lockdown Mode provides a clear execution boundary
SecureAge documents that Lockdown Mode automatically blocks untrusted files attempting to execute. This makes it a reasonable configuration to evaluate for workstations with a controlled set of approved applications.
The documented local-console path is Manage → Protection Modes → Lockdown Mode. Its Default option blocks applications outside the trusted list. SecureAge also documents a Silent option with automatic quarantine for viruses detected by real-time scans.
Test the setting before broad deployment: legitimate installers, updates and business utilities may need approval. Follow the official Lockdown Mode instructions for the installed release.
2. Automatic and Interactive modes make different trust decisions
Automatic Mode uses automated decisions for new or untrusted applications. Interactive Mode involves the user in deciding what to trust. These modes should not be assumed to behave identically to Lockdown Mode.
SecureAge explains that an application awaiting an Interactive Mode decision remains blocked until it is trusted. Consequently, approving a suspicious file can remove the very barrier that was preventing its execution.
For managed environments, establish who may approve software and what evidence they must check. See SecureAge’s explanation of blocking and approval behaviour.
3. Observation Mode is not an enforcement test
Observation Mode permits untrusted applications to run while recording activity. It can help assess compatibility, but it does not demonstrate that those applications would be stopped under the currently active setting.
Use it only within a controlled evaluation plan, with a defined end time. Do not leave production endpoints in observation mode while reporting them as protected by enforced allowlisting. See SecureAge’s Observation Mode documentation.
4. Trust All can create lasting trust decisions
SecureAge states that files attempting to execute during Trust All mode are automatically trusted and added to the allowlist. The temporary mode later returns to the previous setting.
Administrators should not assume that the timer expiring reverses trust decisions made during that window. Avoid using Trust All as a routine workaround for blocked software, especially while investigating suspicious activity.
The CatchPulse protection-mode guide explains these differences.
Supporting Controls and Their Limits
| Control | Potential security benefit | Important qualification |
|---|---|---|
| Application allowlisting | Prevents unauthorized programs from starting. | Protection depends on enforcement and correct trust decisions. |
| AI and antivirus analysis | Adds malicious-file assessment to execution control. | A clean result is not proof that a file is safe. |
| Script controls | Extends trust checking to configured script execution. | Coverage must be checked for the actual interpreter and execution method. |
| Central policy management | Helps administrators apply consistent rules and review approvals. | Endpoints must receive the policy, and administrative access must be protected. |
| Independent backups | Provide a recovery route if prevention fails. | They must remain accessible to defenders and protected from attackers. |
Scripts require more than trusting the interpreter
SecureAge documents that, for its configured script associations, both the interpreter and the script file must be trusted. An interpreter is the program that executes a script.
Administrators should review Manage → Application Control → Scripts and verify the associations relevant to their applications.
This documentation does not, by itself, demonstrate coverage for every inline command, macro, in-memory technique or abuse of a trusted Windows utility. Validate those requirements separately rather than treating script-file control as universal protection.
See SecureAge’s script interpreter and file association guidance.
Trusted certificates and installers need careful review
SecureAge documents that applications associated with entries in the Trusted Certificates list can be trusted. A broad certificate-based rule therefore affects more than one file.
The vendor also documents a Restricted Applications setting that prevents new files created by a restricted application from being automatically trusted. This can help control how trust extends through software installation workflows.
Review these mechanisms before deployment. A rule that makes updates convenient may also grant more trust than the organization intends. A digital signature identifies a signer; it does not establish that every possible use of the software is harmless.
Consult SecureAge’s documentation on trusted certificates and restricted applications.
Cloud scanning and offline operation are separate considerations
Cloud antivirus functions require connectivity to the relevant service. SecureAge documents that on-demand scanning is unavailable without internet access when the optional offline antivirus component is absent or disabled.
Do not interpret this as evidence that every protection component stops working offline. Equally, do not assume that an offline endpoint has all the capabilities available to an online endpoint.
Test execution control, scanning availability, alert delivery and later synchronization under the connectivity conditions your devices actually experience. See CatchPulse’s documented scanning requirements.
What Does Independent Testing Establish?
AVLab Cybersecurity Foundation’s March 2026 report includes CatchPulse Pro and describes a malicious executable being blocked at the execution stage. This provides independent evidence of execution prevention in the reported test.
However, the laboratory states that it enabled Block Mode, which was not active by default in its tested configuration. The result should therefore be read together with those settings.
The report does not establish a GigaWiper-specific result. Nor should its “Block Mode” terminology automatically be treated as identical to every setting named in another product version.
Read the AVLab March 2026 test report for the laboratory’s configuration and observations.
For a purchasing decision that specifically depends on GigaWiper protection, request evidence identifying the tested samples, product build, enabled components, policy settings, execution outcome and whether any damage occurred before blocking.
Compatibility and Edition Checks Before Deployment
SecureAge’s system-requirements page, updated in July 2026, lists:
- Windows 11, 64-bit.
- Windows 10, 32-bit and 64-bit.
- Windows Server 2016, 2019, 2022 and 2025, 64-bit.
- A local disk formatted with NTFS.
Check the current CatchPulse system requirements before installation. Confirm architecture, build and workload support with SecureAge where the documentation is not explicit. Product compatibility does not establish that the operating system itself remains within its applicable security-support lifecycle.
Edition matters: the current product comparison lists Lite as an on-demand scanner without application control. Standard and Pro include application control, while Pro adds reporting and policy-management features. The comparison also states that trials revert to Lite.
Check licence status and expiry as part of protection monitoring. Do not assume that a completed trial retains the preventive capabilities evaluated during the trial.
Recommended Deployment and Verification Procedure
The following is an administrative deployment checklist, not a GigaWiper removal procedure. Installation and policy changes should be performed by authorized administrators with the necessary Windows and management-console permissions.
- Establish a clean starting point. Investigate suspicious activity before generating a trusted software baseline. Do not use a new allowlist as evidence that an already compromised endpoint is clean.
- Record the existing configuration. Document installed security products, required applications, policy assignments and recovery arrangements. Preserve a known-good policy configuration before changing enforcement.
- Pilot representative devices. Include ordinary user workflows, application updates, remote support, backup operations and any specialist software.
- Confirm the licensed components. Check that application control and the intended scanning components are available and enabled. Complete the initial scan and review unresolved findings.
- Review trust rules. Examine trusted applications, certificates, installers and exceptions. Assign an owner to each business exception.
- Enable the intended enforcement mode. Evaluate Lockdown Mode where a controlled application set is practical. Verify the effective setting on the endpoint.
- Review script handling. Confirm that required interpreters and script types are covered without granting unnecessary trust.
- Validate protection and compatibility. Confirm that approved applications work, an intentionally untrusted harmless test application is blocked, and the event is recorded.
- Expand deployment gradually. Resolve pilot issues before applying the policy to more devices.
Clean baselines, staged rollout and testing of application behaviour follow the principles in NIST SP 800-167: Guide to Application Whitelisting. This is foundational guidance, not current CatchPulse-specific documentation.
Verify the protection state
SecureAge documents a Show Details view in the main console with status information for licensing, scanning, services and the application allowlisting driver.
Check the components expected for your installation rather than requiring an optional, deliberately uninstalled component to appear active. See the CatchPulse console and status documentation.
For a harmless blocking test, use an approved test program verified to be outside the effective trust rules. Confirm that its intended action did not occur. A program already trusted through a certificate or installer is unsuitable for testing the untrusted-file boundary.
Do not run live GigaWiper samples on production equipment. A harmless test verifies policy behaviour; it does not establish malware-family coverage.
Handle legitimate blocks without weakening every endpoint
If an essential application is blocked, review its source, integrity and business purpose. Approve the smallest justified exception through the authorized process.
If a policy change disrupts operations, restore the previously recorded policy for the affected pilot group and investigate the cause. Avoid organization-wide Trust All as a recovery shortcut. During suspected compromise, containment takes priority over allowing a blocked application to run.
Protection That Must Exist Alongside CatchPulse
Backups protected from the same compromise
Maintain recovery copies that compromised endpoints and ordinary administrator accounts cannot freely modify or delete. Depending on the environment, this can include offline copies and immutable storage with retention controls.
Test restoration of complete business services, including applications and configuration. An attached backup disk or a continuously synchronized folder should not be treated as an independent recovery guarantee.
MITRE ATT&CK’s data-backup mitigation connects protected backups and disaster-recovery planning to destructive attacks.
Access control, patching and monitoring
- Use standard user accounts for routine work and restrict elevated privileges.
- Protect remote access, administrative accounts and security-management access with strong authentication.
- Keep operating systems, applications and security agents updated.
- Restrict access between user devices, critical servers and backup infrastructure.
- Monitor endpoint alerts, policy changes and unexpected administrative activity.
- Maintain an incident-response plan with named decision-makers and recovery priorities.
These are general defence-in-depth recommendations, not a list of features supplied automatically by CatchPulse. NIST provides related guidance on application restrictions, patching, isolated backups and recovery planning.
What to Do If Destructive Malware Is Suspected
Unexpected file destruction, security alerts or widespread boot failures require urgent investigation. These symptoms alone do not identify GigaWiper.
- Isolate affected systems promptly. Use established endpoint-isolation controls or disconnect their network access.
- Contact the incident-response team. Coordinate through a trusted communication channel and protect backup infrastructure from affected systems.
- Preserve evidence where feasible. Retain alert records, logs and relevant timestamps. Avoid casually deleting files or repeatedly rebooting machines.
- Assess whether destruction is continuing locally. Network isolation does not necessarily stop an already running destructive process. Responders must balance immediate damage containment against loss of volatile evidence when deciding whether to power down.
- Investigate the wider compromise. Identify affected accounts, additional systems and persistence before reconnecting devices.
- Recover through a controlled plan. After containment and evidence decisions, rebuild compromised systems from trusted sources where appropriate and restore verified clean data.
CISA’s ransomware response checklist provides isolation and evidence-preservation guidance. Its incident-response playbooks cover coordinated eradication and recovery.
Frequently Asked Questions
Can CatchPulse restore data after a successful wipe?
The reviewed documentation does not establish a capability to reconstruct overwritten disk contents. Blocking malware and recovering destroyed data are different functions. Recovery requires an unaffected copy or another viable recovery source.
Can CatchPulse run alongside existing antivirus software?
SecureAge documents deployment alongside other antivirus products and advises omitting or disabling its optional Offline AV component for that arrangement. This is not a compatibility guarantee for every combination.
Confirm the exact products, versions and installation choices with the vendors, then pilot the configuration. See SecureAge’s coexistence and performance guidance.
Where is CatchPulse most practical?
As a practical assessment, its execution-control approach is particularly worth evaluating for managed Windows endpoints with a known application set and a reliable approval process. Environments that constantly generate or install new software need more careful policy design and operational testing.
Is CatchPulse a Good Choice Against GigaWiper?
CatchPulse is a reasonable product to evaluate for reducing unauthorized execution, which is an important preventive objective against destructive malware. Its documented allowlisting controls provide a concrete basis for that assessment.
A deployment decision should depend on verified enforcement, controlled trust rules, compatible workflows and evidence relevant to the organization’s threat model. Treat GigaWiper-specific coverage as unverified until supported by suitable testing, and maintain independent recovery capability even when prevention works well.
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.