# Ensure Resources Carry Required Tags

- Source: https://support.icompaas.com/support/solutions/articles/a_1791826035145532-ensure-resources-carry-required-tags
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [OVH Cloud](https://support.icompaas.com/support/solutions/c_1791819364512367) › [checks](https://support.icompaas.com/support/solutions/folders/f_1791819376721251)
- Last updated: 2026-10-12
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description**

Ensure OVHcloud resources carry the tags required by the organization, such as environment, owner, application, and cost center, so every resource can be identified, managed, and covered by tag-based IAM policies.

**Rationale**

Untagged resources are hard to assign to an owner, review, or include in cost reports, and they are often forgotten. Tags also allow IAM policies to grant access based on tags. Consistent tagging improves accountability, security reviews, and cost control.

**Impact**

-   Every resource has a known owner and purpose
    
-   Supports tag-based IAM policies and cost reports
    
-   Existing resources must be tagged
    

**Default Value**

By default, resources have no custom tags.

**Pre-Requisites**

-   Permission to manage the resources
    
-   A defined list of required tags
    

**Test Plan**

1.  Log in to the OVHcloud Control Panel at [https://www.ovh.com/manager/](https://www.ovh.com/manager/).
    
2.  In the left-hand menu, select Identity, Security & Operations.
    
3.  Open the resources list in Identity and Access Management and review the tags on each resource.
    
4.  Alternatively, use the OVHcloud API console at [https://eu.api.ovh.com/console/](https://eu.api.ovh.com/console/) (or your region's console). Run GET /iam/resource and check the tags of each resource.
    
5.  If any resource is missing required tags, follow the implementation steps.
    

**Implementation Steps**

1.  Log in to the OVHcloud Control Panel at [https://www.ovh.com/manager/](https://www.ovh.com/manager/).
    
2.  In the left-hand menu, select Identity, Security & Operations.
    
3.  Open the resource in Identity and Access Management and add the required tags.
    
4.  Alternatively, run POST /iam/resource/{resourceURN}/tag in the API console for each tag.
    

**Backout Plan**

1.  Remove the added tag from the resource in the Control Panel, or run DELETE /iam/resource/{resourceURN}/tag/{key}.
    

**Reference**

-   [https://us.ovhcloud.com/identity-security/identity-access-management/](https://us.ovhcloud.com/identity-security/identity-access-management/)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.