Privera Administrative template for Privera by Itha AB: security log and updates. Privera Security log Updates Privera 0.9.0-beta20 or later Privera 0.9.0-beta21 or later Privera 0.9.0-beta22 or later Write the security log to a file Controls whether Privera writes its security log to a file (JSONL with a hash chain). Enabled: the log file is written. Disabled: no log file. The Windows event log is still written unless it is turned off with the policy "Write the security log to the Windows event log". Not Configured: the log file is written (default). Registry value: HKLM\Software\Policies\Privera\SecurityLogEnabled (REG_DWORD, 1 or 0). Read at startup. Folder for the security log file Sets the folder where Privera writes the security log file. Each computer and Windows account gets its own file, so several computers can share one folder. Enter an absolute local path (C:\...) or a UNC path (\\server\share\...), at most 240 characters and without "..". Environment variables such as %PROGRAMDATA% are expanded. If the folder cannot be written to at startup, Privera writes the log in the application data folder and logs the event logg.skrivfel. A path that is not accepted counts as invalid, and the application data folder is used. Not Configured or Disabled: the application data folder, %APPDATA%\privera-desktop\sakerhetslogg. Registry value: HKLM\Software\Policies\Privera\SecurityLogDirectory (REG_EXPAND_SZ; the program also accepts REG_SZ). Read at startup. Write the security log to the Windows event log Controls whether Privera writes its security log entries to the Windows event log (Application, source Privera). Enabled: entries are written to the event log. Disabled: nothing is written to the event log. Not Configured: entries are written (default). Registry value: HKLM\Software\Policies\Privera\EventLogEnabled (REG_DWORD, 1 or 0). Read at startup. Allow export logs to be cleared in the program Controls whether the user may use "Rensa mappen" (Clear folder) under Historik (History) to delete export logs (.audit.json). Enabled: clearing is allowed. Disabled: clearing is refused and the event historik.rensning_nekad is logged. The files can still be deleted in File Explorer if the user has permission to the folder. Not Configured: clearing is allowed (default). If the policies cannot be read at startup, clearing is refused. Registry value: HKLM\Software\Policies\Privera\AllowClearExportLogs (REG_DWORD, 1 or 0). Read at startup. Require the Windows event log for export Controls whether an export is refused when it could not be recorded in the Windows event log (source Privera). Enabled: an export is refused if the event log could not be reached, so that no export happens without a trace. The attempt is recorded in the file log as export.stoppad with reason HANDELSELOGG. Disabled: the export proceeds even if the event log could not be reached (default). Not Configured: same as Disabled. Requires the event log to be on (EventLogEnabled). If it is off, this requirement does not apply. Note: on a computer where the event log does not work, for example when PowerShell is blocked for users, every export is then refused. Each export tries to write to the event log again, and when PowerShell hangs the export waits up to about 10 seconds before it is refused. Test that the event log works on the computers before enabling this policy. Registry value: HKLM\Software\Policies\Privera\RequireEventLogForExport (REG_DWORD, 1 or 0). Read at startup. Allow the debugging port Controls whether the customer edition of Privera may be started with a debugging port (--remote-debugging-port). Normally the program exits immediately when such a flag is present, so that no one can read document text out of the renderer. Enabled: the debugging port is allowed. Used only by the unattended sandbox test, which runs as administrator. An event is logged when the port is allowed through this policy. Disabled: the debugging port is refused and the program exits (default). Not Configured: same as Disabled. Registry value: HKLM\Software\Policies\Privera\AllowDebugPort (REG_DWORD, 1 or 0). Read at startup. Privera updates Controls how Privera updates itself. Off: the program does not check for new versions. The IT department installs new versions itself, for example with Intune or Configuration Manager. Check and notify: the program asks licens.privera.se at startup and shows that a new version is available, but downloads and installs nothing. Automatic: the program downloads a new version in the background and installs it when the user chooses to or at the next normal exit. Not Configured or Disabled: Automatic (default). For an installation for all users under Program Files: choose Off or Check and notify and deploy new versions centrally. An automatic update of such an installation requests administrator rights. A value that cannot be interpreted, or a policy that cannot be read at startup, turns updates off for that session. The user can see under Settings, About Privera (Inställningar, Om Privera) that updates are managed by the organization. The mode is also recorded in the security log start entry (app.start, field uppdateringar). Registry value: HKLM\Software\Policies\Privera\UpdateMode (REG_DWORD: 0 = off, 1 = check and notify, 2 = automatic). Read at startup. Versions older than 0.9.0-beta21 ignore the value. Off (IT installs new versions) Check and notify, do not install Automatic (default) Folder: Mode: