Home
KUBE
Unify DevOps and Security teams by managing certificates with a Kubernetes-native certificate lifecycle management solution.
KUBE User Guide
Visibility
Client
Handle Excluded Certificates During Certificate Ingestion
Use this procedure to ensure certificates already present in Excluded Certificates inventory are not added again to the main inventory when certificates enter AppViewX through Config Sync, KUBE, or Cloud integrations.

CLM
Automate certificate lifecycle management including issuance, discovery, renewal, and deployment, across public and private trust CAs. Assess, prioritize, and plan your migration to quantum-safe encryption with the Quantum Trust Hub add-on module.
PKI
Provision, govern and scale private trust certificates with a Post Quantum ready cloud based Enterprise PKI-as-a-Service.
Code Signing
Secure software, firmware, and containers with a comprehensive enterprise code signing solution.
SSH
Control SSH access and key rotation at scale with an SSH key lifecycle management solution.
KUBE
Unify DevOps and Security teams by managing certificates with a Kubernetes-native certificate lifecycle management solution.
- KUBE User Guide
  - Getting Started
  - KUBE Features and Capabilities
  - KUBE Deployment Architecture
  - Visibility & Control
  - Docker Image and Helm Chart Validation Using Cosign
  - Visibility
    - Server
    - Client
      - Exporting Client Certificate
      - Deleting Client Certificates
      - Changing Client Certificate Status
      - Assigning Client Certificate Group
      - Unassigning Certificate Group from Client Certificates
      - Bulk Client Certificate Revoke Action
      - Add/Modify Comments for Client Certificate
      - Updating Certificate Attributes for Client Certificate
      - Bulk Updating Certificate Attributes
      - Pushing a Client Certificate to a Device
      - Bulk Updating Certificate Attributes
      - Pushing a Client Certificate to a Device
      - Discover and Push AWS S3 Client Certificates
        Use this procedure to verify S3-discovered client certificates in KUBE inventory and push a selected certificate to a target device.
      - Handle Excluded Certificates During Certificate Ingestion
        Use this procedure to ensure certificates already present in Excluded Certificates inventory are not added again to the main inventory when certificates enter AppViewX through Config Sync, KUBE, or Cloud integrations.
      - Renewing a Client Certificate
    - Trust Store
  - Dashboard - Insights
  - Policy Enforcement
  - Automate Certificate Lifecycle Management
  - Secure Service Mesh with mTLS authentication
  - Managing the Mesh Inventory
  - Enable External Signing
  - Integrating Istio with Custom CA
  - Alerts and Logs
  - Automation
  - System Administration
  - Notification Event
  - Enabling Custom Workflow Integration
  - Uninstalling and Cleaning up the KUBE Deployment
  - FAQs and Troubleshooting
- KUBE API Guide
- KUBE Upgrade Guide
  When migrating the AppViewX Compute cluster, it is necessary to upgrade the Cloud Connector and Cert Orchestrator to enable the latest KUBE features.
- KUBE as an EKS Addon - AWS Marketplace
DDI
Manage domain registration, renewal, decommissioning, and other security controls with an end-to-end domain lifecycle management solution.
ADC
Automate and orchestrate application delivery infrastructure at scale with an ADC lifecycle automation platform.
Platform
Manage policy and automation across all of the products and modules in the AVX ONE platform.
AVX Setup
Get detailed instructions for setting up AVX ONE in on-premises or SaaS deployments.
Artifacts
Review new features, fixes, and security advisories with official AppViewX release documentation.

Handle Excluded Certificates During Certificate Ingestion

Use this procedure to ensure certificates already present in Excluded Certificates inventory are not added again to the main inventory when certificates enter AppViewX through Config Sync, KUBE, or Cloud integrations.

Certificate ingestion is enabled through one or more sources: Config Sync, KUBE, or Cloud integrations.
The certificates that must be blocked from main inventory are available in Excluded Certificates inventory.

Go to Menu > KUBE > VISIBILITY > Client > Excluded Certificates, and verify that the certificate(s) to be excluded are already present.
The target certificate entries are confirmed in Excluded Certificates inventory.
Trigger or wait for certificate ingestion from Config Sync, KUBE, or Cloud integration.
Certificate ingestion processing is initiated for incoming certificates.
Go to Menu > KUBE > VISIBILITY > Client > All, and search for the excluded certificate(s).
The excluded certificate entries are not added to the main inventory.
Validate operational status or logs for the ingestion run, if required by your workflow.
The ingestion run completes without adding excluded certificates to the main inventory.

Certificates listed in Excluded Certificates inventory are filtered out when they enter AppViewX through Config Sync, KUBE, or Cloud integrations, and are not created in main certificate inventory.

Note: If an excluded certificate appears in main inventory, review exclusion entry accuracy and ingestion source mapping before rerunning discovery or sync.

AppViewX