1- I’m not sure I understand your question; this is the root of side-channel leakage, isn’t it? Code execution depends on some secret, and POIs are points in time where power differences stemming from the secret-dependent code execution can be observed. As for predicting POIs – they will occur whenever secret-dependent code is being run. The trick, for an attacker, is in leveraging that for an efficient attack; or for a defender, to reduce the leakage to the point where an efficient attack is no longer possible.
2- In the CW305 ECC demo we use trace averaging to average out the “noise”, essentially. In the case of ECC, we’re looking at a multiplication between two operands, one of which is secret. The power consumption depends on both operands. By averaging many traces with the secret operand constant and the public operand variable, we can average out the public operand’s contribution to the power consumption.
Thanks, you really helped me so much, after these discussions, I gained a more clear view on what I’m doing.
So can we regard the points found in 2 as POIs?