Which process is responsible for archive scanning?
zipscnis the Check Point process responsible for scanning archive files. The DLP-related processes handle data-loss-prevention functions rather than archive inspection.
Master the Check Point Check Point Certified Threat Prevention Specialist (CTPS) (156-590) certification exam with 38 realistic practice questions covering Anti-Virus and Anti-Bot Protections, Advanced Threat Prevention Features and Troubleshooting, Threat Prevention Policy Profiles, Threat Prevention Policy Layers.
156-590
$20.00
Click any option to test your knowledge, or reveal the verified answer and detailed explanation below each question.
zipscnis the Check Point process responsible for scanning archive files. The DLP-related processes handle data-loss-prevention functions rather than archive inspection.
The Forensics tracking option adds extra fields to Threat Prevention logs, providing deeper information about an attack for analysis and troubleshooting.
Profile Cleanup can remove user-modified IPS protection overrides from selected Threat Prevention profiles, returning those protections to the profile’s configured activation behavior. It can also clear staging settings; it does not merge profiles, define a fallback packet policy, or remove protections based on elapsed time.
Threat Prevention can evaluate matching rules in multiple applicable policy layers. Each layer calculates its action independently, and when rules match in more than one layer, the Security Gateway enforces the strictest applicable action and settings; enforcement is therefore not limited to only one first-matched rule for the entire policy.
Anti-Virus is a pre-infection control that blocks malware while it is being transferred, and its inspection is limited to supported protocol decoders. The recommended setting is Hold so the firewall can wait for the real-time WildFire signature lookup; this helps prevent zero-day malware and exposure caused by outdated signatures.
The MITRE Corporation owns the CVE trademark and operates the CVE Program Secretariat, which maintains the program’s infrastructure. DHS/CISA sponsors and funds the program, while NIST maintains the separate National Vulnerability Database (NVD).
The IPS Software Blade is enabled in the individual Security Gateway object's Network Security settings and is applied through policy installation. In a ClusterXL deployment, the corresponding activation is configured on the cluster object, not independently on every member. [Check Point Threat Prevention Administration Guide](https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_ThreatPrevention_AdminGuide/Topics-TPG/Out_of_the_Box_Protection_from_Threats.htm)
IPS Follow Protections automatically enables new IPS protections that match the configured IPS profile criteria, keeping the profile aligned with newly downloaded protection definitions.
For Check Point Anti-Virus inspection, Active Streaming supports only a subset of file types. File-size limits apply to Passive Streaming, so they are not an Active Streaming limitation.
Check Point Anti-Virus protected scope defaults to inspecting traffic on External and DMZ interfaces.
In Check Point SmartConsole, theOptimizedThreat Prevention profile is activated by default because it provides strong protection while maintaining good Security Gateway performance.
A Cleanup Rule is an explicit catch-all rule and is recommended as a best practice, but it is not mandatory because an implicit cleanup rule/default behavior applies when no explicit rule matches. Check Point documentation states that an explicit cleanup rule can be changed or deleted.
`fwaccel stats` reports SecureXL acceleration statistics, including the proportion of F2F (forwarded-to-firewall) traffic or connections and counters that indicate why traffic was not accelerated. SecureXL status is obtained with `fwaccel stat`, not `fwaccel stats`.
A traditional Snort rule consists of a rule header followed by a parenthesized set of rule options. The header establishes the traffic and action criteria, while the options define the detailed matching conditions. Whitespace may be ignored by newer Snort versions, but the conventional rule syntax is a single logical line. [Snort Rule Writing Guide: The Basics](https://docs.snort.org/rules/)
Threat Prevention applies the profile action from a matching rule. Traffic that matches no Threat Prevention rule is not blocked or detected by that policy and is allowed to proceed; therefore, the action is Accept.
Updated IPS signatures are enforced on Security Gateways only after installation of the Threat Prevention Policy. The Access Control Policy is not the policy used to deploy IPS updates.
Threat Prevention inspection is performed only after the Access Control Policy has accepted the traffic. Traffic dropped or rejected by Access Control is not passed to Threat Prevention, so Threat Prevention cannot override or take precedence over that decision.
In Check Point IPS,Protectionis a searchable field. Date-related metadata such as update time, threat year, and release date is not searchable.
Check Point provides three preconfigured Threat Prevention profiles: Basic, Optimized, and Strict. They represent increasing breadth and strictness of protection, with corresponding potential performance impact.
IPS stands for Intrusion Prevention System, a security technology designed to detect and actively prevent malicious activity.
Anti-Virus exclusions identify trusted files that the Anti-Virus engine does not inspect, reducing inspection overhead on the Security Gateway.
Detect Mode permits traffic while logging detected threats instead of blocking them, enabling administrators to observe events and tune or troubleshoot Threat Prevention settings safely.
SecureXL uses the Secure Network Distributor (SND) to process and accelerate traffic on the accelerated path. Traffic that cannot remain fully accelerated is passed to Firewall/CoreXL processing instead.
IPS Implied Exceptions exclude certain Check Point component communications from IPS inspection so that IPS enforcement does not disrupt essential Security Gateway operations, including control connections.
The Anti-Bot Software Blade provides post-infection detection of bots on hosts and prevents damage by blocking bot command-and-control communications.
The Anti-Virus profile’s protocol inspection categories are Web (HTTP/HTTPS), FTP, SMB, and Mail, which includes SMTP. Therefore, the default enabled protocol set includes all four listed categories. Check Point’s Threat Prevention Administration Guide documents these Anti-Virus protocol categories.
A Threat Prevention exception is incorporated into and enforced through the Threat Prevention policy. The policy must be installed on the target Security Gateways for the exception to take effect.
An audit log records actions performed by administrators, such as administrative changes and other management operations. Check Point documentation states that the Management Server generates audit logs as records of administrator actions.
The Resource Advisor Daemon (RAD) manages Security Gateway communication with Check Point ThreatCloud for Anti-Virus protection-update activity. Check Point documents that Anti-Virus gateways download updates directly from the Check Point cloud.
Core Activation Exceptions override activation behavior for specific individual protections, allowing an administrator to handle a protection differently from the broader default activation policy.
Check Point enforces traffic quotas with SecureXL rate-limiting policy commands.fwaccel dos rateinstalls the rate-limiting policy and can consume quota policy data fromfw sam_policy, allowing rate limits to be enforced without unnecessarily forwarding matching traffic through the F2F path.
Access Control and Threat Prevention are separate policies. A connection permitted by Access Control is not dropped merely because it has no matching Threat Prevention rule; without a matching Threat Prevention rule and profile, the Threat Prevention engine does not inspect that traffic.
Profile cleanup removes administrator-made overrides from a Threat Prevention profile, restoring settings to the profile’s intended baseline rather than deleting exemptions, changing every setting to Detect, or repairing updates.
Prevent activates IPS inspection and applies active prevention, adding enforcement work to the traffic inspection already required for detection. Detect activates inspection only to track related traffic and events, whereas Inactive does not enforce the protection.Check Point: Configuring IPS Protections for Custom Threat Prevention
In Check Point IPS, newly updated protections placed in staging mode useDetectby default, allowing traffic while logging detected events until the protection action is manually changed.
QoS policy exemptions relate to quality-of-service configuration rather than the IPS exception categories. IPS Settings Exceptions, Core Activations Exceptions, and Implied IPS Exceptions are exception types.
TheInactiveaction disables the applicable Threat Prevention Blade for traffic that matches the exception rule. Check Point documentation specifies selecting Detect or Inactive to disable an applicable Threat Prevention Blade; Inactive is the action that excludes it from enforcement.
ThreatCloud DGA Protection detects domains generated by malware’s Domain Generation Algorithm, which enables infected devices to locate newly registered command-and-control servers.
Explore related CHECKPOINT exam dumps and free practice question banks.
"The content displayed here is a promotional preview and contains only 50% of the actual exam database. To access the complete set of updated questions, please upgrade to the Full Version."
👉 Click the button and follow the instructions to secure your full access immediately!