Retire defunct CorpSec functions and realign Corporate IT documentation

/content/handbook/engineering/data-engineering/database-excellence/database-health/ @alexives

^[eta]

/content/handbook/eta @marc_disabatino @nitin-garg @rpollak1

/content/handbook/eta @rpollak1 @nitin-garg

/content/handbook/eta/ai/ @simon_mansfield @mattmangia

/content/handbook/eta/arb/ @mnarayan-gl @rpollak1

/content/handbook/company/infrastructure-standards/ @gitlab-com/gl-security/identity/infra

^[it]

/content/handbook/it/ @dzhu-gl @smanzuik @bill_staples

/content/handbook/it/ @dzhu-gl @lenny-glab @bill_staples

^[legal]

/content/handbook/legal/ @robin @craigpatrick

^[security]

/content/handbook/security/ @cibericua @jdicken @bill_staples @cynthiamiller @cmazal

/content/handbook/security/corporate/ @smanzuik @dzhu-gl

/content/handbook/security/corporate/systems/okta/ @gitlab-com/gl-security/corp/identity @smanzuik @dzhu-gl @gbowen1 @jwong6 @ErikLentz @jacobdwaters @sladgrove @mspry_gl

/content/handbook/security/corporate/systems/google/ @gitlab-com/gl-security/corp/identity @smanzuik @dzhu-gl @gbowen1 @jwong6 @ErikLentz @jacobdwaters @sladgrove @mspry_gl

/content/handbook/security/corporate/systems/lumos/ @gitlab-com/gl-security/corp/identity @smanzuik @dzhu-gl @gbowen1 @jwong6 @ErikLentz @jacobdwaters @sladgrove @mspry_gl

/content/handbook/security/corporate/systems/slack/ @gitlab-com/gl-security/corp/identity @smanzuik @dzhu-gl @gbowen1 @jwong6 @ErikLentz @jacobdwaters @sladgrove @mspry_gl

/content/handbook/security/corporate/ @lenny-glab @dzhu-gl

/content/handbook/security/corporate/systems/okta/ @gitlab-com/gl-security/corp/identity @lenny-glab @dzhu-gl @gbowen1 @jwong6 @ErikLentz @jacobdwaters @sladgrove @mspry_gl

/content/handbook/security/corporate/systems/google/ @gitlab-com/gl-security/corp/identity @lenny-glab @dzhu-gl @gbowen1 @jwong6 @ErikLentz @jacobdwaters @sladgrove @mspry_gl

/content/handbook/security/corporate/systems/lumos/ @gitlab-com/gl-security/corp/identity @lenny-glab @dzhu-gl @gbowen1 @jwong6 @ErikLentz @jacobdwaters @sladgrove @mspry_gl

/content/handbook/security/corporate/systems/slack/ @gitlab-com/gl-security/corp/identity @lenny-glab @dzhu-gl @gbowen1 @jwong6 @ErikLentz @jacobdwaters @sladgrove @mspry_gl

/content/handbook/eta/css/ @jcolyer @dtragjasi @secole

/content/handbook/security/identity/ @gitlab-com/gl-security/corp/identity @smanzuik @dzhu-gl

/content/handbook/security/identity/ @gitlab-com/gl-security/corp/identity @lenny-glab @dzhu-gl

/content/handbook/security/product-security/ @cmazal

/content/handbook/security/product-security/infrastructure-security/ @jacobjernigan

/content/handbook/security/product-security/data-security/ @jacobjernigan @boconnor @jcamgl

/content/handbook/security/security-assurance/ @cynthiamiller

/content/handbook/security/security-operations/ @cibericua @mmulatu @mcoons @mjozenazemian @cablett

/content/handbook/security/security-operations/security-logging/ @darynwilkinson

/content/handbook/security/threat-management/ @smanzuik @estrike

/content/handbook/security/threat-management/ @dzhu-gl @lenny-glab @estrike

/content/handbook/security/threat-management/identity/ @gitlab-com/gl-security/identity

/content/handbook/security/security-operations/red-team/ @cablett

/content/handbook/security/security-operations/threat-intelligence/ @cibericua

/content/handbook/total-rewards/compensation/ @rallen3 @amccrank

^[tools-and-tips]

/content/handbook/tools-and-tips/ai/ @dnsmichi @panand3 @smanzuik @dfrhodes @manav-gl

/content/handbook/tools-and-tips/ai/ @dnsmichi @panand3 @dzhu-gl @lenny-glab @dfrhodes @manav-gl

^[workspace-devfile]

/.devfile.yaml @zhaochen_li

/content/handbook/people-group/offboarding/offboarding_standards.md @boconnor @gitlab-com/egroup @gitlab-com/content-sites

/content/handbook/people-policies/_index.md @emilyplotkin @rallen3 @gitlab-com/egroup @gitlab-com/content-sites @JohnnieJones

/content/handbook/security/controlled-document-procedure.md @gitlab-com/egroup @gitlab-com/content-sites @bill_staples @cynthiamiller @cmazal

