{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":44064,"path":"security-management/install-fix-intel.md","title":"Install Fix Intelligence for Security Exposure Management","bundle":null,"doc_type":null,"release":"australia","body":"\n# Install Fix Intelligence for Security Exposure Management\n\nActivate the Fix Intelligence for Security Exposure Management plugin \\(`sn_vul_fix`\\) to add the Fix tables, role, and integration to your USEM environment.\n\n## Before you begin\n\nRole required: admin\n\nPrerequisites:\n\n-   Unified Security Exposure Management and Vulnerability Response, including the Vulnerability Integration Framework, are active on your instance.\n-   Your organization is entitled to Armis Centrix™ for Vulnerability Prioritization and Remediation \\(ViPR\\).\n\n## About this task\n\nActivate the Fix Intelligence for Security Exposure Management plugin to install the Fix tables \\(`sn_vul_fix_intel` and its supporting tables\\), the `sn_vul_fix.read` role, the ingestion scripts, and the registered integration.\n\n## Procedure\n\n1.  Navigate to **All** > **System Definition** > **Plugins**.\n\n2.  In the search field, enter the Fix Intelligence for Security Exposure Management plugin name.\n\n    The plugin scope is `sn_vul_fix`.\n\n3.  Select the plugin, and then select **Install**.\n\n4.  When activation completes, confirm that the Fix tables and the `sn_vul_fix.read` role are present.\n\n    For the full list of what the plugin installs, see [Components installed with Fix Intelligence for Security Exposure Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/fix-intel-components-installed.md).\n\n\n## Result\n\nFix Intelligence for Security Exposure Management is active. The Fix tables, role, and integration are installed on your instance.\n\n## What to do next\n\nNow Support configures the Armis Centrix™ for ViPR integration for your instance. Allow one to two business days after you install the plugin. If the integration is not configured after that time, raise a support case.\n\nYou must also configure inbound authentication. For more information, see [KB article](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3139883).\n\nWhen the integration is configured and the first sync completes, you can review the ingested fixes. See [View fixes in USEM Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/view-fixes-in-workspace.md).\n\n**Parent Topic:**[Fix Intelligence for Security Exposure Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/fix-intel-for-usem-landing.md)\n\n"}}