What's more, part of that TestsDumps CKS dumps now are free: https://drive.google.com/open?id=1Sk3rNI1UGgAT0Un7qDzz-K6fkhKDcy1K
In the same way, IE, Firefox, Opera and Safari, and all the major browsers support the web-based Linux Foundation CKS practice test. So it requires no special plugins. The web-based Certified Kubernetes Security Specialist (CKS) (CKS) practice exam software is genuine, authentic, and real so feel free to start your practice instantly with Certified Kubernetes Security Specialist (CKS) (CKS) practice test.
The CKS Certification Exam is an industry-recognized certification that is highly valued by employers. It demonstrates that the candidate has the skills and knowledge required to secure containerized applications and Kubernetes platforms, making them a valuable asset to any organization. Certified Kubernetes Security Specialist (CKS) certification is also an excellent way for professionals to showcase their expertise and differentiate themselves from others in the field.
Related study materials proved that to pass the Linux Foundation CKS exam certification is very difficult. But do not be afraid, TestsDumps have many IT experts who have plentiful experience. After years of hard work they have created the most advanced Linux Foundation CKS Exam Training materials. TestsDumps have the best resource provided for you to pass the exam. Does not require much effort, you can get a high score. Choose the TestsDumps's Linux Foundation CKS exam training materials for your exam is very helpful.
Linux Foundation CKS (Certified Kubernetes Security Specialist) Certification Exam is a highly respected certification for IT professionals who are looking to demonstrate their expertise in Kubernetes security. Certified Kubernetes Security Specialist (CKS) certification is designed to test the knowledge and skills of IT professionals who are responsible for securing Kubernetes clusters and workloads. CKS Exam covers a wide range of topics, including Kubernetes security features, network security, storage security, and compliance.
NEW QUESTION # 60
You must complete this task on the following cluster/nodes: Cluster: trace Master node: master Worker node: worker1 You can switch the cluster/configuration context using the following command: [desk@cli] $ kubectl config use-context trace Given: You may use Sysdig or Falco documentation. Task: Use detection tools to detect anomalies like processes spawning and executing something weird frequently in the single container belonging to Pod tomcat. Two tools are available to use: 1. falco 2. sysdig Tools are pre-installed on the worker1 node only. Analyse the container's behaviour for at least 40 seconds, using filters that detect newly spawning and executing processes. Store an incident file at /home/cert_masters/report, in the following format: [timestamp],[uid],[processName] Note: Make sure to store incident file on the cluster's worker node, don't move it to master node.
Answer:
Explanation:
$vim /etc/falco/falco_rules.local.yaml
- rule: Container Drift Detected (open+create)
desc: New executable created in a container due to open+create
condition: >
evt.type in (open,openat,creat) and
evt.is_open_exec=true and
container and
not runc_writing_exec_fifo and
not runc_writing_var_lib_docker and
not user_known_container_drift_activities and
evt.rawres>=0
output: >
%evt.time,%user.uid,%proc.name # Add this/Refer falco documentation
priority: ERROR
$kill -1 <PID of falco>
Explanation
[desk@cli] $ ssh node01 [node01@cli] $ vim /etc/falco/falco_rules.yaml search for Container Drift Detected & paste in falco_rules.local.yaml [node01@cli] $ vim /etc/falco/falco_rules.local.yaml
- rule: Container Drift Detected (open+create)
desc: New executable created in a container due to open+create
condition: >
evt.type in (open,openat,creat) and
evt.is_open_exec=true and
container and
not runc_writing_exec_fifo and
not runc_writing_var_lib_docker and
not user_known_container_drift_activities and
evt.rawres>=0
output: >
%evt.time,%user.uid,%proc.name # Add this/Refer falco documentation
priority: ERROR
[node01@cli] $ vim /etc/falco/falco.yaml
NEW QUESTION # 61
You can switch the cluster/configuration context using the following command: [desk@cli] $ kubectl config use-context stage Context: A PodSecurityPolicy shall prevent the creation of privileged Pods in a specific namespace. Task: 1. Create a new PodSecurityPolcy named deny-policy, which prevents the creation of privileged Pods. 2. Create a new ClusterRole name deny-access-role, which uses the newly created PodSecurityPolicy deny-policy. 3. Create a new ServiceAccount named psd-denial-sa in the existing namespace development. Finally, create a new ClusterRoleBindind named restrict-access-bind, which binds the newly created ClusterRole deny-access-role to the newly created ServiceAccount psp-denial-sa
Answer:
Explanation:
Create psp to disallow privileged container
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: deny-access-role
rules:
- apiGroups: ['policy']
resources: ['podsecuritypolicies']
verbs: ['use']
resourceNames:
- "deny-policy"
k create sa psp-denial-sa -n development
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: restrict-access-bing
roleRef:
kind: ClusterRole
name: deny-access-role
apiGroup: rbac.authorization.k8s.io
subjects:
- kind: ServiceAccount
name: psp-denial-sa
namespace: development
Explanation
master1 $ vim psp.yaml
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
name: deny-policy
spec:
privileged: false # Don't allow privileged pods!
seLinux:
rule: RunAsAny
supplementalGroups:
rule: RunAsAny
runAsUser:
rule: RunAsAny
fsGroup:
rule: RunAsAny
volumes:
- '*'
master1 $ vim cr1.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: deny-access-role
rules:
- apiGroups: ['policy']
resources: ['podsecuritypolicies']
verbs: ['use']
resourceNames:
- "deny-policy"
master1 $ k create sa psp-denial-sa -n development master1 $ vim cb1.yaml apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata:
name: restrict-access-bing
roleRef:
kind: ClusterRole
name: deny-access-role
apiGroup: rbac.authorization.k8s.io
subjects:
# Authorize specific service accounts:
- kind: ServiceAccount
name: psp-denial-sa
namespace: development
master1 $ k apply -f psp.yaml master1 $ k apply -f cr1.yaml master1 $ k apply -f cb1.yaml Reference: https://kubernetes.io/docs/concepts/policy/pod-security-policy/
NEW QUESTION # 62
SIMULATION
Enable audit logs in the cluster, To Do so, enable the log backend, and ensure that
1. logs are stored at /var/log/kubernetes-logs.txt.
2. Log files are retained for 12 days.
3. at maximum, a number of 8 old audit logs files are retained.
4. set the maximum size before getting rotated to 200MB
Edit and extend the basic policy to log:
1. namespaces changes at RequestResponse
2. Log the request body of secrets changes in the namespace kube-system.
3. Log all other resources in core and extensions at the Request level.
4. Log "pods/portforward", "services/proxy" at Metadata level.
5. Omit the Stage RequestReceived
All other requests at the Metadata level
Answer:
Explanation:
Kubernetes auditing provides a security-relevant chronological set of records about a cluster. Kube-apiserver performs auditing. Each request on each stage of its execution generates an event, which is then pre-processed according to a certain policy and written to a backend. The policy determines what's recorded and the backends persist the records.
You might want to configure the audit log as part of compliance with the CIS (Center for Internet Security) Kubernetes Benchmark controls.
The audit log can be enabled by default using the following configuration in cluster.yml:
services:
kube-api:
audit_log:
enabled: true
When the audit log is enabled, you should be able to see the default values at /etc/kubernetes/audit-policy.yaml The log backend writes audit events to a file in JSONlines format. You can configure the log audit backend using the following kube-apiserver flags:
--audit-log-path specifies the log file path that log backend uses to write audit events. Not specifying this flag disables log backend. - means standard out
--audit-log-maxage defined the maximum number of days to retain old audit log files
--audit-log-maxbackup defines the maximum number of audit log files to retain
--audit-log-maxsize defines the maximum size in megabytes of the audit log file before it gets rotated If your cluster's control plane runs the kube-apiserver as a Pod, remember to mount the hostPath to the location of the policy file and log file, so that audit records are persisted. For example:
--audit-policy-file=/etc/kubernetes/audit-policy.yaml \
--audit-log-path=/var/log/audit.log
NEW QUESTION # 63
Task
Create a NetworkPolicy named pod-access to restrict access to Pod users-service running in namespace dev-team.
Only allow the following Pods to connect to Pod users-service:
Answer:
Explanation:
NEW QUESTION # 64
You are a security engineer tasked with securing your organization's container registry. You need to ensure that only authorized users can push images to the registry, while other users can only pull them. Explain how you would implement this using RBAC in Kubernetes and provide a detailed configuration example.
Answer:
Explanation:
Solution (Step by Step) :
1. Create a Service Account for Registry Operations:
- Create a service account specifically for registry operations:
2. Create a Role for Registry Pushers: - Define a role that grants push access to the registry:
3. Create a RoleBinding to Associate the Role with the Service Account: - Bind the 'registry-pusher role to the 'registry-operator' service account:
- Apply the role binding definition: bash kubectl apply -f role-binding.yaml 4. Create a Role for Registry Pullers: - Define a role that grants pull access to the registry:
5. Create a RoleBinding to Associate the Role with Users/Service Accounts: - Bind the 'registry-puller role to the desired users or service accounts:
- Apply the role binding definitiom bash kubectl apply -f role-binding.yaml 6. Configure the Registry (Example with Harbor): - In your registry (e.g., Harbor), create project-level permissions and map them to the service accounts you created. This step might involve creating users and groups in Harbor and then associating them with the appropriate projects and roles. By following these steps, you can securely control access to your container registry, allowing only authorized users to push images and restricting others to pulling only.
NEW QUESTION # 65
......
CKS Reasonable Exam Price: https://www.testsdumps.com/CKS_real-exam-dumps.html
BONUS!!! Download part of TestsDumps CKS dumps for free: https://drive.google.com/open?id=1Sk3rNI1UGgAT0Un7qDzz-K6fkhKDcy1K