From: Sai.Sathujoda@toshiba-tsip.com
To: cip-dev@lists.cip-project.org, jan.kiszka@siemens.com
Cc: Sai <Sai.Sathujoda@toshiba-tsip.com>,
dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp
Subject: [isar-cip-core 3/3] security.yml: Add additional features to security image
Date: Wed, 30 Aug 2023 10:11:15 +0530 [thread overview]
Message-ID: <20230830044115.1112349-4-Sai.Sathujoda@toshiba-tsip.com> (raw)
In-Reply-To: <20230830044115.1112349-1-Sai.Sathujoda@toshiba-tsip.com>
From: Sai <Sai.Sathujoda@toshiba-tsip.com>
From IEC certification perspective, a security image is needed which has the below features along with security customizations.
1. Data encryption (CR4.1)
2. Secure boot (EDR 3.14)
3. SWupdate (NDR 3.10)
Signed-off-by: Sai <Sai.Sathujoda@toshiba-tsip.com>
---
kas/opt/security.yml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kas/opt/security.yml b/kas/opt/security.yml
index 1f3745b..67bf4ff 100644
--- a/kas/opt/security.yml
+++ b/kas/opt/security.yml
@@ -10,6 +10,9 @@
#
header:
version: 12
+ includes:
+ - kas/opt/encrypt-partitions.yml
+ - kas/opt/ebg-secure-boot-snakeoil.yml
target: cip-core-image-security
--
2.30.2
next prev parent reply other threads:[~2023-08-30 4:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 4:41 [isar-cip-core 0/3] Enabling additional features in security image Sai.Sathujoda
2023-08-30 4:41 ` [isar-cip-core 1/3] Kconfig: Opt additional IEC 62443-4-2 features when security option is selected Sai.Sathujoda
2023-08-30 4:41 ` [isar-cip-core 2/3] deploy-cip-core.sh: Workaround to search for swupdate initrd image name Sai.Sathujoda
2023-08-30 6:39 ` Jan Kiszka
2023-08-30 4:41 ` Sai.Sathujoda [this message]
2023-09-06 4:56 [isar-cip-core 0/3] Enabling additional features in security image Sai.Sathujoda
2023-09-06 4:56 ` [isar-cip-core 3/3] security.yml: Add additional features to " Sai.Sathujoda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230830044115.1112349-4-Sai.Sathujoda@toshiba-tsip.com \
--to=sai.sathujoda@toshiba-tsip.com \
--cc=cip-dev@lists.cip-project.org \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.