/content/handbook/security/corporate/end-user-services/access-requests/_index.md @mnarayan-gl @gitlab-com/egroup @gitlab-com/content-sites @smanzuik @rpollak1

/content/handbook/security/isms.md @cynthiamiller @gitlab-com/egroup @gitlab-com/content-sites @bill_staples @cmazal

/content/handbook/security/policies_and_standards/cryptographic-standard.md @cynthiamiller @jdicken @smanzuik @mloveless @gitlab-com/egroup @gitlab-com/content-sites @bill_staples

/content/handbook/eta/corporate-it/end-user-services/access-requests/_index.md @mnarayan-gl @gitlab-com/egroup @gitlab-com/content-sites @dzhu-gl @lenny-glab @rpollak1

/content/handbook/security/isms.md @corey-oas @cynthiamiller @gitlab-com/egroup @gitlab-com/content-sites @bill_staples @cmazal

/content/handbook/security/policies_and_standards/cryptographic-standard.md @cynthiamiller @jdicken @dzhu-gl @lenny-glab @gitlab-com/egroup @gitlab-com/content-sites @bill_staples

/content/handbook/security/policies_and_standards/data-classification-standard.md @emccrann @gitlab-com/egroup @gitlab-com/content-sites @bill_staples @cynthiamiller @cmazal @madlake

/content/handbook/security/policies_and_standards/password-standard.md @gitlab-com/egroup @gitlab-com/content-sites @bill_staples @cynthiamiller @cmazal

/content/handbook/security/policies_and_standards/physical-security-standard-for-company-assets.md @jdicken @gitlab-com/egroup @gitlab-com/content-sites @bill_staples @cynthiamiller @cmazal

### Granting others maintain access

Do not grant people maintainer access without an [Access Request](/handbook/security/corporate/end-user-services/access-requests/access-requests/). As a maintainer you have the ability to grant others maintainer access. Don't do so without following the Access Request process to garner the appropriate approvals and create the necessary documentation.

Do not grant people maintainer access without an [Access Request](/handbook/eta/corporate-it/end-user-services/access-requests/access-requests/). As a maintainer you have the ability to grant others maintainer access. Don't do so without following the Access Request process to garner the appropriate approvals and create the necessary documentation.

### Description Templates for Issues and Merge Requests

Many finance systems that are provisioned are also considered a SOX system and are subject to the [SOX Program.](https://internal.gitlab.com/handbook/internal-audit/sarbanes-oxley/)

The finance systems admin team goes through additional procedures when handling [Access Requests.](/handbook/security/corporate/end-user-services/access-requests/access-requests/)

The finance systems admin team goes through additional procedures when handling [Access Requests.](/handbook/eta/corporate-it/end-user-services/access-requests/access-requests/)

This applies to the following systems:

### Additional Procedures

On top of the [GitLab Access Request](/handbook/security/corporate/end-user-services/access-requests/#individual-or-bulk-access-request) process, the team will perform the following:

On top of the [GitLab Access Request](/handbook/eta/corporate-it/end-user-services/access-requests/#individual-or-bulk-access-request) process, the team will perform the following:

- Ensure/Clarify access being requested is specific to the system being requested.

  - Example: Instead of `Needs read only access to Netsuite`, the team will clarify with the requester that they are asking for the `Custom Auditor (read only)` role in Netsuite.

  - See matrix [here](/handbook/business-technology/enterprise-applications/finsys-access-requests/#-system-specific-access-request-requirements) for System specific requirements.

- Seek Business Owner's approval of the exact role and/or permission being requested, according to who is listed in the [Tech Stack.](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) This includes [baseline entitlement(s).](https://internal.gitlab.com/handbook/security/corporate/end-user-services/access-request/baseline-entitlements/)

- Seek Business Owner's approval of the exact role and/or permission being requested, according to who is listed in the [Tech Stack.](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) This includes [baseline entitlement(s).](https://internal.gitlab.com/handbook/eta/corporate-it/end-user-services/access-request/baseline-entitlements/)

- Once approved, the team will provision the user in the system and add to the corresponding Okta Google group (if necessary).

- Once provisioned, the team will take a screenshot of the user record in the system with a timestamp and attach it to the issue and then close.

- [Expenses](/handbook/finance/expenses/)

- [Payroll (US & Non-US)](/handbook/finance/payroll/)

- [Sales Commissions](https://internal.gitlab.com/handbook/sales/sales-commission/#fy23-sales-commission-policies)

- [CorpSec End User Services](/handbook/security/corporate/end-user-services/)

- [CorpSec End User Services](/handbook/eta/corporate-it/end-user-services/)

- [Enterprise Applications](/handbook/business-technology)

## How do I use HelpLab?

### Access Requests

Please review our [Access Requests handbook page](/handbook/security/corporate/end-user-services/access-requests/access-requests/) to find more information on how to request access to systems. Choose the right template for your use case and follow the instructions.

Please review our [Access Requests handbook page](/handbook/eta/corporate-it/end-user-services/access-requests/access-requests/) to find more information on how to request access to systems. Choose the right template for your use case and follow the instructions.

### Procurement