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] security.yml: Add additional features to security image
Date: Wed, 12 Jul 2023 17:01:53 +0530 [thread overview]
Message-ID: <20230712113153.1194397-1-Sai.Sathujoda@toshiba-tsip.com> (raw)
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)
The config.yaml will not have the extra enabled features as true. Hence they
should be passed in the image run command.
Signed-off-by: Sai <Sai.Sathujoda@toshiba-tsip.com>
---
doc/README.security-testing.md | 2 +-
kas/opt/security.yml | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/doc/README.security-testing.md b/doc/README.security-testing.md
index c9540be..97000da 100644
--- a/doc/README.security-testing.md
+++ b/doc/README.security-testing.md
@@ -33,7 +33,7 @@ Save & Build
```
# Boot the Linux image
```
-host$ ./start-qemu.sh x86
+host$ SECURE_BOOT="true" TPM2_ENCRYPTION="true" ./start-qemu.sh x86
```
# Copy security tests in to the Linux image
diff --git a/kas/opt/security.yml b/kas/opt/security.yml
index 1f3745b..b21f330 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 reply other threads:[~2023-07-12 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 11:31 Sai.Sathujoda [this message]
2023-07-13 17:32 ` [isar-cip-core] security.yml: Add additional features to security image Jan Kiszka
2023-07-14 6:10 ` Jan Kiszka
2023-07-17 7:37 ` Sai.Sathujoda
2023-07-17 7:52 ` Jan Kiszka
2023-08-03 4:19 ` Sai.Sathujoda
2023-08-10 10:31 ` Jan Kiszka
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=20230712113153.1194397-1-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.