You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- DO NOT modify the "owner" and "repo" parameters - they must be exactly as shown
184
182
- Use only '${{ env.PULL_REQUEST_NUMBER }}' as PR number. DO NOT PARSE from anywhere.
185
183
- DO NOT try to access environment variables through shell commands
@@ -360,3 +358,5 @@ jobs:
360
358
## Final Instructions
361
359
362
360
Remember, you are running in a virtual machine and no one reviewing your output. Your review must be posted to GitHub using the MCP tools to create a pending review, add comments to the pending review, and submit the pending review.
361
+
362
+
gcp_token_format: '${{ secrets.GITHUB_TOKEN || github.token }}'# Migrated from env var
Search for raw logs in Chronicle using the query language:
221
+
222
+
```bash
223
+
secops search raw-logs \
224
+
--query 'raw = \"authentication\"' \
225
+
--snapshot-query 'user != ""' \
226
+
--time-window 24 \
227
+
--case-sensitive \
228
+
--log-types "OKTA,AZURE_AD" \
229
+
--max-aggregations-per-field 100 \
230
+
--page-size 25
231
+
```
232
+
215
233
### Get Statistics
216
234
217
235
Run statistical analyses on your data:
@@ -654,8 +672,18 @@ secops parser run \
654
672
secops parser run \
655
673
--log-type OKTA \
656
674
--logs-file "./test.log"
675
+
676
+
# Run parser with statedump for debugging (outputs readable parser state)
677
+
secops parser run \
678
+
--log-type WINEVTLOG \
679
+
--parser-code-file "./parser.conf" \
680
+
--logs-file "./logs.txt" \
681
+
--statedump-allowed \
682
+
--parse-statedump
657
683
```
658
684
685
+
The `--statedump-allowed` flag enables statedump output in the parser results, which shows the internal state of the parser during execution. The `--parse-statedump` flag converts the statedump string into a structured JSON format.
Chronicle also provides comprehensive case management capabilities for tracking and managing security investigations. The CLI supports listing, retrieving, updating, and performing bulk operations on cases.
>**Note**: The case management uses a batch API that can retrieve multiple cases in a single request. You can provide up to 1000 case IDs separated by commas.
1104
+
>**Note**: You can provide up to 1000 case IDs separated by commas.
1105
+
1106
+
#### List cases
1107
+
1108
+
```bash
1109
+
# List all cases with default pagination
1110
+
secops case list --page-size 50
1111
+
1112
+
# List with filtering
1113
+
secops case list --page-size 100 --filter 'status = "OPENED"' --order-by "createTime desc"
1114
+
1115
+
# Get cases as a flat list instead of paginated dict
1116
+
secops case list --page-size 50 --as-list
1117
+
```
1118
+
1119
+
#### Get case details
1120
+
1121
+
```bash
1122
+
# Get a specific case by ID
1123
+
secops case get --id "12345"
1124
+
1125
+
# Get case with expanded fields
1126
+
secops case get --id "12345" --expand "tags,products"
1127
+
1128
+
# Legacy: Get multiple cases by IDs (batch API)
1129
+
secops case --ids "case-123,case-456"
1130
+
```
1131
+
1132
+
>**Note**: The legacy batch API can retrieve up to 1000 case IDs in a single request.
1133
+
1134
+
#### Update a case
1135
+
1136
+
```bash
1137
+
# Update case priority
1138
+
secops case update --id "12345" --data '{"priority": "PRIORITY_HIGH"}' --update-mask "priority"
0 commit comments