OpenParable
Skip to content
← Back to skills

T1213.003_code-repositories

DevOps & Security

Adversaries may leverage code repositories to collect valuable information.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/mitre_attack/TA0009_collection/T1213.003_code-repositories/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/t1213-003-code-repositories, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

T1213.003 Code Repositories

Sub-technique of: T1213

High-Level Description

Adversaries may leverage code repositories to collect valuable information. Code repositories are tools/services that store source code and automate software builds. They may be hosted internally or privately on third party sites such as Github, GitLab, SourceForge, and BitBucket. Users typically interact with code repositories through a web application or command-line utilities such as git.

Once adversaries gain access to a victim network or a private code repository, they may collect sensitive information such as proprietary source code or Unsecured Credentials contained within software's source code. Having access to software's source code may allow adversaries to develop Exploits, while credentials may provide access to additional resources using Valid Accounts.

Note: This is distinct from Code Repositories, which focuses on conducting Reconnaissance via public code repositories.

Kill Chain Phase

  • Collection (TA0009)

Platforms: SaaS

What to Check

  • Identify if Code Repositories technique is applicable to target environment
  • Check SaaS systems for indicators of Code Repositories
  • Verify mitigations are bypassed or absent (4 known mitigations)
  • Assess detection coverage (1 detection strategies)

How to Test

Manual Testing

  1. Identify Attack Surface: Determine if the target environment is susceptible to Code Repositories by examining the target platforms (SaaS).

  2. Assess Existing Defenses: Review whether mitigations for T1213.003 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

  3. Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.

Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.

Remediation Guide

M1017 User Training

Develop and publish policies that define acceptable information to be stored in code repositories.

M1047 Audit

Consider periodic reviews of accounts and privileges for critical and sensitive code repositories. Scan code repositories for exposed credentials or other sensitive information.

M1018 User Account Management

Enforce the principle of least-privilege. Consider implementing access control mechanisms that include both authentication and authorization for code repositories.

M1032 Multi-factor Authentication

Use multi-factor authentication for logons to code repositories.

Detection

Detecting Bulk or Anomalous Access to Private Code Repositories via SaaS Platforms

Risk Assessment

FindingSeverityImpact
Code Repositories technique applicableHighCollection

CWE Categories

CWE IDTitle
CWE-200Exposure of Sensitive Information

References