Incorporate Observability for Attacker

[sandorstormen]

When calling node_is_observable() for the attacker, we should be able to set, for example, all defense steps to non-observable.

[mrkickling]

I believe what you might want is that node_is_observable is agent based? So is_observable(agent, node). And if agent is an attacker, it will not observe defenses?

[sandorstormen]

I believe what you might want is that node_is_observable is agent based? So is_observable(agent, node). And if agent is an attacker, it will not observe defenses?

That sounds about right. Attacker agents might/ might not observe the defense steps. So observability is a relevant concept for the attacker as well.

[mrkickling]

Yes. I think we might want to update the scenario format to allow observability rules or agents as well, and perhaps also observability rule based on attack step type (defende/or/and/exist/notExist).

[mrkickling]

I will add this to the new scenario design