open-appsec
WebsiteManagement PortalPlaygroundGitHub
  • open-appsec Documentation
  • What is open-appsec?
  • open-appsec Video Tutorials
  • Release Notes
  • Getting started
    • Getting Started
    • Start With Kubernetes
      • Install Using Interactive CLI Tool (Ingress NGINX)
      • Configuration Using Interactive CLI Tool
      • Install Using Helm
      • Install Using Helm - new flow (beta)
      • Configuration Using CRDs
      • Configuration Using CRDs - v1beta2
      • Configuration using CRDs - special options for Large Scale Deployments
        • Using appsec class for assigning separate custom resources to specific deployments
        • Using namespace-scoped custom resources
      • Monitor Events
    • Start With Linux
      • Install open-appsec for Linux
      • Using the open-appsec-ctl Tool
      • Configuration Using Local Policy File (Linux)
      • Local Policy File (Advanced)
      • Local Policy File v1beta2 (beta)
      • Monitor Events
    • Start with Docker
      • Install With Docker (Centrally Managed)
      • Install With Docker (Locally Managed)
      • Deploy With Docker-Compose (Beta)
      • Configuration Using Local Policy File (Docker)
      • Local Policy File (Advanced)
    • Using the Web UI (SaaS)
      • Sign-Up and Login to Portal
      • Agents Deployment
      • Connect Deployed Agents to SaaS Management Using Tool (K8s & Linux)
      • Connect Deployed Agents to SaaS Management Using Helm (K8s)
      • Connect Deployed Agents to SaaS Management (Docker)
      • Create a Profile
      • Protect Additional Assets
      • Monitor Events
    • Using the Advanced Machine Learning Model
  • Concepts
    • Agents
    • Management & Automation
    • Security Practices
    • Contextual Machine Learning
  • SETUP INSTRUCTIONS
    • Setup Web Application Settings
    • Setup Custom Rules and Exceptions
    • Setup Web User Response Pages
    • Setup Log Triggers
    • Setup Behavior Upon Failure
    • Setup Agent Upgrade Schedule
  • Additional Security Engines
    • Anti-Bot
    • API Schema Enforcement
    • Data Loss Prevention (DLP) Rules
    • File Security
    • Intrusion Prevention System (IPS)
    • Rate Limit
  • Snort Rules
    • Import Snort Rules
    • Write Snort Signatures
  • HOW TO
    • Configuration and Learning
      • Track Learning and Move From Learn/Detect to Prevent
      • Configure Contextual Machine Learning for Best Accuracy
      • Track Learning and Local Tuning in Standalone Deployments
      • Move From Detect to Prevent in K8s With Many Ingress Rules
  • Deployment and Upgrade
    • Load the Attachment in Proxy Configuration
    • Upgrade Your Reverse Proxy/API Gateway When an Agent is Installed
    • Integration in GitOps CD (K8s)
    • Build open-appsec Based on Source Code
  • Management Web UI
    • Track Agent Status
    • Delete or Reset Management Tenant (SaaS)
    • Disconnect an open-appsec agent from Central Management
  • Integrations
    • About Integrations With 3rd Party Solutions
    • CrowdSec
      • CrowdSec Bouncer Support
      • CrowdSec Intelligence Sharing Using open-appsec Parser/Scenario
    • NGINX Proxy Manager
      • Install NGINX Proxy Manager with open-appsec managed from NPM WebUI
      • Install NGINX Proxy Manager with open-appsec managed from central WebUI (SaaS)
      • Frequently Asked Questions
      • How to Migrate from an Existing NGINX Proxy Manager Deployment and Keep Configuration
    • NPMplus
    • Docker SWAG
      • Install Docker SWAG with open-appsec (locally managed)
      • How to connect locally managed Docker SWAG with open-appsec to WebUI
      • Install Docker SWAG with open-appsec (centrally managed)
      • Deploy Docker SWAG with docker-compose (beta)
      • Frequently Asked Questions
  • Troubleshooting
    • Troubleshooting
    • Troubleshooting Guides
      • Configuration contains ingress/asset with URL which already has asset attached to it in your tenant
      • HTTP Request to Port 80 Not Returning as Expected
      • Agent Fails to Recognize HTTP Transactions with NGINX
      • Agent Not Recognizing Initial HTTP Requests
      • Handling Large Requests (413 Responses)
      • open-appsec on Docker HTTP Transaction Handler Is Set To Ready
      • Traffic Recognition Issue on Single-Core Machine/Connection Timed Out
      • Installing open-appsec on CentOS 7
      • SELinux: checking status and disabling
      • Deploy open-appsec directly on the web server hosting the application to protect
      • object is locked or remote, and therefore cannot be modified
      • Failed to Register to Fog
  • references
    • Agent CLI
    • Event Query Language
    • Events/Logs Schema
    • WAF Comparison Project
Powered by GitBook
On this page

Was this helpful?

  1. Management Web UI

Disconnect an open-appsec agent from Central Management

PreviousDelete or Reset Management Tenant (SaaS)NextAbout Integrations With 3rd Party Solutions

Last updated 3 months ago

Was this helpful?

When working with open-appsec, there are two management systems: Declarative Management and Central Management. Depending on your setup, the steps to disconnect an agent may vary.

Agents can be deleted from central management using the Delete button, please note that while the agent won't be displayed in the Web UI it won't be uninstall.

Disconnecting from Central Management

The recommended and safest way to disconnect an agent from Central Management is to uninstall it and then redeploy. This ensures a clean disconnection and avoids potential issues.

However, if you need to disconnect the agent quickly and temporarily, follow these steps based on your environment.

Linux:

Currently, manual disconnection is not available. To disconnect, you must uninstall and reinstall the agent:

./open-appsec-install --uninstall
./open-appsec-install --auto

Docker:

Remove the AGENT_TOKEN Environment Variable

The agent authenticates with Central Management using the AGENT_TOKEN. To disconnect, remove it from your Docker configuration.

Modify your Docker command or Docker Compose file to exclude the AGENT_TOKEN:

  • Modify the Docker Command or Docker Compose File: Edit your Docker configuration by removing the AGENT_TOKEN environment variable,

    environment:
      - AGENT_TOKEN=

  • Remove the presistance folders: Delete the following persistent storage mounts to clear cached configuration and data:

${APPSEC_CONFIG}:/etc/cp/conf - 
${APPSEC_DATA}:/etc/cp/data - 
${APPSEC_LOGS}:/var/log/nano_agent
  • Ensure the Correct Policy Setup

    • If you are using Declarative Management, ensure that the local policy file is still mounted to /ext/appsec.

    • If you were using Central Management, you will need to add a local policy before restarting.

  • Restart the Agent: After making the change, restart the agent to apply the update:

    docker-compose up -d

Kubernetes:

  1. Uninstall the deployment.

helm list -n <namespace>
helm uninstall <release-name> -n <namespace>
  1. Verify that no persistent volumes remain.

  2. Redeploy, usimng instrcions bellow:

Start With Kubernetes