else statements/ complex if

[Dionka]

Please fill out the Bug Form or Feature Request Below

Feature Request

Describe the feature and give an example use case

How do i create complex if like below:
† cvss_exploitability > 3 AND cvss_exploitability <6 †
do something
¥

or

† cvss_exploitability > 3 AND cvss_impact <6 †
do something
ELSE
do something else
¥

Additionally how I write IF in a row?
this doesn't seems to work in a row...

For every finding in a table I want to print the cvss impact and exploitation but not the values. The description.
For example if the cvss impact is >0 and <4 --> low e.t.c This is filled in a row.

Thank you very much!

[Petessss]

Did you look at the findings section of the default template? (Page5) It shows how to create a table based on conditional statements. Just swap out the DREAD Score and Remediation effort with cvss impact and exploitation.

Also take a look at the Meta Language wiki: https://github.com/SerpicoProject/Serpico/wiki/Serpico-Meta-Language-In-Depth

[Dionka]

@hi,

Thank you very much for the answer but this is not what I meant.

I have a loop like this:
"For every finding create a table with the details for this finding"

¬report/findings_list/findings:::CVSS_TOTAL>-1¬

IMPACT:

IF cvss_impact is >0 and <4 then write Low else if cvvss_impact is >4 and <7 then write medium else write high enf_if

∆

Additionally, regarding the counting, I can't find any part in default reports template, that actually counts and displays the number of findings.

Thank you very much again for your response.

[Petessss]

@Dionka,
Thank you for the additional detail. Ya, the current markup language does not support control structures like your describing.

[Dionka]

I was able to do the following work around:

† cvss_impact > -1 †
† cvss_impact < 4 †
† cvss_exploitability > -1 †
† cvss_exploitability < 4 †

Technical Impact

Exploitability

Low

Low

¥ ¥ ¥ ¥

For all nine possible combinations (Low-Low, Low-Medium, Low-High, etc...)

The table created is split, and at the end several empty lines created must be deleted in order to merge the table.
But that's for sure acceptable!
Thank you very much for your time and support on this one. Great work!