Hi @cdm-anv
No that's not supported right now.
The goal was to have the lurker run with as little rights as required so that it works with almost all rules/policies.
The securityContext set on the lurker should be enough to have it run in the strict pod security standard.

The automountServiceToken token is explicitly set to true as the lurker needs that token to talk to the kubernetes api to find out weather the scanner pod is finished.

Can you go into more details what your requirements reguarding security content are that the lurker doesn't meet yet?
Would be interessting to see if there is something we could set in addition to the current settings.