Skip to content

Commit c1e1661

Browse files
committed
Adjust Notus documentation
1 parent a3e1759 commit c1e1661

File tree

1 file changed

+13
-6
lines changed
  • doc/manual/nasl/built-in-functions/glue-functions

1 file changed

+13
-6
lines changed

doc/manual/nasl/built-in-functions/glue-functions/notus.md

Lines changed: 13 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ product: identifier for the notus scanner to get list of vulnerable packages
1919
In contrast to **[update_table_driven_lsc_data(3)](update_table_driven_lsc_data.md)**
2020
this function does not publish results by itself, but returns a json like structure,
2121
so information can be adjusted and must be published using
22-
**[security_lsc(3)](../report-functions/security_lsc.md)**. The json like format depends
22+
**[security_notus(3)](../report-functions/security_notus.md)**. The json like format depends
2323
one the scanner that is used. There are currently 2 scanner types available: Notus and
2424
Skiron. Their response have different formats and also will be parsed differently. The
2525
format for Notus has the following structure:
@@ -54,11 +54,18 @@ The elements can be accessed by using the normal NASL array handling. For more i
5454

5555
The format for Skiron has the following structure:
5656
```json
57-
{
58-
"[oid1]": "some message",
59-
"[oid2]": "some message"
60-
}
61-
It is just a dictionary with the OID of the result as key and the result message as value.
57+
[
58+
{
59+
"oid": "[oid1]",
60+
"message": "[message1]"
61+
},
62+
{
63+
"oid": "[oid2]",
64+
"message": "[message2]"
65+
}
66+
]
67+
```
68+
It is a list of dictionaries. Each dictionary has the key `oid` and `message`.
6269

6370
To determine which format is used, the builtin function **[notus_type(3)](notus_type.md)** can be used.
6471

0 commit comments

Comments
 (0)