소스 정보
- 저장소
- CyberStrikeus/CyberStrike
- 최근 소스 활동
- 2026년 4월 22일 14:54
- 감지된 SKILL.md 언어
- 영어
- 스타
- 1,653
- 포크
- 254
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-apache24-4-2명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
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
| name | cis-apache24-4.2 |
| description | Ensure Appropriate Access to Web Content Is Allowed |
| category | cis-apache |
| version | 2.3.0 |
| author | cyberstrike-official |
| tags | ["cis","apache","linux","access-control"] |
| cis_id | 4.2 |
| cis_benchmark | CIS Apache HTTP Server 2.4 Benchmark v2.3.0 |
| tech_stack | ["linux","apache"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
In order to serve Web content, either the Apache Allow directive or the Require directive will need to be used to allow for appropriate access to directories, locations and virtual hosts that contain web content.
Either the Allow or Require directives may be used within a directory, a location or other context to allow appropriate access. Access may be allowed to all, or to specific networks, or hosts, or users as appropriate. The Allow/Deny/Order directives are deprecated and should be replaced by the Require directive. It is also recommended that either the Allow directive or the Require directive be used, but not both in the same context.
Perform the following to determine if the recommended state is implemented:
httpd.conf and any included configuration files) to find all <Directory> and <Location> elements.Use the deprecated Order/Deny/Allow method:
Order directive with the value of Deny,Allow for each.Allow and Deny directives, have values that are appropriate for the purposes of the directory.Use the Require method:
Order/Deny/Allow directives are NOT used for the directory.The following command may be useful to extract <Directory> and <Location> elements and Allow directives from the Apache configuration files.
# perl -ne 'print if /^ *<Directory */i .. //<\/Directory>/i'
$APACHE_PREFIX/conf/httpd.conf $APACHE_PREFIX/conf.d/*.conf
# perl -ne 'print if /^ *<Location */i .. //<\/Location>/i'
/conf/httpd.conf /conf.d/*.conf
/conf.d/*.conf
Perform the following to implement the recommended state:
httpd.conf and any included configuration files) to find all <Directory> and <Location> elements. There should be one for the document root and any special purpose directories or locations. There are likely to be access control directives in other contexts, such as virtual hosts or special elements like <Proxy>.Require directives, with values that are appropriate for the purposes of the directory.The configurations below are just a few possible examples.
<Directory "/var/www/html/">
Require ip 192.169.
</Directory>
<Directory "/var/www/html/">
Require all granted
</Directory>
<Location /usage>
Require local
</Location>
<Location /portal>
Require valid-user
</Location>
The following is the default Web root directory configuration:
<Directory "/usr/local/apache2/htdocs">
. . .
Require all granted
. . .
</Directory>
Controls Version: v8
Controls Version: v7