We're sorry, the page you requested cannot be found. Below are some links that may be useful.
++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/README.md b/README.md deleted file mode 100644 index 99113b4..0000000 --- a/README.md +++ /dev/null @@ -1,92 +0,0 @@ -# opencert.website-output - -Opencert website content repo - -## Getting started - -To make it easy for you to get started with GitLab, here's a list of recommended next steps. - -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! - -## Add your files - -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: - -``` -cd existing_repo -git remote add origin https://gitlab.eclipse.org/eclipse/opencert/opencert.website-output.git -git branch -M main -git push -uf origin main -``` - -## Integrate with your tools - -- [ ] [Set up project integrations](https://gitlab.eclipse.org/eclipse/opencert/opencert.website-output/-/settings/integrations) - -## Collaborate with your team - -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) - -## Test and Deploy - -Use the built-in continuous integration in GitLab. - -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) - -*** - -# Editing this README - -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. - -## Suggestions for a good README -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. - -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. diff --git a/about/index.html b/about/index.html new file mode 100644 index 0000000..d56a703 --- /dev/null +++ b/about/index.html @@ -0,0 +1,457 @@ + + + + + + + + + +OpenCert is not a monolithic platform. The OpenCert Tool Platform is composed of various contributions that cover the different features:
+The main contributions come from the AMASS project. The reuse of existing open source projects shows the pragmatism of the approach, and the application of a best practices of software engineering and open source communities: “join and contribute to existing communities” instead of “reinventing the wheel”. As such, the OpenCert open source platform is a good example of the advantages of open source software that can be combined and extended more easily as all APIs and formats are open.
+ + + + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/community/index.html b/community/index.html new file mode 100644 index 0000000..cf6250d --- /dev/null +++ b/community/index.html @@ -0,0 +1,471 @@ + + + + + + + + + +Follow OpenCert and the AMASS Open Platform on:
+ +View more videos on the youtube channel
+Learn about OpenCert, join the community, connect with other CHESS users, get support and service:
+You can use the code from these repositories to experiment, test, build, create patches, issue pull requests, etc. This project is hosted on gitlab.eclipse.org. Please use GitLab issues or OpenCert bugzilla product.
+Project GitLab is hosted here.
+Clone: https://gitlab.eclipse.org/eclipse/opencert/opencert.git
+Browse: https://gitlab.eclipse.org/eclipse/opencert/opencert
+ + + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/downloads/index.html b/downloads/index.html new file mode 100644 index 0000000..483a2be --- /dev/null +++ b/downloads/index.html @@ -0,0 +1,463 @@ + + + + + + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/home/index.html b/home/index.html new file mode 100644 index 0000000..48f776f --- /dev/null +++ b/home/index.html @@ -0,0 +1,472 @@ + + + + + + + + + +The Eclipse OpenCert Tools Platform integrates contributions from different open source projects
+ + + +PolarSys OpenCert is an integrated and holistic solution for assurance and certification management of Cyber-Physical Systems (CPS) spanning the largest safety and security-critical industrial markets, such as aerospace, space, railway, manufacturing, energy and health. The ultimate aim is to lower certification costs in face of rapidly changing product features and market needs.
+ +To deal with the technical CPS complexity and the associated labor-intensive activities for qualifying and certifying these systems, OpenCert uses model-based approaches and incremental techniques. The OpenCert tool platform focuses on architecture-driven assurance, multi-concern assurance (mainly safety and cybersecurity), reuse-oriented assurance (intra and cross-industrial domains) and seamless interoperability between assurance/certification and engineering activities along with third-party activities (external assessments, supplier assurance).
+ ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/images/201806AtifEclipseConFrance.jpg b/images/201806AtifEclipseConFrance.jpg new file mode 100644 index 0000000..d3f3d1f Binary files /dev/null and b/images/201806AtifEclipseConFrance.jpg differ diff --git a/images/ARTA.png b/images/ARTA.png new file mode 100644 index 0000000..5cfa720 Binary files /dev/null and b/images/ARTA.png differ diff --git a/images/OpenCertUsageScenarios.jpg b/images/OpenCertUsageScenarios.jpg new file mode 100755 index 0000000..ff50c04 Binary files /dev/null and b/images/OpenCertUsageScenarios.jpg differ diff --git a/images/bernard-hermant-590572-unsplash_camera.png b/images/bernard-hermant-590572-unsplash_camera.png new file mode 100644 index 0000000..c84c6c6 Binary files /dev/null and b/images/bernard-hermant-590572-unsplash_camera.png differ diff --git a/images/carousel/opencert-slide-01.png b/images/carousel/opencert-slide-01.png new file mode 100644 index 0000000..e6faa7c Binary files /dev/null and b/images/carousel/opencert-slide-01.png differ diff --git a/images/carousel/opencert-slide-03.png b/images/carousel/opencert-slide-03.png new file mode 100644 index 0000000..2fc7ab1 Binary files /dev/null and b/images/carousel/opencert-slide-03.png differ diff --git a/images/carousel/opencert-slide-04.png b/images/carousel/opencert-slide-04.png new file mode 100644 index 0000000..316c660 Binary files /dev/null and b/images/carousel/opencert-slide-04.png differ diff --git a/images/chess-logo.png b/images/chess-logo.png new file mode 100644 index 0000000..d9fb315 Binary files /dev/null and b/images/chess-logo.png differ diff --git a/images/eclipse.jpg b/images/eclipse.jpg new file mode 100644 index 0000000..8967f20 Binary files /dev/null and b/images/eclipse.jpg differ diff --git a/images/epf_logo.jpg b/images/epf_logo.jpg new file mode 100644 index 0000000..c4f1d54 Binary files /dev/null and b/images/epf_logo.jpg differ diff --git a/images/gettingstarted/Fig1.png b/images/gettingstarted/Fig1.png new file mode 100755 index 0000000..1575a1b Binary files /dev/null and b/images/gettingstarted/Fig1.png differ diff --git a/images/gettingstarted/Fig2.png b/images/gettingstarted/Fig2.png new file mode 100755 index 0000000..b893dc8 Binary files /dev/null and b/images/gettingstarted/Fig2.png differ diff --git a/images/gettingstarted/Fig3.png b/images/gettingstarted/Fig3.png new file mode 100644 index 0000000..301d527 Binary files /dev/null and b/images/gettingstarted/Fig3.png differ diff --git a/images/gettingstarted/Fig4.png b/images/gettingstarted/Fig4.png new file mode 100755 index 0000000..82eb3a2 Binary files /dev/null and b/images/gettingstarted/Fig4.png differ diff --git a/images/gettingstarted/Fig5.png b/images/gettingstarted/Fig5.png new file mode 100755 index 0000000..cabfd78 Binary files /dev/null and b/images/gettingstarted/Fig5.png differ diff --git a/images/gettingstarted/Fig6.png b/images/gettingstarted/Fig6.png new file mode 100755 index 0000000..ac6724c Binary files /dev/null and b/images/gettingstarted/Fig6.png differ diff --git a/images/gettingstarted/Fig7.png b/images/gettingstarted/Fig7.png new file mode 100755 index 0000000..9438e30 Binary files /dev/null and b/images/gettingstarted/Fig7.png differ diff --git a/images/gettingstarted/Fig8.png b/images/gettingstarted/Fig8.png new file mode 100755 index 0000000..2772168 Binary files /dev/null and b/images/gettingstarted/Fig8.png differ diff --git a/images/logo.png b/images/logo.png new file mode 100644 index 0000000..fc9dd2f Binary files /dev/null and b/images/logo.png differ diff --git a/images/logo_square.png b/images/logo_square.png new file mode 100644 index 0000000..4475bc9 Binary files /dev/null and b/images/logo_square.png differ diff --git a/images/screenshots/screenshot_00.png b/images/screenshots/screenshot_00.png new file mode 100644 index 0000000..a32da26 Binary files /dev/null and b/images/screenshots/screenshot_00.png differ diff --git a/images/screenshots/screenshot_01.png b/images/screenshots/screenshot_01.png new file mode 100644 index 0000000..90b612d Binary files /dev/null and b/images/screenshots/screenshot_01.png differ diff --git a/images/screenshots/screenshot_02.png b/images/screenshots/screenshot_02.png new file mode 100644 index 0000000..a5cc2fa Binary files /dev/null and b/images/screenshots/screenshot_02.png differ diff --git a/images/screenshots/screenshot_03.png b/images/screenshots/screenshot_03.png new file mode 100644 index 0000000..bb9bb07 Binary files /dev/null and b/images/screenshots/screenshot_03.png differ diff --git a/images/screenshots/screenshot_04.png b/images/screenshots/screenshot_04.png new file mode 100644 index 0000000..b23e30b Binary files /dev/null and b/images/screenshots/screenshot_04.png differ diff --git a/images/youtube.png b/images/youtube.png new file mode 100644 index 0000000..7e596a2 Binary files /dev/null and b/images/youtube.png differ diff --git a/index.html b/index.html new file mode 100644 index 0000000..c244add --- /dev/null +++ b/index.html @@ -0,0 +1,492 @@ + + + + + + + + + +The Eclipse OpenCert Tools Platform integrates contributions from different open source projects
+ + + +PolarSys OpenCert is an integrated and holistic solution for assurance and certification management of Cyber-Physical Systems (CPS) spanning the largest safety and security-critical industrial markets, such as aerospace, space, railway, manufacturing, energy and health. The ultimate aim is to lower certification costs in face of rapidly changing product features and market needs.
+ +To deal with the technical CPS complexity and the associated labor-intensive activities for qualifying and certifying these systems, OpenCert uses model-based approaches and incremental techniques. The OpenCert tool platform focuses on architecture-driven assurance, multi-concern assurance (mainly safety and cybersecurity), reuse-oriented assurance (intra and cross-industrial domains) and seamless interoperability between assurance/certification and engineering activities along with third-party activities (external assessments, supplier assurance).
+ ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/index.xml b/index.xml new file mode 100644 index 0000000..7cba3a4 --- /dev/null +++ b/index.xml @@ -0,0 +1,184 @@ + +In 2017 spring, we are starting to build a website for the Eclipse OpenCERT project.
+You will find all the information about the project, including tutorials and documentation.
+The Eclipse Foundation is provisioning resources like Forum, Wiki, Bugzilla and Mailing-list, so please stay tuned.
+Article by Antoine THOMAS, Eclipse Foundation
+ + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/news/2018-01-15-youtubechannel/index.html b/news/2018-01-15-youtubechannel/index.html new file mode 100644 index 0000000..185a47d --- /dev/null +++ b/news/2018-01-15-youtubechannel/index.html @@ -0,0 +1,454 @@ + + + + + + + + + +Subscribe to the OpenCert Youtube
+ +The AMASS partners regularly publish new content on the OpenCert Youtube channel.
+Subscribe to the channel to get notified of new videos!
+Article by Gaël Blondelle, Eclipse Foundation
+ + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/news/2018-03-09-new-prototype/index.html b/news/2018-03-09-new-prototype/index.html new file mode 100644 index 0000000..b83394b --- /dev/null +++ b/news/2018-03-09-new-prototype/index.html @@ -0,0 +1,452 @@ + + + + + + + + + +The AMASS project partners invested tons of energy to build the new prototype of the AMASS Open Platform.
+Read more information at on the project website
+Article by Gaël Blondelle, Eclipse Foundation
+ + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/news/2018-03-22-new-content/index.html b/news/2018-03-22-new-content/index.html new file mode 100644 index 0000000..48c09d2 --- /dev/null +++ b/news/2018-03-22-new-content/index.html @@ -0,0 +1,452 @@ + + + + + + + + + +To accompany their new prototype, the AMASS partners updated the web site with new content.
+New documentation has been put together in the resources section.
+Article by Gaël Blondelle, Eclipse Foundation
+ + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/news/2018-06-01-meet-amass-ec-france/index.html b/news/2018-06-01-meet-amass-ec-france/index.html new file mode 100644 index 0000000..0cc9ce8 --- /dev/null +++ b/news/2018-06-01-meet-amass-ec-france/index.html @@ -0,0 +1,452 @@ + + + + + + + + + +The AMASS project will participate again to the Open Research lab booth at EclipseCon France 2018 on June 13th-14th.
+Register and meet us at the conference.
+Article by Gaël Blondelle, Eclipse Foundation
+ + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/news/2018-06-25-epf-presentation-at-ec-france/index.html b/news/2018-06-25-epf-presentation-at-ec-france/index.html new file mode 100644 index 0000000..cd33570 --- /dev/null +++ b/news/2018-06-25-epf-presentation-at-ec-france/index.html @@ -0,0 +1,472 @@ + + + + + + + + + +AMASS was present on stage during the plenary session. Atif explains the process to migrate EPF to the latest version of the Eclipse platform.
+
At Eclipse France 2018, Muhammad Atif Javed from MDH, explained the whole attendance +the process of migrating Eclipse Process Framework composer to the latest version of Eclipse.
+During the second half of 2017, Mälardalen University (MDH), with the help of +the Eclipse Foundation, started an important contribution to the Eclipse Process +Framework project and more specifically to EPF Composer. The project was under +maintenance since 2013, with no new official release since then, and still +running on an old version of the Eclipse platform.
+Due to this too old version of the Eclipse platform, it was not possible to +integrate EPF Composer in the AMASS open platform prototype.
+MDH stepped up to fix this, and with the help of the Eclipse Foundation, +the AMASS partners started to collaborate with the IBM team which was +maintaining EPF Composer.
+After initial contacts, MDH developed a patch to port EPF to Eclipse Neon. +This patch was then tested by the EPF development team before integration. +Later, as MDH designated developer, Muhammad Atif Javed, had proved his ability +to contribute to the project, he was elected as a new committer of the EPF +project in conformance with the principles of meritocracy promoted by the +Eclipse Development Process.
+Then, the EPF project team collaborated to create a new release, +which is the one integrated in the AMASS Open Platform.
+Article by Gaël Blondelle, Eclipse Foundation
+ + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/news/2018-12-05-download_p2_preview/index.html b/news/2018-12-05-download_p2_preview/index.html new file mode 100644 index 0000000..bc0194e --- /dev/null +++ b/news/2018-12-05-download_p2_preview/index.html @@ -0,0 +1,452 @@ + + + + + + + + + +AMASS partners just published their latest version of the AMASS open tools platform.
+Go to the download page and give it a try!
+Article by Gaël Blondelle, Eclipse Foundation
+ + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/news/2019-01-24-security_blog/index.html b/news/2019-01-24-security_blog/index.html new file mode 100644 index 0000000..7cedb87 --- /dev/null +++ b/news/2019-01-24-security_blog/index.html @@ -0,0 +1,452 @@ + + + + + + + + + +Security and openness are two orthogonal issues and the AMASS Open Tool Platform is certainly not a liability for the development of CPS
+Read the blog post .
+Blog Post by Maria Teresa Delgado and Gaël Blondelle, Eclipse Foundation
+ + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/news/2021-03-31-opencert_for_privacy_assurance/index.html b/news/2021-03-31-opencert_for_privacy_assurance/index.html new file mode 100644 index 0000000..4685cde --- /dev/null +++ b/news/2021-03-31-opencert_for_privacy_assurance/index.html @@ -0,0 +1,457 @@ + + + + + + + + + +Assurance was one key aspect of the PDP4E project (Privacy and Data Protection for Engineering) H2020 European Project No 787034.
+In this project, it was demonstrated the feasibility to use Eclipse OpenCert also for privacy assurance through the modelling of privacy reference frameworks, mapping models and privacy assurance patterns.
+The public PDP4E knowledge base for privacy assurance is currently at the “release/2.0” branch in the “examples/privacy” folder. This branch also contains the initial contribution for OpenCert 2.0 where several improvements and new functionalities were developed thanks to the PDP4E project and its application in the privacy-related use cases.
+Blog Post by Jabier Martinez Perdiguero, Tecnalia
+ + + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/news/index.html b/news/index.html new file mode 100644 index 0000000..2cfc4fe --- /dev/null +++ b/news/index.html @@ -0,0 +1,532 @@ + + + + + + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/news/index.xml b/news/index.xml new file mode 100644 index 0000000..7ae9827 --- /dev/null +++ b/news/index.xml @@ -0,0 +1,95 @@ + +Access to the documentation of the current OpenCert package produced by the AMASS partners - code name Prototype P2.
++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/resources/gettingstarted/index.html b/resources/gettingstarted/index.html new file mode 100644 index 0000000..ee85423 --- /dev/null +++ b/resources/gettingstarted/index.html @@ -0,0 +1,489 @@ + + + + + + + + + +This section guides the end-user through the its initial use of OpenCert.
+It needs to be upgraded to take into account the new prototype.
+It must be noted that the pre-existing OpenCert tools are designed to follow client-server architecture approach:
+This installation relates to a standalone version of OpenCert, including Papyrus/CHESS, EPF Composer and BVR plugins.
+It is required to have installed (minimum) Java Environment 1.8.
+To install the OpenCert platform client, download it from the Downloads page for Windows 64 bits and uncompress it into your hard disk.
+To use the platform execute the eclipse.exe file and introduce a select a folder that will be used as workspace.
+ +The first step after the installation process is to configure the connection settings with the CDO repository where all the models generated using the platform will be stored. This information must be introduced in the Model Repository Preference page inside the OpenCert category. Go to menu Window → Preferences to open this window.
+ + +The information to introduce is:
+Disable the Repository timeout to avoid the automatic closing of the connection with the server for inactivity using the menu Window → Preference as shown in the image below.
+ +After introducing this data the Opencert Perspective can be used to connect to the server and view the data of the repository configured. To open it, go to menu Window→ Perspective → Open Perspective→ Other.
+ +If the provided connection settings with the repository are incorrect or the server is not running, this view will display the error in the screenshot below instead of the contents of the repository. To solve it, check the server is running (using the page http://opencert.tecnalia.com:8080) and the configuration settings are correct, ensure the communication ports (2036 and 8080) are open, close the Repository Explorer view and open it again (Window→Show View→Other→Opencert→Repository Explorer).
+ +To delete a folder and its contents, right click over it and left click the “Delete” menu.
+ +To delete a model, right click over it and left click the “Delete“menu.
+ + + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/resources/index.html b/resources/index.html new file mode 100644 index 0000000..1936c27 --- /dev/null +++ b/resources/index.html @@ -0,0 +1,496 @@ + + + + + + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/resources/index.xml b/resources/index.xml new file mode 100644 index 0000000..45af34e --- /dev/null +++ b/resources/index.xml @@ -0,0 +1,59 @@ + +This page shows some screenshots that illustrate the AMASS Open Platform in action.
+ + + + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/resources/security/index.html b/resources/security/index.html new file mode 100644 index 0000000..a657539 --- /dev/null +++ b/resources/security/index.html @@ -0,0 +1,471 @@ + + + + + + + + + +By Maria Teresa Delgado and Gaël Blondelle - Eclipse Foundation Europe GmbH
+Security and openness are two orthogonal issues and the AMASS Open Tool Platform is certainly not a liability for the development of CPS
+AMASS (Architecture-driven, Multi-concern and Seamless Assurance and Certification of Cyber-Physical Systems) is an EU-funded project that has created and consolidated a de-facto European Open Tool Platform, ecosystem, and community for assurance and certification of Cyber-Physical Systems (CPS). The tools provided by the AMASS open platform leverage both existing open source components, and new open source components that are published to the community, under an open collaborative model. The resulting open source ecosystem and community are managed as an Eclipse project hosted by the Eclipse Foundation. +As AMASS is addressing a wide universe of application areas (i.e. automotive, railway, aerospace, space, and energy) while implementing an open collaboration model to develop its technology solutions, it is not surprising that the community would express its concern on the platform security aspects and its openness. +But no worries! As you will learn after reading this article, security and openness are two orthogonal issues and the AMASS Open Tool Platform is certainly not a liability for the development of CPS.
+ +Open Source (OS) implies that source code is distributed under a license in which the copyright holder grants the users the power to access, modify and re-distribute the software to anyone and for any purpose. Nowadays, OS components are the core building blocks of application software, providing developers with an ever-growing offer of off-the-shelf possibilities that they can use for assembling their products faster and more efficiently.
+The OSS movement was not designed with security in mind, OSS is all about open collaboration and open innovation. However, the Linus’ law in Open Source states that: “given enough eyeballs, all bugs are shallow.” And the OS community do believe that opening their code up for inspection will increase protection against bugs — and often improve code trust. Nonetheless, OSS community has evolved, and the vast majority of users are now downloading OS resources without actually reviewing the source code itself, meaning that the number of users is far greater than the number of eyeballs. Thus, having the source code available for scrutiny could be either a good or a bad thing, depending on the size of the community and the user perspective.
+Others have studied the correlation between security and open source in a more structured way. Schryen performed a thorough literature review on security aspects in open source vs. closed source software, concluding that the discussion is often biased depending on the preferences of development styles, and the lack of appropriate metrics, a common methodology and hard data. Schryen’s work analyses and compares published vulnerabilities (software bugs that can be used by attackers to gain access to a system or network are commonly referred to as vulnerabilities according to the U.S. MITRE corporation) of a set of open and close source software packages, all of which are widely deployed. His investigation reveals that no significant differences in the severity of vulnerabilities were found between open source and closed source software.
+Security wise, the main concern remains the surface of exposure of software code: all the different points where an unauthorized party could try to inject or extract data. The openness in OSS makes it easier for both the good and the bad guys to find vulnerabilities in the code, since it is available for anyone to review (and to fix!).
+However, closed models implementing a “security through obscurity” approach are not necessarily better. Security is a holistic concept not only depending on the final result, but also linked to the creation and maintenance process, and open source has the potential to be better than closed source software in terms of security vulnerabilities being available for public scrutiny and fixes. But simply being open is not a guarantee of security; over the past years a few examples have made this clear for the OSS community: (a) the Heartbleed bug, which put the spotlight on OpenSSL, the security toolkit used by many of the internet’s largest sites, maintained primarily by two men who have never met in person, (b) the Equifax breach that exposed sensitive data for as many as 143 million U.S. consumers, accomplished by exploiting a web application vulnerability that had been patched more than two months earlier, and (c) the Apache Struts 2 flaw uncovered recently, which promises to be even more critical than the Equifax Bug, a remote code-execution vulnerability in the popular open-source framework for developing web applications in the Java programming language which could lead to full endpoint and network compromise.
+On the other side, if you need to think about security breaches in proprietary solutions or closed source software, just think about the Microsoft security breaches that we were never told about, and you should be good to go, for example: that time when Microsoft responded quietly to a detected secret database hack in 2013. Security in the 21st century has proven to have suffered enough breaches both in the open and closed software worlds.
+AMASS project partners and early adopters agree that security is crucial in all tools, systems and platforms, and of course AMASS results are no exception. However, we have made clear that security and openness are two orthogonal issues and we support the idea that OSS is potentially better -security wise- due to the public availability of source code.
+In the context of the Eclipse ecosystem, some specific efforts are already in place to reinforce the security of the AMASS open platform. Eclipse Development Process (EDP) already covers the traceability of the code published in open source, checked by the Eclipse IP process that tracks the provenance of each contribution as well as the provenance of each dependency recursively. Also, EDP requires that the binaries are signed during the release process.
+Moreover, the AMASS open platform is supposed to be embedded in a larger environment, - either a proprietary product, or a specific deployment by a large organisation- where additional measures can be integrated to ensure the security of the platform.
+AMASS is about tools for assurance and certification processes that can be used in several domains to improve system efficiency, but AMASS is not a CPS core component, and thus the AMASS tool platform by itself is not a liability for the development of CPS. The AMASS open platform is deployed in the context of a global certification and assurance process that should consider the security risks related to the tools in order to effectively mitigate them.
+ + + + + ++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/resources/training/index.html b/resources/training/index.html new file mode 100644 index 0000000..88ca11d --- /dev/null +++ b/resources/training/index.html @@ -0,0 +1,493 @@ + + + + + + + + + +This page references the latest training material available for the OpenCert platform.
++ Back to the top +
+ + + + + + + + + + + + + + + + + + diff --git a/robots.txt b/robots.txt new file mode 100644 index 0000000..4f9540b --- /dev/null +++ b/robots.txt @@ -0,0 +1 @@ +User-agent: * \ No newline at end of file diff --git a/sitemap.xml b/sitemap.xml new file mode 100644 index 0000000..23b4174 --- /dev/null +++ b/sitemap.xml @@ -0,0 +1,68 @@ + +
+