Updated AWS tagging

Update source/manuals/aws-tagging.html.md.erb Co-authored-by: James Robinson <[email protected]> changed Directorate to Product
alphagov · Nov 3, 2023 · 0a69296 · 0a69296
1 parent c667f7e
commit 0a69296
Showing 1 changed file with 8 additions and 10 deletions.
diff --git a/source/manuals/aws-tagging.html.md.erb b/source/manuals/aws-tagging.html.md.erb
@@ -1,7 +1,7 @@
 ---
 title: Tagging AWS resources
-last_reviewed_on: 2022-09-16
-review_in: 6 months
+last_reviewed_on: 2023-10-30
+review_in: 12 months
 ---
 
 # <%= current_page.data.title %>
@@ -36,22 +36,20 @@ Currently, we do not enforce tags.
 
 In future, we may wish to consider mechanisms such as alerting on untagged resources, or automatically deleting untagged resources.
 
-## Tags used in GOV.UK Sign In
-
-GOV.UK Sign In is using the following tags:
-
 ### Mandatory
 
- - `Product`: should be `GOV.UK Sign In`
- - `System`: the name of the software system, for example `Authentication` or `Identity proofing and verification core`. Avoid abbreviations.
+ - `Product`: for example `GOV.UK` or `DSP`
+ - `System`: the name of the software system (for example `Authentication` or `Identity proofing and verification core`. Avoid abbreviations)
+ - `Service`: used to describe the function of a particular resource (for example: `account management`, `session storage`, `front end`)
  - `Environment`: should be one of `production`, `staging`, `integration`, or `development`.
  - `Owner`: an email address for an owner for the resource. For dev environments, this will be an individual email address; elsewhere it will be a group address.
 
 ### Optional
 
- - `Service`: used to describe the function of a particular resource (for example: account management, session storage, front end)
- - `Name`: a name for this particular resource. This should be unique within a deployment (terraform deployment, cloudformation stack, etc)
  - `Source`: the URL(s) for any source code repositories related to this resource, separated by spaces
+ - `Exposure` : should specify the level of exposure the resource has to determine its attack surface area. (for example `internal` or `external`)
+ - `Data Classification` : should specify the highest data classification level the resource handles. This will help internal security teams to know what level of controls to apply and help focus on the resources with greatest level of risk.
+ - `Cost Centre` : helps the organisation's accounting or financial management system to track and allocate expenses or costs to specific departments, teams, projects, or functions
 
 ## References