소스 정보
- 저장소
- CyberStrikeus/CyberStrike
- 최근 소스 활동
- 2026년 4월 13일 11:05
- 감지된 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-azure-foundations-2-1-7명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? 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-azure-foundations-2.1.7 |
| description | Ensure diagnostic log delivery is configured for Azure Databricks |
| category | cis-azure-foundations |
| version | 5.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","databricks","analytics"] |
| cis_id | 2.1.7 |
| cis_benchmark | CIS Microsoft Azure Foundations Benchmark v5.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Azure Databricks Diagnostic Logging provides insights into system operations, user activities, and security events within a Databricks workspace. Enabling diagnostic logs helps organizations:
Diagnostic logging provides visibility into security and operational activities within Databricks workspaces while maintaining an audit trail for forensic investigations, and it supports compliance with regulatory standards that require logging and monitoring.
Logs consume storage and may require additional monitoring tools, leading to increased operational overhead and costs. Incomplete log configurations may result in missing critical events, reducing monitoring effectiveness.
Check if diagnostic logging is enabled for the Databricks workspace:
Azure Databricks.Monitoring > Diagnostic settings.Ensure that logging is enabled for the following categories:
accounts: User account activities.Filesystem: Databricks Filesystem Logs.clusters: Cluster state changes and errors.notebook: Execution events.jobs: Job execution tracking.Verify that logs are being sent to one or more of the following destinations:
Azure Log Analytics workspace: For analysis and querying.Azure Storage Account: For long-term retention.Azure Event Hubs: For integration with SIEM tools.Check if diagnostic logging is enabled for the Databricks workspace:
az monitor diagnostic-settings list --resource <databricks-resource-id>
If the output is empty, no diagnostic settings are configured.
Verify log categories being collected:
az monitor diagnostic-settings show --name <setting-name> --resource <databricks-resource-id>
Review the output to confirm that the necessary log categories are enabled.
Check if logs are stored securely in an approved location:
az monitor diagnostic-settings list --resource <databricks-resource-id>
Review the storageAccountId, workspaceId, and eventHubAuthorizationRuleId fields in the output to confirm the log destinations.
Check if diagnostic logging is enabled for the Databricks workspace:
Get-AzDiagnosticSetting -ResourceId <databricks-resource-id>
An empty result indicates that diagnostic logging is not enabled.
138ff14d-b687-4faa-a81c-898c91a87fa2 - Name: 'Resource logs in Azure Databricks Workspaces should be enabled'Diagnostic settings should be configured with all required log categories enabled. Logs should be delivered to at least one approved destination (Log Analytics, Storage Account, or Event Hubs).
Enable diagnostic logging for Azure Databricks:
Monitoring > Diagnostic settings.+ Add diagnostic setting.Category details, select the log categories you wish to capture, such as AuditLogs, Clusters, Notebooks, and Jobs.Log Analytics workspace: For advanced querying and monitoring.Storage account: For long-term retention.Event Hub: For integration with third-party systems.Name for the diagnostic setting.Save.Implement log retention policies:
General, select Usage and estimated costs.Data Retention.OK.Monitor logs for anomalies:
Azure Monitor.Alerts > + New alert rule.Scope, specify the Databricks resource.Condition based on log queries that identify anomalies (e.g. unauthorized access attempts).Actions to notify stakeholders or trigger automated responses.name and description.Create alert rule.Enable diagnostic logging for Azure Databricks:
az monitor diagnostic-settings create --name "DatabricksLogging" --resource <databricks-resource-id> --logs '[{"category": "accounts", "enabled": true}, {"category": "Clusters", "enabled": true}, {"category": "Notebooks", "enabled": true}, {"category": "Jobs", "enabled": true}]' --workspace <log-analytics-id>
Implement log retention policies:
az monitor log-analytics workspace update --resource-group <resource-group> --name <log-analytics-name> --retention-time 365
Monitor logs for anomalies:
az monitor activity-log alert create --name "DatabricksAnomalyAlert" --resource-group <resource-group> --scopes <databricks-resource-id> --condition "contains 'UnauthorizedAccess'"
By default, diagnostic logging is not enabled for Azure Databricks workspaces.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 8.2 Collect Audit Logs | x | x | x |
| v7 | 6.2 Activate audit logging | x | x | x |
Level 1 | Automated