> ## 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 scanning
export const DefinitionDescription = ({children}) => {children};
export const DefinitionTerm = ({children}) => {children};
export const DefinitionList = ({children}) => {children}
;
export const GCell = ({children, className}) =>
{children}
;
export const GTH = ({children, className}) =>
{children}
;
export const GRow = ({children}) => {children}
;
export const GBody = ({children}) => {children}
;
export const GHead = ({children}) => {children}
;
export const GTable = ({children, className, cols}) =>
{children}
;
export const Comments = ({children}) => {
return ;
};
Environment logging gives you visibility into the security posture of your local conda environments. With environment logging enabled, you can view the packages installed in your environments, identify Common Vulnerabilities and Exposures (CVEs) associated with them, and proactively address security issues before administrator intervention.
## Enabling environments
If an administrator has enabled environments for your organization, running `anaconda login` prompts you to install the `anaconda-env-manager` metapackage and register your machine with your organization.
After setup, conda automatically logs any environment you create or update.
`anaconda-env-log`
Automatically logs the current state of an environment whenever you perform 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 you 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 you 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.
```
If you belong to multiple organizations, you are prompted to select one from the list before registration completes.
## Logging environments
Environments that you created prior to setup can be manually logged with your organization:
```sh theme={null}
anaconda env-log log --name
```
Replace \ with the name of the environment you want to log to your organization.
## Viewing your environments
To view environments you've logged to your organization, select **Environments** under Org Management.
You can only view environments that you've logged to your organization.
### 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.
## 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.
```sh theme={null}
anaconda audit scan [OPTIONS]
```
Option
Description
`--name, -n`
Scan an environment by name (uses default conda environment path prefix)
`--prefix, -p`
Scan an environment at a specific path
`--affected-only`
Only display packages that have CVE matches
`--json`
Output results in JSON format (disables summary table)
`--no-include-cleared`
Exclude cleared CVEs from results
`--no-include-mitigated`
Exclude mitigated CVEs from results
**Reading scan results:**
Scan output includes a package table and a summary matrix of CVE counts by severity level.
* Color indicates [CVE severity](/anaconda-platform/cloud/admin/cve#common-vulnerability-scoring-system-cvss)
* ✓ indicates the CVE has undergone [Anaconda curation](/anaconda-platform/cloud/admin/cve#cve-statuses)
* ~~Strikethrough~~ indicates a cleared CVE that is safe to use
Scan an environment that has been logged with your organization to get an updated list of CVEs:
1. Select **Environments** from the left-hand navigation.
2. Select the environment you want to scan.
3. Click **Update Scan**.
## Investigating environments
### Viewing packages
Click the package count under 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.
### Checking environments for vulnerabilities
To check if any of your environments 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 environments you've logged that contain packages associated with the CVE you're searching for.
