Security domains and project phases

When assigning values to safeguards and controls, if a cell in the table is left empty, PILAR tries to use the value from another cell.

security domains & project phases / phases first

when a safeguard is not evaluated in phase in a domain, PILAR tries to use the value from the previous phase; if none, it tries to use the value from the next security domain

security domains & project phases / domains first

when a safeguard is not evaluated in phase in a domain, PILAR tries to use the value from the next security domain; if none, it tries to use the value from the previous phase
(this is the default behaviour before version 4.4)

	domains first			phases first
	phase 0	phase 1	phase 2	phase 0	phase 1	phase 2
domain 2	7^th	4^th	1^st	3^rd	2^nd	1^st
domain 1	8^th	5^th	2^nd	6^th	5^th	4^th
base	9th	6^th	3^rd	9^th	8^th	7^th

When an asset is subject to individual evaluation, it behaves as if in its own (unnamed) security domain. That is:

	domains first			phases first
	phase 0	phase 1	phase 2	phase 0	phase 1	phase 2
ASSET	7^th	4^th	1^st	3^rd	2^nd	1^st
domain 1	8^th	5^th	2^nd	6^th	5^th	4^th
base	9th	6^th	3^rd	9^th	8^th	7^th

Top