Secbert to detect anomalous log entries

Thanks for your detailed e-mail. It helped. Once I ensured the tokenizer configuration was saved natively (not being done in my earlier code) with the exact vocabulary rules and casing preservation parameters matching the training checkpoint, the tokenization alignment was perfectly restored. Now the textual risk assessment scores show up correctly, which were showing up earlier as anomalous for all the log entries. regards, VIjay