Skip to content

Commit 6f5c26c

Browse files
feature/qualys-was-13569 Review driven README changes and one change in CEL script
1 parent eb233fc commit 6f5c26c

File tree

3 files changed

+5
-17
lines changed

3 files changed

+5
-17
lines changed

packages/qualys_was/_dev/build/docs/README.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -87,8 +87,8 @@ Should the agent run into memory issues, one or more of the following should sol
8787
5. If your system is using the 3.20 API or before, purge scan history. Scan history is the list of all scans have been
8888
run for each vulnerability finding. This list is returned in 3.20 and earlier APIs. This list can be quite large if
8989
it is not purged by the customer. Due to its size, this list can effect the amount of memory required to process the
90-
qualys API results. The cel script that queries the qualys APIs removes history results before sending the data to
91-
elasticsearch.
90+
Qualys API results. The CEL script that queries the Qualys APIs removes history results before sending the data to
91+
Elasticsearch.
9292

9393
The additional data available with verbose mode are:
9494
- Web application tags
@@ -111,10 +111,6 @@ by the qualys_was.vulnerability.id, a unique id for the finding. Knowledge base
111111
the volume of data transported during a single run of the cel script. The cel script removes history data that is
112112
included in verbose mode.
113113

114-
115-
116-
117-
118114
## Data reference
119115

120116
### Web Application Vulnerability Dataset
@@ -269,7 +265,6 @@ An example response from the Qualys WAS API
269265
}
270266
}
271267

272-
273268
```
274269
An example of a Knowledge Base object after decoding from XML to JSON
275270
```json
@@ -378,7 +373,6 @@ An example of a Knowledge Base object after decoding from XML to JSON
378373

379374
{{event "vulnerability"}}
380375

381-
382376
**ECS fields**
383377

384378
| Field | Description | Type |

packages/qualys_was/data_stream/vulnerability/agent/stream/cel.yml.hbs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,7 +175,7 @@ program: |
175175
(size(resp.Body) != 0) ?
176176
string(resp.Body)
177177
:
178-
" no body "
178+
"no body"
179179
),
180180
},
181181
},

packages/qualys_was/docs/README.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -87,8 +87,8 @@ Should the agent run into memory issues, one or more of the following should sol
8787
5. If your system is using the 3.20 API or before, purge scan history. Scan history is the list of all scans have been
8888
run for each vulnerability finding. This list is returned in 3.20 and earlier APIs. This list can be quite large if
8989
it is not purged by the customer. Due to its size, this list can effect the amount of memory required to process the
90-
qualys API results. The cel script that queries the qualys APIs removes history results before sending the data to
91-
elasticsearch.
90+
Qualys API results. The CEL script that queries the Qualys APIs removes history results before sending the data to
91+
Elasticsearch.
9292

9393
The additional data available with verbose mode are:
9494
- Web application tags
@@ -111,10 +111,6 @@ by the qualys_was.vulnerability.id, a unique id for the finding. Knowledge base
111111
the volume of data transported during a single run of the cel script. The cel script removes history data that is
112112
included in verbose mode.
113113

114-
115-
116-
117-
118114
## Data reference
119115

120116
### Web Application Vulnerability Dataset
@@ -269,7 +265,6 @@ An example response from the Qualys WAS API
269265
}
270266
}
271267

272-
273268
```
274269
An example of a Knowledge Base object after decoding from XML to JSON
275270
```json
@@ -524,7 +519,6 @@ An example event for `vulnerability` looks as following:
524519
}
525520
```
526521

527-
528522
**ECS fields**
529523

530524
| Field | Description | Type |

0 commit comments

Comments
 (0)