用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-gcp-foundations-1-15命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
基于 SOC 职业分类
正在显示 SKILL.md
| name | cis-gcp-foundations-1.15 |
| description | Ensure API Keys Are Rotated Every 90 Days |
| category | cis-gcp-foundations |
| version | 4.0.0 |
| author | cyberstrike-official |
| tags | ["cis","gcp","iam","api-keys"] |
| cis_id | 1.15 |
| cis_benchmark | CIS Google Cloud Platform Foundation Benchmark v4.0.0 |
| tech_stack | ["gcp"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
API Keys should only be used for services in cases where other authentication methods are unavailable. If they are in use it is recommended to rotate API keys every 90 days.
Security risks involved in using API-Keys are listed below:
Because of these potential risks, Google recommends using the standard authentication flow instead of API Keys. However, there are limited cases where API keys are more appropriate. For example, if there is a mobile application that needs to use the Google Cloud Translation API, but doesn't otherwise need a backend server, API keys are the simplest way to authenticate to that API.
Once a key is stolen, it has no expiration, meaning it may be used indefinitely unless the project owner revokes or regenerates the key. Rotating API keys will reduce the window of opportunity for an access key that is associated with a compromised or terminated account to be used.
API keys should be rotated to ensure that data cannot be accessed with an old key that might have been lost, cracked, or stolen.
Regenerating Key may break existing client connectivity as the client will try to connect with older API keys they have stored on devices.
APIs & Services\Credentials using https://console.cloud.google.com/apis/credentialsAPI Keys, for every key ensure the creation date is less than 90 days.To list keys, use the command:
gcloud services api-keys list
Ensure the date in createTime is within 90 days.
All API keys should have a createTime within the last 90 days, indicating they have been rotated.
APIs & Services\Credentials using https://console.cloud.google.com/apis/credentialsAPI KeysAPI Key NameREGENERATE KEY to rotate API key.Save.Note: Do not set HTTP referrers to wild-cards (_ or _.[TLD] or .[TLD]/) allowing access to any/wide HTTP referrer(s). Do not set IP addresses and referrer to any host (0.0.0.0 or 0.0.0.0/0 or ::0).
There is not currently a way to regenerate an API key using gcloud commands. To 'regenerate' a key you will need to create a new one, duplicate the restrictions from the key being rotated, and delete the old key.
gcloud services api-keys list
Note the UID and restrictions of the key to regenerate.
Run this command to create a new API key. <key_name> is the display name of the new key:
gcloud services api-keys create --display-name="<key_name>"
Note the UID of the newly created key.
Note - the restriction may vary for each key. Refer to this documentation for the appropriate flags: https://cloud.google.com/sdk/gcloud/reference/services/api-keys/update
gcloud services api-keys update <UID of new key>
gcloud services api-keys delete <UID of old key>
API keys do not have an automatic rotation mechanism.
There is no option to automatically regenerate (rotate) API keys periodically.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 16.10 Apply Secure Design Principles in Application Architectures | x | x | |
| v7 | 0.0 Explicitly Not Mapped |