Firefly Open Source Community

   Login   |   Register   |
New_Topic
Print Previous Topic Next Topic

CKSݩ`ͥȡCKST֪RӖ

67

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
67

CKSݩ`ͥȡCKST֪RӖ

Posted at 1/28/2026 06:03:43      View95 | Replies1        Print      Only Author   [Copy Link] 1#
P.S.TopexamGoogle DriveǹФƤoϤ2026 Linux Foundation CKSףhttps://drive.google.com/open?id=1ALVpTTQ49ixvzHV8GjrjbEoiDHT4Peb7
TopexamϳϵNʆ}ⰲȫʛQgֶΤФ줤`ӥ֤äƤޤҡLinux FoundationCKS}ȥ`֤यˡJޤLinux FoundationCKS}ͨ^ʤߤʤΤǴ˚ݤˤʤޤƷ|Linux FoundationCKS}ϤʤѸ٤ԇY˺ϸ񤵤ޤLinux FoundationCKSYJȡäΤϤΤ褦ʺgʤȤǤ
Linux Foundation CKS (Certified Kubernetes Security Specialist) ExamϡKubernetes饹`Υƥ_뤿֪RȥƥȤJԇYǤKubernetesϡƥʥץꥱ`չ_ȹΤΥǥեȥ`ɤȤʤäƤꡢΤᡢKubernetes饹`Υƥ_ϡFITե饹ȥ饯`ˤҪʂȤʤäƤޤCKSJԇYϡaߤKubernetes饹`Υƥ_˰餦ƥꥹ򄿹Ĥ˹뤿˱Ҫʥ֤äƤ뤳Ȥ^ޤ
CKSJϘIǷdz˸ߤu졢ҪʼgIMJƤޤCKSJȡä뤳ȤˤꡢKubernetesƥΥޥ`ȡMळȤˌƤ뤳ȤʾηҰΌT֪R뤳ȤǤޤJϤޤ٤˳LKubernetesƥҰǤΥץեåʥ¤˙Cȥꥢåפ_ȤǤޤ
^CKSݩ`ͥ & ϸ񥹥`CKST֪RӖ | һCKS౾㏊ϡCKSԇY󥸥ѧĩ`Ȥʹä뷽ǡaߤȤΤʤfĿָơ󤭤ʼеĤMi줲ޤ CKSԇY܊ꠤˤयˡμӤ뤳Ȥǡ˽ϹHЈǥȥåץ饹Υȥ`˥YϥץХ`ˤʤޤ ˡ˽ϳˡ໥_k桹ԭtؤѧ^̤DZҪʤȤϤĤǤCKSg̲Ĥ`DŽĤ֧ԮṩǤŤƤޤ
Linux Foundation Certified Kubernetes Security Specialist (CKS) J CKS ԇY} (Q35-Q40):| # 35
You are tasked with securing the container image supply chain for your organization_ You are using a container registry that supports signing and verification of container images. You need to create a policy that ensures only signed images from a specific trusted source are deployed to your Kubernetes cluster.

h
Solution (Step by Step) :
1. Configure the Container Registry:
- Enable Image Signing: Enable image signing functionality in your container registry (e.g., Docker Hub, Google Container Registry, etc.).
- Create a Signing Key: Generate a signing key and store it securely. This key will be used to sign images from the trusted source.
2 Create a Kubernetes Admission Controller:
- Use an Admission Controller like "Container Image Signature Validation Admission Webhook" to enforce image signature verification during deployment. This Admission Controller ensures that only signed images are allowed to be deployed to your cluster.
3. Configure the Admission Controller:
- Create a Service Account: Create a Service Account with the necessary permissions to access your container registry and verify image signatures.
- Create a Deployment for the Admission Controller: Deploy the Admission Controller with a pod using the Service Account created earlier.
- Configure the Admission Controller: Configure the Admission Controller to use your signing key to verify signatures.
4. Deploy Signed Images:
- Sign Images: Use the signing key to sign images from the trusted source before pushing them to the container registry.
- Deploy Signed Images: Deploy the signed images to your Kubernetes cluster. The Admission Controller will verity their signatures before allowing the deployment.
Example:

This example uses the 'image-signature-validator' container image available on Quay.i0. The 'config.yamr file in the ConfigMap defines the signing key and trusted image sources. Remember to replace these values with your actual information.

| # 36
Enable audit logs in the cluster, To Do so, enable the log backend, and ensure that
1. logs are stored at /var/log/kubernetes/kubernetes-logs.txt.
2. Log files are retained for 5 days.
3. at maximum, a number of 10 old audit logs files are retained.
Edit and extend the basic policy to log:
  • A. 1. Cronjobs changes at RequestResponse
⣺A
h
2. Log the request body of deployments changes in the namespace kube-system.
3. Log all other resources in core and extensions at the Request level.
4. Don't log watch requests by the "system:kube-proxy" on endpoints or

| # 37
SIMULATION
use the Trivy to scan the following images,
1. amazonlinux:1
2. k8s.gcr.io/kube-controller-manager:v1.18.6
Look for images with HIGH or CRITICAL severity vulnerabilities and store the output of the same in /opt/trivy-vulnerable.txt
  • A. Send us the Feedback on it.
⣺A

| # 38
You are managing a Kubernetes cluster with a deployment named 'database-deployment' running 3 replicas of a PostgreSQL database container. You need to implement a security policy that restricts the database pods from accessing the internet, allowing them to only communicate with each other and with specific external services. The allowed external services include a dedicated monitoring service at 'monitoring-example-com:8080' and a logging service at 'logging-example-com:514'. Additionally, you want to enforce this policy using NetworkPolicy.

h
Solution (Step by Step) :
1. Create a NetworkPolicy for database pods:
- Create a YAML file named "database-networkpolicy.yamr with the following contents:



| # 39
Imagine a scenario where you nave multiple Kubernetes clusters. You want to establish a secure supply chain by allowing only images from a centralized image registry to be deployed across all clusters. Explain how you can achieve this.

h
Solution (Step by Step) :
1. Centralized Image Registry:
- Set up a centralized image registry that will serve as the single source of truth for all container images-
- Some popular choices include:
- Docker Hub: A public registry with a free tier for personal and open-source projects.
- Harbor: An open-source registry with features like vulnerability scanning and access control.
- Google Container Registry (GCR): A registry integrated with Google Cloud Platform, offering features like image signing and storage management.
2. Configure Cluster Access:
- Ensure all your Kubernetes clusters have access to this centralized image registry.
- For private registries, configure authentication and authorization mechanisms to control which clusters have access to which images.
3. Implement Image Pull Policies:
- On each cluster, set the 'imagePullPolicy' to 'Always' for deployments using images from the centralized registry. This ensures that every pod pulls
the image directly from the registry, avoiding reliance on cached images.
- Example (for a deployment using 'nginx:latest' from a private registry):

4. Enable Image Signing (Optional): - Implement image signing to further enhance security - Sign images in the centralized registry using a trusted key - Configure Kubernetes clusters to only allow images signed with the trusted key to be deployed. 5. Monitoring and Auditing: - Implement robust monitoring and auditing to track image pulls, deployments, and any potential vulnerabilities. 6. Consider a Software Supply Chain Management (SSCM) Tool: - Use a dedicated SSCM tool to manage the entire image lifecycle, including vulnerability scanning, policy enforcement, and access control. Tools like JFrog Xray or Aqua Security can help automate this process.

| # 40
......
CKS}^ȥԇYΥǩ`ˤä_kơ¤Linux FoundationԇY֪R򺬤ƤޤʤԇYʂ䤷CKSԇYϸ񤹤Ҫʤ顢ҡΆ}Ϥʤ뤳ȤǤޤҡȫĤ|ߤCKS}ϤʤΕrgȽUgΥȤp٤ơʤԇYؤκϸ뤳ȤǤޤ
CKST֪RӖ: https://www.topexam.jp/CKS_shiken.html
BONUS Topexam CKSפһoϤǥ`ɣhttps://drive.google.com/open?id=1ALVpTTQ49ixvzHV8GjrjbEoiDHT4Peb7
Reply

Use props Report

69

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
69
Posted at 2/10/2026 01:24:15        Only Author  2#
Thank you for your article; it is truly outstanding! This C_THR88_2505 reliable test prep helped me get promoted and earn more. Now, its free for everyone. Wishing you all success in reaching your promotions!
Reply

Use props Report

You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list