Commit fa505536 authored by Vitor Meireles De Sousa's avatar Vitor Meireles De Sousa 🌀 Committed by Marc Di Sabatino
Browse files

Changes appsec links and pages location to be within SPA

parent eb6983ea
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -583,7 +583,7 @@ content/handbook/people-group/time-off-and-absence/ @amccrank @dparsonage @vanes
/content/handbook/security/product-security/ @juliedavila
/content/handbook/security/product-security/infrastructure-security/ @jacobjernigan
/content/handbook/security/product-security/data-security/ @jacobjernigan @boconnor @jcamgl
/content/handbook/security/product-security/application-security/ @juliedavila
/content/handbook/security/product-security/security-platforms-architecture/application-security/ @vdesousa
/content/handbook/security/product-security/security-platforms-architecture/ @jdicken
/content/handbook/security/product-security/security-platforms-architecture/security-architecture/ @jdicken
/content/handbook/security/product-security/security-platforms-architecture/security-research/ @jdicken
+1 −1
Original line number Diff line number Diff line
@@ -109,7 +109,7 @@ For any infrastructure services related to business operations and our tech stac

New SaaS applications should go through the [Procurement Process](/handbook/finance/procurement/) and are managed by the respective department's [system owners](/handbook/business-technology/#cross-department-system-owners).

Self-hosted application infrastructure is determined on a case-by-case basis and is architected in collaboration with CorpSec Infrastructure, [Infrastructure Security](/handbook/security/product-security/infrastructure-security/), [Application Security](/handbook/security/product-security/application-security/), and [3rd Party Risk](/handbook/security/security-assurance/security-risk/third-party-risk-management/). Please tag `@vlad` in an issue for preliminary guidance on new services. If you do not have an issue yet, please create one in the [CorpSec Infrastructure issue tracker](https://gitlab.com/gitlab-com/gl-security/corp/issue-tracker/-/issues).
Self-hosted application infrastructure is determined on a case-by-case basis and is architected in collaboration with CorpSec Infrastructure, [Infrastructure Security](/handbook/security/product-security/infrastructure-security/), [Application Security](/handbook/security/product-security/security-platforms-architecture/application-security/), and [3rd Party Risk](/handbook/security/security-assurance/security-risk/third-party-risk-management/). Please tag `@vlad` in an issue for preliminary guidance on new services. If you do not have an issue yet, please create one in the [CorpSec Infrastructure issue tracker](https://gitlab.com/gitlab-com/gl-security/corp/issue-tracker/-/issues).

#### Accessing your AWS Account

+2 −2
Original line number Diff line number Diff line
@@ -44,8 +44,8 @@ great results by using it.
- Lower the entry barrier for creating a proposal in a blueprint.
- Establish criteria for when a blueprint should be used.
- Identify cross-functional touchpoints and consolidate upstream processes like
  [production readiness](/handbook/engineering/infrastructure-platforms/production/readiness.md),
  [AppSec reviews](/handbook/security/product-security/application-security/runbooks/review-process),
  [production readiness](/handbook/engineering/infrastructure-platforms/production/readiness/),
  [AppSec reviews](/handbook/security/product-security/security-platforms-architecture/application-security/runbooks/review-process),
  and [creation of release posts](/handbook/marketing/blog/release-posts/).
- Develop strategy for incorporating this process and the Engineering roadmap into Product planning
  and prioritization via the [Cross-functional Prioritization](/handbook/product/product-processes/cross-functional-prioritization/) framework.
+1 −1
Original line number Diff line number Diff line
@@ -54,7 +54,7 @@ The following members of other functional teams are our stable counterparts:
| Technical Writing | {{< member-by-name "Uma Chandran" >}}                                                |
| UX                | TBD                                                                                  |
| Support           | [TBD](/handbook/support/support-stable-counterparts/)                                |
| AppSec            | [TBD](/handbook/security/product-security/application-security/stable-counterparts/) |
| AppSec            | [TBD](/handbook/security/product-security/security-platforms-architecture/application-security/stable-counterparts/) |

## How We Work

+46 −0
Original line number Diff line number Diff line
---
title: "Context Systems Group"
description: The Context Systems Group is part of the AI Engineering organization focused on context gathering tools used to power our AI systems
---

## Team Overview

The Context Systems Group is part of the AI Engineering organization focused on context gathering tools used to power our AI systems.

## Our Projects

The Context Systems team owns and is actively working on the following projects:

- [Knowledge Graph](/handbook/engineering/architecture/design-documents/gitlab_knowledge_graph/) - Semantic understanding and relationships within codebases.
- [Codebase Semantic Indexing](/handbook/engineering/ai/ai-coding/codebase_semantic_indexing.md) - Advanced code search and discovery capabilities using embeddings.
- [Repository X-Ray](/handbook/engineering/ai/ai-coding/repository_xray.md) - Repository analysis and metadata extraction for enhanced code suggestions context.
- [Duo Context Exclusion](/handbook/engineering/ai/ai-coding/duo_context_exclusion.md) - Filtering of sensitive or irrelevant code context.

## Contact Us

Use this information to connect with the Context Systems group:

| Category                 | Name                                  |
|--------------------------|---------------------------------------|
| GitLab Team Handle       | @gitlab-org/code-creation/engineers   |
| Slack Channel            | #g_context_systems                    |

## Team Members

The following people are permanent members of the Context Systems Team:

{{< team-by-manager-slug manager="mnohr" team="Context Systems">}}

You can reach the whole team on GitLab issues/MRs by using the `@gitlab-org/code-creation/engineers` handle.

## Stable Counterparts

The following members of other functional teams are our stable counterparts:

| Category          | Counterpart                                                                          |
|-------------------|--------------------------------------------------------------------------------------|
| Product Manager   | {{< member-by-name "Meg Corren" >}}                                                |
| Technical Writing | {{< member-by-name "Ashraf Khamis" >}}                                                |
| UX                | TBD                                                                                  |
| Support           | [TBD](/handbook/support/support-stable-counterparts/)                                |
| AppSec            | [TBD](/handbook/security/product-security/security-platforms-architecture/application-security/stable-counterparts/) |
Loading