用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-gcp-foundations-1-14命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 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.14 |
| description | Ensure API Keys Are Restricted to Only APIs That Application Needs Access |
| category | cis-gcp-foundations |
| version | 4.0.0 |
| author | cyberstrike-official |
| tags | ["cis","gcp","iam","api-keys"] |
| cis_id | 1.14 |
| 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. API keys are always at risk because they can be viewed publicly, such as from within a browser, or they can be accessed on a device where the key resides. It is recommended to restrict API keys to use (call) only APIs required by an application.
Security risks involved in using API-Keys are below:
In light 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.
In order to reduce attack surfaces by providing least privileges, API-Keys can be restricted to use (call) only APIs required by an application.
Setting API restrictions may break existing application functioning, if not done carefully.
APIs & Services\Credentials using https://console.cloud.google.com/apis/credentialsAPI Keys, Click the API Key Name. The API Key properties display on a new page.Key restrictions parameter API restrictions is not set to None.Or,
Ensure API restrictions is not set to Google Cloud APIs. Note: Google Cloud APIs represents the API collection of all cloud services/APIs offered by Google cloud.
gcloud services api-keys list
Each key should have a line that says restrictions: followed by varying parameters and NOT have a line saying - service: cloudapis.googleapis.com as shown here:
restrictions:
apiTargets:
- service: cloudapis.googleapis.com
All API keys should have API restrictions configured to only the specific APIs required by the application. No key should be unrestricted or set to Google Cloud APIs.
APIs & Services\Credentials using https://console.cloud.google.com/apis/credentialsAPI Keys, Click the API Key Name. The API Key properties display on a new page.Key restrictions section go to API restrictions.Select API drop-down to choose an API.Save.Note: Do not set API restrictions to Google Cloud APIs, as this option allows access to all services offered by Google cloud.
gcloud services api-keys list
Note the UID of the key to add restrictions to.
Run the update command with the appropriate API target service or flags file with API target services and methods to add the required restrictions.
Command with appropriate API target service:
gcloud services api-keys update <UID> --api-target=service=<service>
Command with flags file:
gcloud services api-keys update <UID> --flags-file=<flags_file>.yaml
Content of flags file:
- --api-target:
service: "foo.service.com"
- --api-target:
service: "bar.service.com"
methods:
- "foomethod"
- "barmethod"
Note: Flags can be found by running:
gcloud services api-keys update --help
Note: Services can be found by running:
gcloud services list
or in this documentation: https://cloud.google.com/sdk/gcloud/reference/services/api-keys/update
By default, API restrictions are set to None.
| 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 |