Skip to main content

Anti-Spyware Profile

Anti-spyware profiles define threat detection and prevention rules for spyware, command-and-control traffic, and other malicious activity. The scm CLI provides commands to create, update, delete, and load anti-spyware profiles.

Overview

The anti-spyware-profile commands allow you to:

  • Create anti-spyware profiles with threat blocking rules
  • Update existing profile configurations
  • Delete profiles that are no longer needed
  • Bulk import profiles from YAML files
  • Export profiles for backup or migration

Set Anti-Spyware Profile

Create or update an anti-spyware profile.

Syntax

scm set security anti-spyware-profile NAME [OPTIONS]

Arguments

ArgumentDescriptionRequired
NAMEProfile nameYes

Options

OptionDescriptionRequired
--folder TEXTFolder locationNo*
--snippet TEXTSnippet locationNo*
--device TEXTDevice locationNo*
--description TEXTProfile descriptionNo
--cloud-inline-analysis / --no-cloud-inline-analysisEnable cloud inline analysisNo
--block-critical-highAdd default rule to block critical and high severity threatsNo

* One of --folder, --snippet, or --device is required.

Examples

Create Basic Profile

$ scm set security anti-spyware-profile strict-security \
--folder Texas \
--description "Block critical threats"
---> 100%
Created anti-spyware profile: strict-security in folder Texas

Create Profile Blocking Critical and High Severity

$ scm set security anti-spyware-profile block-threats \
--folder Texas \
--block-critical-high \
--cloud-inline-analysis
---> 100%
Created anti-spyware profile: block-threats in folder Texas

Create Profile in Snippet

$ scm set security anti-spyware-profile standard-protection \
--snippet Security-Best-Practice
---> 100%
Created anti-spyware profile: standard-protection in snippet Security-Best-Practice

Delete Anti-Spyware Profile

Delete an anti-spyware profile from SCM.

Syntax

scm delete security anti-spyware-profile NAME [OPTIONS]

Arguments

ArgumentDescriptionRequired
NAMEProfile name to deleteYes

Options

OptionDescriptionRequired
--folder TEXTFolder locationNo*
--snippet TEXTSnippet locationNo*
--device TEXTDevice locationNo*
--forceSkip confirmation promptNo

* One of --folder, --snippet, or --device is required.

Example

$ scm delete security anti-spyware-profile strict-security \
--folder Texas \
--force
---> 100%
Deleted anti-spyware profile: strict-security from folder Texas

Load Anti-Spyware Profile

Load multiple anti-spyware profiles from a YAML file.

Syntax

scm load security anti-spyware-profile [OPTIONS]

Options

OptionDescriptionRequired
--file TEXTPath to YAML file containing profile definitionsYes
--folder TEXTOverride folder location for all profilesNo
--snippet TEXTOverride snippet location for all profilesNo
--device TEXTOverride device location for all profilesNo
--dry-runPreview changes without applying themNo

YAML File Format

---
anti_spyware_profiles:
- name: strict-security
folder: Texas
description: "Block critical threats"
cloud_inline_analysis: true

- name: standard-protection
folder: Texas
description: "Standard spyware protection"

Examples

Load with Original Locations

$ scm load security anti-spyware-profile \
--file anti-spyware.yaml
---> 100%
✓ Loaded anti-spyware profile: strict-security
✓ Loaded anti-spyware profile: standard-protection

Successfully loaded 2 out of 2 anti-spyware profiles from 'anti-spyware.yaml'

Load with Folder Override

$ scm load security anti-spyware-profile \
--file anti-spyware.yaml \
--folder Austin
---> 100%
✓ Loaded anti-spyware profile: strict-security
✓ Loaded anti-spyware profile: standard-protection

Successfully loaded 2 out of 2 anti-spyware profiles from 'anti-spyware.yaml'
note

When using container override options (--folder, --snippet, --device), all profiles will be loaded into the specified container, ignoring the container specified in the YAML file.

Show Anti-Spyware Profile

Display anti-spyware profile objects.

Syntax

scm show security anti-spyware-profile [NAME] [OPTIONS]

Arguments

ArgumentDescriptionRequired
NAMEProfile name to display; omit to list allNo

Options

OptionDescriptionRequired
--folder TEXTFolder locationNo*
--snippet TEXTSnippet locationNo*
--device TEXTDevice locationNo*
--output, -o [table|json|yaml]Output format (default: table)No
--max-results INTEGERMaximum number of results to displayNo

* One of --folder, --snippet, or --device is required.

note

When no NAME is specified, all items are listed by default.

Examples

Show Specific Profile

$ scm show security anti-spyware-profile strict-security \
--folder Texas
---> 100%
Anti-Spyware Profile: strict-security
Location: Folder 'Texas'
Description: Block critical threats
Cloud Inline Analysis: true

List All Profiles (Default Behavior)

$ scm show security anti-spyware-profile --folder Texas
---> 100%
Anti-Spyware Profiles in folder 'Texas':
------------------------------------------------------------
Name: strict-security
Description: Block critical threats
Cloud Inline Analysis: true
------------------------------------------------------------
Name: standard-protection
Description: Standard spyware protection
------------------------------------------------------------

Backup Anti-Spyware Profiles

Backup all anti-spyware profile objects from a specified location to a YAML file.

Syntax

scm backup security anti-spyware-profile [OPTIONS]

Options

OptionDescriptionRequired
--folder TEXTFolder to backup profiles fromNo*
--snippet TEXTSnippet to backup profiles fromNo*
--device TEXTDevice to backup profiles fromNo*
--file TEXTOutput filename (defaults to auto-generated)No

* One of --folder, --snippet, or --device is required.

Examples

Backup from Folder

$ scm backup security anti-spyware-profile --folder Texas
---> 100%
Successfully backed up 5 anti-spyware profiles to anti_spyware_profile_folder_texas_20240115_120530.yaml

Backup with Custom Filename

$ scm backup security anti-spyware-profile \
--folder Texas \
--file texas-anti-spyware.yaml
---> 100%
Successfully backed up 5 anti-spyware profiles to texas-anti-spyware.yaml

Best Practices

  1. Block Critical and High Severity: Use --block-critical-high to create profiles that automatically block the most dangerous threats.
  2. Enable Cloud Analysis: Turn on --cloud-inline-analysis for real-time cloud-based threat detection on critical traffic paths.
  3. Use Descriptive Names: Name profiles to reflect their purpose and severity level (e.g., strict-security, standard-protection).
  4. Backup Before Changes: Always backup existing profiles before making bulk modifications via load commands.
  5. Test in Non-Production: Create and validate profiles in a test folder before applying to production environments.