Security practices

So that you can work with SuCri not only efficiently but also securely, some basic security measures should be observed. These concern both the handling of licenses and the protection of your project data.

License and access management

  • Use licenses only when authorized: Use exclusively valid company licenses.
  • Control license transfer: Release licenses after finishing your work with the Push command so that no unnecessary seats are blocked.
  • Check expiry dates: Keep your licenses up to date in order to avoid work interruptions during critical project phases.

File security

  • Control content and project paths: Make sure that content is not stored uncontrolled on unsecured network drives. Local copies on secured company drives are preferable.
  • Regular backups: Back up projects and content directories daily to company-owned servers or dedicated backup systems.

Working environment

  • Restrict write permissions: Changes to content or system folders should only be made with administrator rights.
  • Use the patcher (Module 3) with care: Only perform updates if you have local administration rights.
  • Protect templates: Company-wide ortho templates and BOM templates should be stored write-protected to prevent accidental changes.

Handling support and logs

  • Treat logs confidentially: Log files (command SuCriShowLog) can contain technical details of your system environment. Forward these exclusively to authorized support channels.
  • Make support requests specifically: Use the function SuCriSendSupportRequest for official support reports to ensure a controlled transfer of relevant project data.

Important notes

  • Regularly check the access rights to your central project directories.
  • Make sure that all employees are informed about the internal company guidelines for data backup.