> For the complete documentation index, see [llms.txt](https://docs.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectra.ai/deployment/getting-started/respond-ux-deployment-guide/recommended-next-steps.md). # Recommended next steps Recommended actions after an initial RUX deployment, including backups, integrations, and deployment best practices. ## Backing up your Brain As discussed earlier in the [Deployment Process Overview](/deployment/getting-started/respond-ux-deployment-guide/deployment.md#deployment-process-overview), the Brain appliance should be backed up by the customer. The Vectra cloud platform stores detections, metadata, and triage filters but the configuration of the Brain is not backed up by Vectra. Care should be taken to ensure backup to a Windows server, SFTP/SCP, or AWS S3 bucket. Please see the following Vectra support portal articles for more details: * [Backup and Restore for Vectra Brain Appliances (v8.5+)](/operations/backup-restore-dr/backup-and-restore-v85.md) * [Vectra Brain Appliance Disaster Recovery (DR) / Migration Recommendations (v8.5+)](/operations/backup-restore-dr/disaster-recovery-and-migration-v85.md) ## Recommended Next Steps Vectra offers a variety of deployment services, consulting, or full MDR options for customers that need more help or expert analyst assistance. Please work with your Vectra account team for additional details. This guide covered initial configuration of basic settings. Some recommended next steps are: * Work on [traffic engineering](/deployment/traffic-engineering-and-validation.md) and getting traffic flowing to your Sensors or mixed mode Brain. * Integrations that help with HostID or add context such as: * [vCenter integration](/configuration/setup/external-connectors/vcenter-integration-vmware.md) if you have a VMware environment * [SIEM Event Forwarding](/configuration/setup/external-connectors/siem-vectra-brain-ingesting-logs.md) * [Windows Event Log ingestion](/configuration/coverage/network-identities-weli/windows-event-log-ingestion-weli.md) * [EDR integration](/configuration/setup/edr-integrations.md) * [AD integration](/configuration/setup/external-connectors/active-directory.md) * Integrations to enable taking action. * [AD](/configuration/setup/external-connectors/active-directory.md) and [EDR](/configuration/setup/edr-integrations.md) integration bring [host](/configuration/response/lockdown/host-lockdown-edr.md) and [account](/configuration/response/lockdown/active-directory-account-lockdown.md) Lockdown capability. * [Entra ID (Azure AD) Account Lockdown](/configuration/response/lockdown/entra-id-azure-ad-account-lockdown-rux.md) works with and Azure AD data source. * Enabling [Stream](/deployment/stream.md). * Setting up [SSO using SAML](/configuration/access/saml-sso-rux.md) if you have not already done so. * Building groups and [triage rules](/configuration/tuning/triage-best-practices.md) to suppress unwanted detections for authorized behaviors. ## Best Practices * Change default passwords for the 'admin' (GUI) and `vectra` (CLI and IPMI/iDRAC) users to strong versions. * See [ssh login process for CLI](/deployment/appliance-operations/ssh-login-process-for-cli.md) for details on accessing the CLI of your Brain appliance. * Passwords must be between 8 and 128 characters and contain at least: 1 number, both lowercase and uppercase letters, and 1 symbol (e.g. \~!@#$%^&\*,.?-\_+=). * Limit exposure to admin interfaces through firewall rules that permit communication only from appropriate nodes/networks (including Vectra required endpoints as well). * IPMI / iDRAC interfaces should be on their own isolated networks when possible. * See [IPMI / iDRAC configuration](/deployment/appliance-operations/ipmi-idrac-configuration.md) for more details. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.vectra.ai/deployment/getting-started/respond-ux-deployment-guide/recommended-next-steps.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.