소스 정보
- 저장소
- CyberStrikeus/CyberStrike
- 최근 소스 활동
- 2026년 4월 13일 04:22
- 감지된 SKILL.md 언어
- 영어
- 스타
- 1,653
- 포크
- 254
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-aws-foundations-2-2명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| name | cis-aws-foundations-2.2 |
| description | Maintain current AWS account contact details |
| category | cis-iam |
| version | 7.0.0 |
| author | cyberstrike-official |
| tags | ["cis","aws","iam","account","contact-details","billing"] |
| cis_id | 2.2 |
| cis_benchmark | CIS AWS Foundations Benchmark v7.0.0 |
| tech_stack | ["aws"] |
| cwe_ids | [] |
| chains_with | ["cis-aws-foundations-2.3"] |
| prerequisites | [] |
| severity_boost | {} |
Ensure contact email and telephone details for AWS accounts are current and mapped to more than one individual in your organization.
An AWS account supports a number of contact details, and AWS will use these to contact the account owner if activity judged to be in breach of the Acceptable Use Policy or indicative of a likely security compromise is observed by the AWS Abuse team. Contact details should not be associated with a single individual, as circumstances may arise where that individual is unavailable. Email contact details should point to a mail alias that forwards messages to multiple individuals within the organization; where feasible, phone contact details should point to a PABX hunt group or other call-forwarding system. In AWS Organizations environments, this applies to all member accounts, not just the management account.
If an AWS account is observed to be behaving in a prohibited or suspicious manner, AWS will attempt to contact the account owner by email and phone using the listed contact details. If this is unsuccessful and the account behavior requires urgent mitigation, proactive measures may be taken, including throttling traffic between the account exhibiting suspicious behavior and AWS API endpoints or the Internet. This may result in impaired service to and from the affected account. Therefore, it is in both the customer's and AWS's best interests to ensure that prompt contact can be established. This is best achieved by configuring AWS account contact details to point to resources that reach multiple individuals, such as email aliases and PABX hunt groups.
Outdated contact details may delay incident response and lead to service disruption.
This activity can only be performed via the AWS Console, with a user who has permission to read and write Billing information (aws-portal:*Billing).
Billing and Cost Management console at https://console.aws.amazon.com/billing/home#/.Account.Contact Information, review and verify the current details.aws account get-contact-information
Expected output format:
{
"AddressLine1": "<AddressLine 1>"
Contact information is current, accurate, and mapped to shared resources (email aliases, group phone numbers) rather than a single individual.
Billing and Cost Management console at https://console.aws.amazon.com/billing/home#/.Account.Account Settings page, next to Account Settings, choose Edit.Edit.Save changes.Done.Contact Information, choose Edit.Update.Run the following command:
aws account get-contact-information '{
"AddressLine1": "<AddressLine 1>",
"AddressLine2": "<AddressLine 2>",
"City": "<City>",
"CompanyName": "<Company Name>",
"CountryCode": "<Country Code>",
"FullName": "<Full Name>",
"PhoneNumber": "<Phone Number>",
"PostalCode": "<Postal Code>",
"StateOrRegion": "<State or Region>"
}'
By default, AWS account contact information (email and telephone) is set to the values provided at account creation. These usually reference a single individual rather than a shared alias or group contact. In AWS Organizations environments, this may vary across accounts unless centrally managed or periodically reviewed.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 17.2 Establish and Maintain Contact Information for Reporting Security Incidents | x | x | x |
| v7 | 19.3 Designate Management Personnel to Support Incident Handling | x | x | x |
Level 1 | Manual
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 직업 분류 기준