> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/asset-managment/asset-classes/security-services-assets.md). # Security services assets Navigate to **Inventory > All Assets > Security Services > All Security Services Assets** to access a complete, centralized overview of the security services being actively managed within your organization. A Security Service Asset is a specific class of asset within the inventory that represents the actual security configurations, policies, and managed services deployed to protect your cloud environment. Rather than representing the infrastructure that needs protection, such as a compute instance or storage bucket, these assets represent the mechanisms doing the protecting. Examples of these assets include cloud-native security controls like AWS KMS Key Rotation Status and Google Binary Authorization Policy. The system tracks these assets to provide a complete, centralized overview of the security services being actively managed within your environment, ensuring your defensive infrastructure remains active, properly configured, and uncompromised. You can review these assets to ensure your core security mechanisms are functioning correctly and have not been tampered with. Because these assets are continuously enriched with posture and threat data, you can quickly identify, prioritize, and resolve active threats or misconfigurations directly impacting your managed security services. For example, if an encryption key rotation policy is disabled or a binary authorization policy is misconfigured, you can view a direct breakdown of any related cases, issues, and findings tied to that specific security service to immediately remediate the gap in your defenses. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/asset-managment/asset-classes/security-services-assets.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.