The objective of this tool is to analyze the traces captured from a given scope.
Main features:
* CPA and Profiling types of attack;
* Built-in preprocessing modules (decimation, resync, digital filter, normalize and noise);
* Record preprocessed traces output;
* Execute custom analysis scripts;
* AES Key schedule calculator;
* Set of result widgets: Correlation vs Traces plot; Output vs Point plot; PGE vs Trace plot; PGE Table; Waveform Viewer.
[[File:Screen Shot 2016-07-12 at 4.02.17 PM.png|1100px]]
== Using the Analyzer ==
After loading the project, you will need to setup the analysis environment first.
In the analyzer, the settings tabs are used to automatically generate the analysis script (shown in the "Analysis Script" dock). This code can be edited by the user for a more "advanced" usage. It can also be saved and loaded through:
* the console ($python script.py);
* using the "Attack Script Generator" tab;
* copying it to the scripts folder (chipwhisperer/software/chipwhisperer/analyzer/scripts or ˜/chipwhisperer_projects/chipwhisperer/analyzer/scripts) so that it will appear in the Project->"Example Scripts" menu the next time you execute the tool.
In the "Analysis Script" dock, the constructor of the script object is called automatically every time that a new script is generated. It is done because widgets like the waveform viewer should update the trace output of the preprocessing modules when the user modify its settings. The run() method is executed only when the "Start Analysis" button in the toolbar is pressed. Custom methods can be executed by selecting it in the code and right clicking: a "Run Function" option will show up.
The "Attack Script Generator" is the main settings tab. It allows the user to set the Preprocessing modules that should be applied over the original traces and the Attack module. The Preprocessing and the Attack tabs will update accordingly.
The "Trace Explorer" tab enables a set of helper scripts needed by some of the analysis algorithms (like the POI detection in the Template attack).
== Preprocessing Modules ==
They are Are filters that modify the previous traces from a given trace source (that can be another Preprocessing Module or the Trace Manager ) and works as a new trace source to the next module in the chain (Channel is supported aswell but only through scriptingcalled trace observer). It means that multiple modules can be used one after === Add Noise: Amplitude ===Add random noise to the othertraces. You may want Used for testing, has no use in actual analysis. === Add Noise: Time Jitter ===Add random jitter. Used for testing, has no use in actual analysis. === Decimation: Clock Recovery ===Attempts to observe 'recover' the changes in autoclock by band-generated script code in pass filtering, and then uses that to decimate to only points of interest. ****CURRENTLY NOT SUPPORTED**** === Decimation: Fixed ===Decimate (reduce the "Analysis script" editor widgetsample rate) by a fixed factor.
=== Sum of Difference Digital Filter ===Frequency specific filter.
This module, also known as Sum o Absolute Difference (SAD), is used to re-synchronize traces as in the case of signals with time jitter=== Normalize ===Normalize by standard deviation. Zooming in the waveform plot, you can detect the presence of jitter when the traces are not aligned (you may need to select about 8 or more traces to be ploted simulteneously in the "Trace Output Plot" settings in order to visualize it):
[[File=== Resync:Screen Shot 2016Cross Correlation ===Use cross-07-13 at 1.31correlation to detect shift between a 'reference trace' and every input trace.23 PMIn practice the other resync methods seem to work better.png|1100px]]
If it is the case, go to the "Attack Script Generator" tab and select "=== Resync: Sum-of-Difference" as the Module #0. Peak Detect ===Switch to the "Preprocessing" tab and Select a point range in the plot as "Reference Points". It can be performed by manually inserting the values (usually around a Line up traces so peak) in the corresponding field (either max positive or by clicking in the adjacent button and select the area direcly in the plot by draggin the vertical linesmax negative) within some given range of points all aligns.
[[FileFor each trace the following must hold or the trace is rejected:Screen Shot 2016-07* (1-13 at valid limit) < (peak value from candidate trace) / (peak value from reference) < (1.54.09 PM.png|1100px]]+valid limit)
Next, you will need to select the "Input Windows" which * If 'valid limit' is the interval in the other traces that the tool will try to match with the reference by shifting it until the SAD 0 then this is reduced. The best value for this field can be determined by adding more traces to the plot ignored, and checking if all of then would fit in the "Reference Points after shifting:traces are kept.
[[File=== Resync:Screen Shot 2016Resample based on Zero-07Crossing ===Deal with resampling 'bins' based on zero-13 at 1crossing detection.55.57 PM.png|1100px]]
Click "Enable" and === Resync: Sum-of-Difference ===Minimize the 'Sum of Absolute Difference' (with some luckSAD) all , also known as 'Sum of Absolute Error'. Uses a portion of one of the traces will align magicallyas the 'reference'. This reference is then slid over the 'input window' for each trace, and the amount of shift resulting in the minimum SAD criteria is selected as the shift amount for that trace.
See [[File:Screen Shot 2016Sum of Absolute Difference (SAD) Pre-07-13 at 1.56.20 PM.png|1100pxProcessing]]for more information.
