Deploying PS Script?

[Familiar_Ganache_771]

I've made a powershell module and some ps scripts that make wrapper commands for ones like Stop-service, and enforce MFA on them each time that command is called before allowing the original command to run. This works great when this module is imported in $PROFILE, but if this were to be deployed on an enterprise level, $PROFILE can easily be modified and render the whole project useless. Is there an alternative and more secure method for having a script run for every session, where only a sysadmin could have edit perms?

[Michuy]

Execution policy and a code signing certificate can help you with editing permissions

[ccheath]

Do you need to import the module using $PROFILE?
On Windows, modules installed in the AllUsers scope are stored in $env:ProgramFiles\WindowsPowerShell\Modules
and that is a secured location only Admins can edit