Table 9. Loss scenarios of IFBs.

Identified loss scenarios of the listed IFBs in Table 8.

IFBs	GW: function itself	GW: environment
Phone_Func1_IFB1	/	Phone_Func1_IFB1_LS1
Phone_Func1_IFB2	/	Phone_Func1_IFB2_LS1
Phone_Func1_IFB3	Phone_Func1_IFB3_LS1	/
Phone_Func1_IFB4	Phone_Func1_IFB4_LS1	Phone_Func1_IFB4_LS2, Phone_Func1_IFB4_LS3
LS Description:
Phone_Func1_IFB1_LS1: Function is bypassed but returns a fake OK result
Phone_Func1_IFB2_LS1: Valid key is replaced by a forged one
Phone_Func1_IFB3_LS1: Algorithm is maliciously modified by the attacker
Phone_Func1_IFB4_LS1: Algorithm is maliciously modified by the attacker, which requires more computing resource
Phone_Func1_IFB4_LS2: Input length exceeds the limitation but is not detected
Phone_Func1_IFB4_LS3: Computing resource is occupied by others maliciously