Skip to content

Commit 3c5bf4b

Browse files
“Jerome“Jerome
authored andcommitted
updated text
1 parent a9fc305 commit 3c5bf4b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/technical-standards/How-to guides/Production Environment Tools & PII Handling.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Covers all development, testing, debugging, or API interaction tools used in pro
2323

2424
Developers must not use third-party tools to access production environments or handle production PII unless they have a clear and documented understanding of how the tool manages, stores, and transmits data, and are satisfied that its use aligns with Hackney’s security and data protection standards.
2525

26-
Where a new tool is approved for use, supporting evidence of this assessment must be recorded in the [Hackney Service Catalogue](https://docs.google.com/spreadsheets/d/1QoinQ9Yvlr4gvUoROYAA8vDWOWyXw7-vokZmPEH296A/edit?gid=1633075159#gid=1633075159).
26+
Where a new tool is approved for use, supporting evidence of this assessment must be recorded in the [Hackney Service Catalogue](https://docs.google.com/spreadsheets/d/1QoinQ9Yvlr4gvUoROYAA8vDWOWyXw7-vokZmPEH296A/edit?gid=1633075159#gid=1633075159) in columns Q to U.
2727

2828
### Approval Process for New Tools
2929

0 commit comments

Comments
 (0)