>>Responses imported from previous forum
Reply From User: adamwoodland, posted: 2019-02-17 23:21:44
Note that https://www.schneider-electric.com/en/work/support/cybersecurity/overview.jsp is the public Schneider portal for cyber security. I am not part of the product/development team so my following comments should take that into consideration...
Do you mean standards for the product, for a system or for hardening of the environment?
For the product I believe all Schneider development teams follow the SDL. I haven't specifically looked recently but I don't believe any software has Achilles or ISASecure certification. Some Schneider development teams are certified by ISASecure but last I checked none of the Telemetry teams all.
For the system, ClearSCADA can be part of a system that is implemented for standards such as ISA62443 but these standards are much more than just ClearSCADA. Schneider Electric have some white papers on how various components available can fit together to meet relevant security levels and the extra components required (NIDS, NIPS, AD, etc).
For the hardening we in delivery have implemented some systems using CIS-CAT requirements, but with a couple of exceptions to ensure availability is the focus rather than confidentiality.
Reply From User: brcgomezle, posted: 2019-02-18 12:48:34
Hi Adam,
Thanks for your reply.
I was looking for standards for the product.
Those white papers that you mention are available?
Thank you.
Reply From User: adamwoodland, posted: 2019-02-19 00:13:27
https://www.schneider-electric.com/en/download/document/998-20186845/ was the one I was thinking about. Just mentally replace the word Citect with ClearSCADA in that document 🙂
As a technical person I'm not a massive fan of white papers, I generally find them vague, unhelpful and only a glorified sales document for a specific product. This one is much better (although a disclaimer: I did provide some input to Dan prior to release so opinion may be biased) but it still is general in its advice and indicative of what is needed.
The whole point of 62443 is doing a risk assessment and implementing what is relevant to your system.
It may be worth you getting a hold of the official 62443 standard if you're keen for more information, although each section costs some money. For an overview check out 62443-1-1, for actual technical implementation check out 62443-3-2 and -3-3, and if you know ISO27001 then 62443-2-1 will be interesting. They used to have the working drafts on the ISA website but it looks like they took those down, else you could have just read those for free.
Reply From User: sbeadle, posted: 2019-02-19 14:39:02
Thanks Adam. That white paper refers to SCADA generally, and 'Citect' only appears in tiny writing on the diagrams. It all applies, and is a good document.
Standards for software products are not worth the paper or memory they are written in/on unless the system is secured in a holistic way.
There are 3 key pointers here:
1) ClearSCADA, like the other software applications created by SE, is developed using the Secure Development Life Cycle, which is considered best practice. This standard governs how software is designed, created, tested and managed. While not available externally, it is a confluence of global norms which is kept up to date through training, procedures etc.
2) ClearSCADA has features which enable integrators and users to create a secured system, and the system must include operating system, networking, procedures for security etc. Consult the documentation and Resoirce Center for more details.
3) We know that customers have implemented ClearSCADA within their environments and met the needs of their security auditors and testers.
Reply From User: adamwoodland, posted: 2019-02-19 22:07:18
Steve, I thought Microsoft developed SDL, at least in concept? If so https://www.microsoft.com/en-us/securityengineering/sdl/ could be a good general reference?
