Manual :
BIG-IP Application Security Manager: Implementations
Applies To:
-
BIG-IP ASM
21.1.0
- About adding file types
- Adding allowed file types
- Adding disallowed file types
- Adding potential disallowed file types
- About adding parameters to a security policy
- Adding URLs to a Security Policy
- About adding URLs
- About referrer URLs
- Adding allowed HTTP URLs
- Adding disallowed HTTP URLs
- Creating allowed WebSocket URLs
- Adding disallowed WebSocket URLs
- Enforcing requests for HTTP URLs based on header content
- Specifying characters legal in URLs
- Overriding methods on URLs
- Configuring flows to URLs
- Creating flow parameters
- Configuring dynamic flows to URLs
- Configuring dynamic session IDs in URLs
- Adding Cookies
- About cookies
- About adding cookies
- Overview: Configuring advanced cookie protection
- Adding Allowed Methods to a Security Policy
- Adding allowed methods
- Overview: Adding JSON support to existing security policies
- Creating a JSON profile
- Associating a JSON profile with a URL
- Associating a JSON profile with a parameter
- Implementation result
- Using a Custom JSON Schema
- Using a custom JSON schema
- Assigning a JSON profile to an HTTP URL
- Assigning a JSON profile to a WebSocket URL
- Overview: Automatically synchronizing ASM systems
- About device management and synchronizing application security configurations
- Considerations for application security synchronization
- Performing basic network configuration for synchronization
- Specifying an IP address for config sync
- Establishing device trust
- Creating a Sync-Failover device group
- Syncing the BIG-IP configuration to the device group
- Specifying IP addresses for failover communication
- Creating a Sync-Only device group
- Enabling ASM synchronization on a device group
- Synchronizing an ASM-enabled device group
- Implementation result
- Overview: Changing how a security policy is built
- Task summary
- Changing how to build a security policy
- Adding trusted IP addresses to a security policy
- Learning host names automatically
- Classifying the content of learned parameters
- Specifying whether to learn integer parameters
- Specifying when to learn dynamic parameters
- Collapsing entities in a security policy
- Changing how cookies are enforced
- Limiting the maximum number of policy elements
- Classifying the content of requests to URLs
- Specifying the file types for wildcard URLs
- Disabling full policy inspection
- Stopping and starting automatic policy building
- About security policy settings
- Editing an existing security policy
- Changing security policy enforcement
- Adjusting the enforcement readiness period
- Making a parent policy mandatory
- Viewing whether a security policy is case-sensitive
- Differentiating between HTTP and HTTPS URLs
- Specifying the response codes that are allowed
- Activating ASM iRule events
- Allowing XFF headers in requests
- Adding host names
- Protecting against cross-site request forgery (CSRF)
- About bot defense
- About bot defense profile templates
- Bot defense relaxed template
- Bot defense balanced template
- Bot defense strict template
- Creating a bot defense profile
- Assigning a bot defense profile to a virtual server
- Configuring bot defense logging
- Viewing bot defense traffic
- Creating a bot defense whitelist
- Using bot defense microservices
- Using DoS Attack Mitigation Mode
- Using API access for browsers and mobile applications
- Enforcing staged bot signatures
- About cross domain requests
- Bot defense and CORS
- Overview: Configuring DoS policy switching
- Task Summary
- About DoS protection and local traffic policies
- Creating a DoS profile for Layer 7 traffic
- Modifying the default DoS profile
- Creating a local traffic policy for DoS policy switching
- Creating policy rules for DoS policy switching
- Apply a protection profile to a protected object
- Associating a published local traffic policy with a virtual server
- Implementation results
- Overview: Integrating ASM and APM with database security products
- Prerequisites for integrating ASM and APM with database security
- Creating a VLAN
- Creating a self IP address for a VLAN
- Creating a local traffic pool for application security
- Creating a virtual server to manage HTTPS traffic
- Creating a simple security policy
- Creating an access profile
- Configuring an access policy
- Adding the access profile to the virtual server
- Configuring a database security server
- Enabling database security integration with ASM and APM
- Implementation result
- About logging profiles
- How to use multiple logging profiles
- Log Illegal Requests locally, All requests remotely
- Multiple SIEM Systems
- Creating a logging profile for local storage
- Setting up remote logging
- Associating a logging profile with a security policy
- About logging responses
- About ArcSight log message format
- About syslog request format
- Filtering logging information
- Viewing application security logs
- Overview: Manually synchronizing ASM systems
- About device management and synchronizing application security configurations
- Considerations for application security synchronization
- Performing basic network configuration for synchronization
- Specifying an IP address for config sync
- Establishing device trust
- Creating a Sync-Failover device group
- Syncing the BIG-IP configuration to the device group
- Specifying IP addresses for failover communication
- Enabling ASM synchronization on a device group
- Synchronizing an ASM-enabled device group
- Implementation result
- About brute force attacks
- About configuring brute force protection
- Overview: Mitigating brute force attacks
- Creating login pages automatically
- Creating login pages manually
- Configuring automatic brute force protection
- Creating a custom brute force protection
- Viewing brute force attack reports
- Displaying brute force event logs
- What is a DoS attack?
- About recognizing DoS attacks
- When to use different DoS protections
- About configuring TPS-based DoS protection
- About configuring stress-based DoS protection
- About Behavioral DoS protection
- About DoS mitigation methods
- About geolocation mitigation
- About heavy URL protection
- About site-wide DoS mitigation
- About CAPTCHA challenges in DoS detection
- About DoS protection and HTTP caching
- Overview: Preventing DoS attacks on applications
- Configuring DoS protection for applications
- Creating a whitelist for DoS protection
- Configuring TPS-based DoS detection
- Configuring behavioral & stress-based DDoS protection
- Configuring heavy URL protection
- Recording traffic during DoS attacks
- Configuring CAPTCHA for DoS protection
- Apply a protection profile to a protected object
- Implementation Result
- Overview: Preventing session hijacking
- Task Summary
- Preventing session hijacking
- Configuring the response to cookie hijacking
- Overview: Tracking user sessions using login pages
- Task Summary
- Creating login pages automatically
- Creating login pages manually
- Setting up session tracking
- Monitoring user and session information
- Tracking specific user and session information
- Overview: Tracking application security sessions using APM
- Prerequisites for setting up session tracking with APM
- Task summary
- Creating a VLAN
- Creating a self IP address for a VLAN
- Creating a local traffic pool for application security
- Creating a virtual server to manage HTTPS traffic
- Creating a virtual server to manage HTTP/2 traffic
- Creating a simple security policy
- Creating an access profile
- Configuring an access policy
- Adding the access profile to the virtual server
- Setting up ASM session tracking with APM
- Monitoring user and session information
- About learning
- About learning suggestions
- What suggestions look like
- What violations are unlearnable?
- Configuring how entities are learned
- Learning from responses
- Learning based on response codes
- Reviewing learning suggestions
- Viewing requests that caused learning suggestions
- Viewing and allowing ignored suggestions
- About enforcement readiness
- Enforcing entities
- Exploring security policy action items
- Overview: Securing applications that use WebSocket connections
- Task Summary
- About WebSocket security
- About WebSocket and login enforcement
- About WebSocket and cross-domain request enforcement
- Securing WebSocket applications: The easy way
- Creating a WebSocket profile
- Recognizing WebSocket traffic
- Creating a JSON profile
- Creating a plain text content profile
- Creating allowed WebSocket URLs
- Adjusting learning settings for WebSocket URLs
- Classifying the content of requests to WebSocket URLs
- Adding disallowed WebSocket URLs
- Associating a profile with a WebSocket URL
- WebSocket violations
- Overview: Securing FTP traffic using default values
- Creating an FTP service profile with security enabled
- Enabling protocol security for an FTP virtual server
- Review violation statistics for security profiles
- Overview: Securing FTP traffic using a custom configuration
- Task summary
- Creating a custom FTP profile for protocol security
- Creating a security profile for FTP traffic
- Modifying associations between service profiles and security profiles
- Configuring an FTP virtual server with a server pool
- Review violation statistics for security profiles
- Overview: Securing SMTP traffic using system defaults
- Task Summary
- Creating an SMTP service profile with security enabled
- Creating an SMTP virtual server with protocol security
- Review violation statistics for security profiles
- Overview: Creating a custom SMTP security profile
- Task summary
- Creating a custom SMTP service profile
- Creating a security profile for SMTP traffic
- Enabling anti-virus protection for email
- Modifying associations between service profiles and security profiles
- Creating and securing an SMTP virtual server and pool
- Review violation statistics for security profiles
- Overview: Setting up IP intelligence blocking
- Task summary
- Downloading the IP intelligence database
- Blocking IP addresses with bad reputations
- Reviewing IP intelligence statistics
- Creating an iRule to log IP intelligence information
- Creating an iRule to reject requests with questionable IP addresses
- IP intelligence categories
- Overview: Synchronizing ASM systems across LANs
- About device management and synchronizing application security configurations
- Considerations for application security synchronization
- Performing basic network configuration for synchronization
- Specifying an IP address for config sync
- Establishing device trust
- Creating a Sync-Failover device group
- Syncing the BIG-IP configuration to the device group
- Specifying IP addresses for failover communication
- Creating a Sync-Only device group
- Enabling ASM synchronization on a Sync-Only device group
- Synchronizing an ASM-enabled device group
- Implementation result