> ## 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 management
export const DefinitionDescription = ({children}) => {children};
export const DefinitionTerm = ({children}) => {children};
export const DefinitionList = ({children}) => {children}
;
export const Comments = ({children}) => {
return ;
};
Environment logging gives administrators visibility into the packages 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) associated with those packages
* Identify which member environments are affected by a specific CVE
* Block environments from use and provide remediation guidance
## Enabling environments
Environment logging is not enabled by default. You can enable **Environments** for your organization in [Organization Settings](/anaconda-platform/cloud/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.
`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.
```
## 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** under Org Management.
### 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.
## Scanning environments
Scanning checks the most recently saved environment log for CVEs associated with its packages.
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**.
## Investigating environments
### Viewing packages
Click the package count in the **PACKAGES** column to see which packages are installed in an environment and what channels they were sourced from.
Use the navigation controls at the bottom to browse the environment's packages.
### Viewing 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.
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.
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](/anaconda-platform/cloud/user/unified-search) bar at the top of the page. Results include every environment containing packages associated with that CVE.
## 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**.
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**.
Archived environments are still available for use. To prevent an environment from being used, [block it](#blocking-environments).