/opt/philter/profiles. You can edit the filter profiles directly there using a text editor or you can use Philter's API to upload a filter profile. In this case we recommend just using a text editor on the Philter instance to create a filter profile.
cp /opt/philter/profiles/default.json /opt/philter/profiles/evaluation.json
/opt/philter/profiles/evaluation.jsonin a text editor. (The content of
evaluation.jsonwill be similar to what's shown below but may have minor differences between different versions of Philter.)
evaluationand save the file.
enabledproperty to false. Using the
enabledproperty allows you to keep the filter configuration in the filter profile in case it is needed later but both options have the same effect.
redactionFormatvalues for each filter should be fine for evaluation.
file.txtto Philter. The
?p=evaluationtells Philter to apply the
evaluationfilter profile that we have been editing. Philter's response to this command will be the redacted contents of
file.txtas defined in the filter profile.
file.txtand the redacted contents returned by Philter, we can now compare those files to begin evaluating Philter's performance. You can
diffthe text to find the redacted information or use some other method.
explainAPI endpoint produces a detailed description of the redaction. The response will include a list of spans that contain the start and stop positions of redacted text and the type of sensitive information that was redacted. Using this information we can compare the redacted information to our annotated file to calculate precision and recall metrics.