> ## Documentation Index > Fetch the complete documentation index at: https://anaconda.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Environment logging and monitoring Business or Custom plans only Environment logging gives administrators visibility into the packages (Software files and information about the software, such as its name, version, and description, bundled into a file that can be installed and managed by a package manager.) installed across member environments and the tools to enforce security standards when vulnerabilities arise. With environment logging enabled, you can: * Monitor packages installed in member environments * View Common Vulnerabilities and Exposures (CVEs (A public identifier for a known security flaw in software, used to track and assess vulnerabilities.)) associated with those packages * Identify which member environments are affected by a specific CVE * Block environments from use and provide remediation guidance ## Enabling environment logging Environment logging is not enabled by default. You can enable **Environments** in [Organization Settings](https://anaconda.com/docs/anaconda-platform/admin/organizations#organization-settings). Once enabled, members are automatically prompted to install the `anaconda-env-manager` metapackage and register their machine with your organization the next time they run `anaconda login`. After setup, conda automatically logs any environment they create or update. > [accordion] Plugins provided by the anaconda-env-manager metapackage > >
>
`anaconda-env-log`
> >
Automatically logs the current state of an environment whenever a member performs a `create`, `install`, `remove`, `rename`, or `update` action with conda. Manual logging of existing environments is also supported.
> >
`anaconda-activate-check`
> >
Validates environments against administrator-defined security controls before activation and notifies members of warnings or access restrictions with guidance for resolution.
> >
`anaconda-audit`
> >
Scans local environments to assess the security impact of actions like installing or updating packages, so members can proactively address potential issues without requiring administrator intervention.
>
```text wrap theme={null} (base) ➜ ~ anaconda login Anaconda Environment Manager is required by your organization. It is recommended to install. Proceed? [y/n] (y): y Installing anaconda-env-manager... ✔︎ anaconda-env-manager installed successfully. Only one organization found, automatically selecting: my-organization Linking this machine to organization my-organization... ✔ This machine is now registered with my-organization. Conda environments will be logged to this organization. ``` ## Environment dashboard Closed Beta - Contact your CSM to participate > [!NOTE] > > Viewing the environment dashboard requires that you have previously established a global environment policy for your organization. See [Environment policies](https://anaconda.com/docs/anaconda-platform/admin/policies.md#environment-policy) for more information. The environment dashboard shows how your organization's environments are performing against the active environment policy: * **Compliant**: No active policy violations * **Warning**: Active policy violations within their SLA remediation window * **Blocked**: Exceeded their SLA remediation window and are prevented from use Select a card to filter the table below. Select it again to clear the filter. > [!NOTE] > > Only one filter can be applied at a time. ![Status cards showing Blocked, Warning, and Compliant environment counts with percentage gauges](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-platform/ap_env_dashboard_status_overview.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=a389e3173c2143063f46a732ba62bb87) The environment status table lists individual environments and their compliance details. Column Description **Name** The environment name and path to the environment on the member's local machine. **Status** The compliance state displayed as a badge. **Package Violations** Which environment packages contain vulnerabilities.\ \[!NOTE] Hover over a warning to see a list of packages that violate the policy and their versions. **Python Version** Whether the environment's Python version meets the policy requirement.\ \[!NOTE] Hover over a warning to see the environment's Python version and why it violates the policy. **License Violations** Whether the environment contains packages with licenses that violate the policy.\ \[!NOTE] Hover over a warning to see which packages have a license violation. **SLA Period** Time remaining before the environment's SLA period expires. > [!TIP] > > Use the controls at the bottom of the table to navigate between pages. ### Compliance trend The **Compliance Trend** chart displays daily counts of environments by compliance status over time as a stacked area chart. Use the dropdown in the upper-right corner of the chart to switch between viewing the **Last 7 days** or the **Last 30 days**. ![Compliance trend chart showing Compliant, Violations, and Blocked lines over 30 days](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-platform/ap_env_dashboard_compliance_trend.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=930156ad0af403171deebd96e3383943) ### Environment alerts Click the alert icon in the top navigation bar to open the Environments Alerts pane. This pane shows a feed of environment-related events across your organization. ![Environments Alerts pane showing event list with filter chips for Blocked, Warning, and Environment Created](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-platform/ap_env_dashboard_alerts.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=0cc9e194d83e25f962ae84a6089557ad) Each alert entry displays: * The event type (Blocked, Warning, or Environment Created) * The environment name * The date the event occurred Use the filter buttons at the top of the pane to show only specific event types. Click **Mark all as read** to clear unread indicators. ## Viewing member environments As an administrator, you have visibility into every environment logged with your organization, including the packages they contain and any CVEs associated with those packages. To view them, select **Environments** from the left-hand navigation. ![View logged environments](https://mintcdn.com/anaconda-29683c67/ghAcs1Rv_eiLtpni/images/anaconda-platform/ap_view_org_environments.png?fit=max\&auto=format\&n=ghAcs1Rv_eiLtpni\&q=85\&s=fb15e842cdac8cab182cc7421405446f) ### Searching and filtering Search for environments by name or path using the search box at the top of the table. You can also filter by platform, user, or a combination of both. ![Environment search and filters](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-platform/ap_env_search_filter.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=ea855db99e76acf15406999b8e0aea55) ## Scanning environments Scanning checks the most recently saved environment log for CVEs associated with its packages. > [!NOTE] > > Environments are automatically scanned when created but not when updated. Perform a scan before investigating an environment to ensure its data is current. 1. Select the environment you want to scan. 2. Click **Update Scan**. ![Update scan button](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-platform/ap_env_scan_in_cloud.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=d6c345b2cd22163d3eb6a10271067a6e) ## Investigating environments ### Viewing packages Click the package count in the **PACKAGES** column to see which packages are installed in an environment and what channels (A location (URL or file path) in a repository where conda looks for packages.) they were sourced from. ![Viewing a logged environment's packages](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-platform/ap_env_pkgs.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=bcc8596e16ceae195e3bf268e273c54b) > [!NOTE] > > Use the navigation controls at the bottom to browse the environment's packages. ### Viewing CVEs > [tab] Environment CVEs > > Click the CVE count in the **CVES** column to view all CVEs associated with an environment. Each entry includes the CVE name, CVSS score, Anaconda curation date, a description, and its current status. > > Use the filters at the top of the page to locate critical CVEs. Select a CVE from the list to view its details. > > ![Viewing a logged environment's CVEs](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-platform/ap_env_cves.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=025f3fe9b54ba0857a24431fa46c5c62) > [tab] Package CVEs > > To view CVEs associated with a specific package: > > 1. Click the package count in the **PACKAGES** column. > 2. Locate the package. > 3. Click the CVE count beside the package. > > Each entry includes the CVE name, CVSS score, Anaconda curation date, a description, and its current status. Select a CVE from the panel to view its details. > > ![CVEs associated with a specific package in a logged environment](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-platform/ap_env_pkg_cves.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=ccced75551d6f8a0229c92c799d8cbe2) > [!NOTE] > > The **active** filter is applied to CVE results by default. ### Identifying environments affected by a CVE To find which environments in your organization are affected by a specific vulnerability, search by CVE ID using the [unified search](https://anaconda.com/docs/anaconda-platform/user/unified-search.md) bar at the top of the page. Results include every environment containing packages associated with that CVE. ![The unified search bar at the top of anaconda.com/app](https://mintcdn.com/anaconda-29683c67/ghAcs1Rv_eiLtpni/images/anaconda-platform/ap_unified_search.png?fit=max\&auto=format\&n=ghAcs1Rv_eiLtpni\&q=85\&s=328d3a861548a4e12847687bbcf1d3af) ## Managing member environments ### Blocking environments If an environment does not meet your organization's security standards, you can warn the member or block access completely. Both options allow you to include a custom message with remediation guidance. Members receive this message the next time they attempt to activate the environment. 1. Select the environment you want to take action on. 2. Click **Update Status**. ![Environment status controls](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-platform/ap_env_status_controls.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=602ac645e214a7b42c6b48d7db66b7ed) 3. Select a status and enter a custom message, if necessary. 4. Click **Save**. ### Unblocking environments After a member remediates the issue, restore access by resetting the environment's status. 1. Select the blocked environment. 2. Click **Update Status**. 3. Click **OK**. 4. Click **Save**. ### Archiving environments Archiving moves inactive or obsolete environments to a dedicated tab, reducing clutter in the active list. 1. Select the environment you want to archive. 2. Click **Archive**. ![Archive environment button](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-platform/ap_env_archive.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=4339d113090b80a8db868aaef3e1d8b9) > [!NOTE] > > Archived environments are still available for use. To prevent an environment from being used, [block it](#blocking-environments).