Security by Default

WinCC OA comes with its built-in expert knowledge and Secure by Default configuration. This is a development principle ensuring that security measures are enabled right from the installation. This episode will provide guidance on working with this ready-to-use security template.

Video Information

Length
2:07
Language
English

Transcript

Hello, here is your host Mounir again and I welcome you to our Security video series. In this video we will explore the Security by Default settings in WinCC OA. Right, let’s get into it.

To configure a system securely you need to get an overview of all the configuration options and switches. As a non-expert, this would take a lot of work and time. But luckily, this expert knowledge is already built-into WinCC OA because we deliver many features in a Secure by Default configuration.

Security by Default is a development principle ensuring that security measures are enabled by default. This means that a feature is configured securely - directly after the installation, and you just need to refine the configuration according to your requirements. You can compare this with a Firewall that blocks all ports after the installation, and you just need to open the required ones.

With our already built-in Security by Default settings, you get the following benefits:

  • Firstly, Security by Default serves as a good starting point to build a secure foundation for all the following security configurations.
  • Secondly, the vulnerability exposure is reduced, so it is not very likely that a system will get attacked right after the installation.
  • As a third point, the ‘Security by Default feature in WinCC OA provides a ready-to-use security template for your project. This makes it easier for you to refine the settings and make changes as needed, enhancing the security of your project.

Don’t worry, how this works is explained in detail in our WinCC OA Security Guideline.

To sum up, you should understand that Security by Default reduces the security threat impact directly right after the installation of WinCC OA. But when deploying your WinCC OA project into productive environments, think about the concept of defaults. Take our default certificates, for example. They’re great to get you started, but they’re not meant for use in productive environments.

Thank you for listening and remember to follow us on LinkedIn and YouTube and watch our next episode.