vania-janet/multiturn-rag-retrieval-data huggingface dataset:
1.3.1 Ensure that the --terminated-pod-gc-threshold argument is set as appropriate Scored 1 Pass IBM 
 1.3.2 Ensure that the --profiling argument is set to false Scored 1 Pass IBM 
 1.3.3 Ensure that the --use-service-account-credentials argument is set to true Scored 1 Pass IBM 
 1.3.4 Ensure that the --service-account-private-key-file argument is set as appropriate Scored 1 Pass IBM 
 1.3.5 Ensure that the --root-ca-file argument is set as appropriate Scored 1 Pass IBM 
 1.3.6 Ensure that the RotateKubeletServerCertificate argument is set to true Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-127cis-benchmark-remediations-127) IBM 
 1.3.7 Ensure that the --bind-address argument is set to 127.0.0.1 Scored 1 Pass IBM 







 1.4 Scheduler 



Section 1.4 Scheduler benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 1.4.1 Ensure that the --profiling argument is set to false Scored 1 Pass IBM 
 1.4.2 Ensure that the --bind-address argument is set to 127.0.0.1 Scored 1 Pass IBM 









 2 Etcd node configuration 

Review the Etcd Node Configuration results of the version 1.5 CIS Kubernetes benchmark.



Section 2 Etcd node configuration benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 2.1 Ensure that the --cert-file and --key-file arguments are set as appropriate Scored 1 Pass IBM 
 2.2 Ensure that the --client-cert-auth argument is set to true Scored 1 Pass IBM 
 2.3 Ensure that the --auto-tls argument is not set to true Scored 1 Pass IBM 
 2.4 Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate Scored 1 Pass IBM 
 2.5 Ensure that the --peer-client-cert-auth argument is set to true Scored 1 Pass IBM
A low recall score indicates that the machine learning model failed to create annotations that it should have created.





 Causes 

Low recall scores can occur for many different reasons that depend on the domain, type system complexity, appropriateness of training documents, human annotator skills, and other factors.





 Resolving the problem 

Tune the performance of your machine learning model by performing one or more of following steps then retrain your model:



1. Identify commonly occurring types with low recall.
2. Identify commonly confused types. This information can be found by looking at the numbers that are off the diagonal in the confusion matrix.
3. Review errors where the machine learning model has high confidence.
4. Find patterns in the false positives in the confusion matrix.
5. If certain types have low recall scores, review the clarity of the annotation guidelines that apply to those types.



![How to resolve low recall scores.](https://cloud.ibm.com/docs-content/v1/content/148d3bd95f946aa1bb53ea1540475f522e6b61c9/watson-knowledge-studio-data/images/wks_lowrecall.svg)

Figure 3. How to resolve low recall scores
The threshold is a double-precision number in the range 0.0 - 1.0 that indicates the minimum ratio of pattern size to sublist. For example, a threshold of 0.75 means that the specified pattern must match at least 75% of the time series values, in sequence and contiguously. If the threshold is met, the pattern is considered to match, and the function that uses the matcher returns the observations that correspond to the pattern; otherwise, the function returns null.

TS_MATCHER_SUBSEQ_PS(Double) Output: MatcherType
Creates a matcher that matches an array of string values (the pattern) with a subsequence of a string time series, to within the specified coverage threshold. The threshold is a double-precision number in the range 0.0 - 1.0 that indicates the minimum ratio of pattern size to sequence size. For example, a threshold of 0.75 means that the specified pattern must match at least 75% of the sequence of time series values, in sequence but not necessarily contiguously. If the threshold is met, the pattern is considered to match, and the function that uses the matcher returns the observations that correspond to the pattern; otherwise, the function returns null.

TS_MATCHER_SUBSEQ_PM(Double) Output: MatcherType
Creates a matcher that matches an array of string values (the pattern) with a subsequence of a string time series, to within the specified coverage threshold. The threshold is a double-precision number in the range 0.0 - 1.0 that indicates the minimum ratio of pattern size to match string size. For example, a threshold of 0.75 means that the specified pattern must match at least 75% of the match string, in sequence but not necessarily contiguously. If the threshold is met, the pattern is considered to match, and the function that uses the matcher returns the observations that correspond to the pattern; otherwise, the function returns null.

TS_MATCHER_SUBSEQ_MS(Double) Output: MatcherType
Creates a matcher that matches an array of string values (the pattern) with a subsequence of a string time series, to within the specified coverage threshold.
(https://cloud.ibm.com/docs-content/v1/content/50eddb8fd81f33092880335ff107a78ff5cd0f65/watson-knowledge-studio/images/wks_tutiaa2.png)
4. After you review the scores, you can decide whether you want to approve or reject document sets that are in the SUBMITTED status. Take one of these actions:



* If the scores are acceptable for an annotation set, select the check box and click Accept. Documents that do not overlap with other document sets are promoted to ground truth. Documents that do overlap must first be reviewed through adjudication so that conflicts can be resolved. For this tutorial, accept both document sets.
* If the scores are not acceptable for an annotation set, select the check box and click Reject. The document set needs to be revisited by the human annotator to improve the annotations.









 Results 

When you evaluated the inter-annotator agreement scores, you saw how different pairs of human annotators annotated the same document. If the inter-annotator agreement score was acceptable, you accepted the document set.







 Lesson 6: Adjudicating conflicts in annotated documents 

In this lesson, you will learn how to adjudicate conflicts in documents that overlap between document sets in Knowledge Studio.



 About this task 

When you approve a document set, only the documents that do not overlap with other document sets are promoted to ground truth. If a document is part of the overlap between multiple document sets, you must adjudicate any annotation conflicts before the document can be promoted to ground truth.

For more information about adjudication, see [Building the ground truth](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-build-groundtruth).





 Procedure 



1. Log in to Knowledge Studio as the administrator and select Machine Learning Model > Annotations. Click the Annotation Tasks tab, then click the Test task.
2. Verify that the two document sets are in an approved state.
3.
Not Scored 1 [Pass](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-124cis-benchmark-remediations-124) Shared 
 5.2.9 Minimize the admission of containers with capabilities assigned. Not Scored 2 [Pass](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-124cis-benchmark-remediations-124) Shared 







 5.3 Network policies and CNI 



Section 5.3 Network policies and CNI benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 5.3.1 Ensure that the CNI in use supports network policies. Not Scored 1 Pass IBM 
 5.3.2 Ensure that all namespaces have network policies defined. Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-124cis-benchmark-remediations-124) Shared 







 5.4 Secrets management 



Section 5.4 Secrets management benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 5.4.1 Prefer using secrets as files over secrets as environment variables. Not Scored 1 Pass Shared 
 5.4.2 Consider external secret storage. Not Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-124cis-benchmark-remediations-124) Shared 







 5.5 Extensible admission control 



Section 5.5 Extensible admission control benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 5.5.1 Configure Image Provenance using ImagePolicyWebhook admission controller. Not Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-124cis-benchmark-remediations-124) Shared 







 5.6 General policies 



Section 5.6 General policies benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 5.6.1 Create administrative boundaries between resources using namespaces. Not Scored 1 Pass Shared
Scored 1 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-125cis-benchmark-remediations-125) Shared 
 1.2.26 Ensure that the --request-timeout option is set as appropriate. Scored 1 Pass IBM 
 1.2.27 Ensure that the --service-account-lookup option is set to true. Scored 1 Pass IBM 
 1.2.28 Ensure that the --service-account-key-file option is set as appropriate. Scored 1 Pass IBM 
 1.2.29 Ensure that the --etcd-certfile and --etcd-keyfile options are set as appropriate. Scored 1 Pass IBM 
 1.2.30 Ensure that the --tls-cert-file and --tls-private-key-file options are set as appropriate. Scored 1 Pass IBM 
 1.2.31 Ensure that the --client-ca-file option is set as appropriate. Scored 1 Pass IBM 
 1.2.32 Ensure that the --etcd-cafile option is set as appropriate. Scored 1 Pass IBM 
 1.2.33 Ensure that the --encryption-provider-config option is set as appropriate. Scored 1 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-125cis-benchmark-remediations-125) Shared 
 1.2.34 Ensure that encryption providers are appropriately configured. Scored 1 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-125cis-benchmark-remediations-125) Shared 
 1.2.35 Ensure that the API server makes use of only Strong Cryptographic Ciphers. Not Scored 1 Pass IBM 







 1.3 Controller manager 



Section 1.3 Controller manager benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 1.3.1 Ensure that the --terminated-pod-gc-threshold option is set as appropriate. Scored 1 Pass IBM
Not Scored 1 [Pass](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-123cis-benchmark-remediations-123) Shared 
 5.2.9 Minimize the admission of containers with capabilities assigned. Not Scored 2 [Pass](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-123cis-benchmark-remediations-123) Shared 







 5.3 Network policies and CNI 



Section 5.3 Network policies and CNI benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 5.3.1 Ensure that the CNI in use supports network policies. Not Scored 1 Pass IBM 
 5.3.2 Ensure that all namespaces have network policies defined. Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-123cis-benchmark-remediations-123) Shared 







 5.4 Secrets management 



Section 5.4 Secrets management benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 5.4.1 Prefer using secrets as files over secrets as environment variables. Not Scored 1 Pass Shared 
 5.4.2 Consider external secret storage. Not Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-123cis-benchmark-remediations-123) Shared 







 5.5 Extensible admission control 



Section 5.5 Extensible admission control benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 5.5.1 Configure Image Provenance using ImagePolicyWebhook admission controller. Not Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-123cis-benchmark-remediations-123) Shared 







 5.6 General policies 



Section 5.6 General policies benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 5.6.1 Create administrative boundaries between resources using namespaces. Not Scored 1 Pass Shared
(https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-zones)

Compliance posture information displayed includes:

Zone/Policy
: Indicates the zones where policies have been defined in your environment.

Passing Score
: Indicates the percentage of policy requirements that are passing. The higher the percentage the more compliant your system is.

Requirements Failing
: Indicates the number of policy requirements that need to be fixed to get the passing score to 100%. These are displayed as a bar chart displaying the results from the last 7 days. Requirements are comprised of one or more controls.

Controls to Fix
: Indicates the number of controls that need to be remediated to achieve a 100% passing score.

Multiple controls comprise a single requirement. So, the number controls to fix will always be larger that the number of failing requirements.

Resource Violations by Severity
: Each control has a defined severity. This severity can be high, medium, or low. Resource violations by severity indicates the number of resources failing based on severity.

One resource can have multiple controls and can be counted multiple times; once for each failing control.

Accepted Risks
: Indicates the controls that have been evaluated as accepted.

One control can affect multiple resources, so a number of resources can display the same controls as accepted risks.





 Reviewing details 

You can see more information about a zone or policy by clicking the row. A Results page is displayed with the compliance details.



 Filtering details 

By default the top 50 results are displayed with the highest number of failures by severity displayed first. You can filter the results to see additional controls or to limit the displayed data.

You can filter the view by the zones and policies, types of findings and even by individual requirements or controls. The view can also be filtered to show failing controls by severity (high, medium, and low).





 Reviewing the control plane 

From the details page you can click on a requirement or control to see the sub-requirements and controls that make up the requirement or control. Each items indicates if it is passing or failing. If even one sub-requirement or control is failing, the overall requirement or control is marked as failing.
"issues": 134,132,342],// link(s) to the issue(s) created to track the bugs found during the test run. Should be populated only if the test failed
"required": "yes" | "no" ] // yes: this is an auditable step; no: this is a non auditable step
}, {
"evidence_type_id": "com.ibm.acceptance_tests",
"version": "1.0.0",
"date": "2020-05-06T12:00:00Z", // date of task run
"origin": {
"url":"https://us-south.git.cloud.ibm.com/open-toolchain/compliance-pipelines/-/blob/master/definitions/mytask.yaml", // where the task is taken from
"version": "423792" // commit id representing the task version used to produce the evidence
}
"toolchain_crn": "crn:v1:bluemix:public:toolchain:us-south:a/190e0b4ce4cd013159917665213ddc51:7467a214-f404-4e23-acab-2e57e935d138::" // CRN of the toolchain
"pipeline_id": "b1cfb6a4-813d-4fec-bbf7-ce662e8ce4e0", // the id of the pipeline that generated this piece of evidence
"pipeline_run_id": 12345, // this is the id of the pipeline run that generated this piece of evidence
"result": "passed"|"failed"], // the result of the test
"log": {
"url": "https://acme.org/log.txt", // the link to where the actual log of the test is
"hash": "abc123", // the hash of the log file
},
Not Scored 1 [Pass](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-46cis-benchmark-remediations-46) Shared 
 5.2.8 Minimize the admission of containers with added capabilities. Not Scored 1 [Pass](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-46cis-benchmark-remediations-46) Shared 
 5.2.9 Minimize the admission of containers with capabilities assigned. Not Scored 2 [Pass](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-46cis-benchmark-remediations-46) Shared 







 5.3 Network policies and CNI 



Section 5.3 Network policies and CNI benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 5.3.1 Ensure that the CNI in use supports Network Policies. Not Scored 1 Pass IBM 
 5.3.2 Ensure that all Namespaces have Network Policies defined. Scored 2 [Fail](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-46cis-benchmark-remediations-46) Shared 







 5.4 Secrets management 



Section 5.4 Secrets management benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 5.4.1 Prefer using secrets as files over secrets as environment variables. Not Scored 1 [Fail](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-46cis-benchmark-remediations-46) Shared 
 5.4.2 Consider external secret storage. Not Scored 2 [Fail](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-46cis-benchmark-remediations-46) Shared 







 5.5 Extensible admission control 



Section 5.5 Extensible admission control benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility
Not Scored 1 [Pass](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-remediations-122) Shared 
 5.2.9 Minimize the admission of containers with capabilities assigned. Not Scored 2 [Pass](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-remediations-122) Shared 







 5.3 Network policies and CNI 



Section 5.3 Network policies and CNI benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 5.3.1 Ensure that the CNI in use supports network policies. Not Scored 1 Pass IBM 
 5.3.2 Ensure that all namespaces have network policies defined. Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-remediations-122) Shared 







 5.4 Secrets management 



Section 5.4 Secrets management benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 5.4.1 Prefer using secrets as files over secrets as environment variables. Not Scored 1 Pass Shared 
 5.4.2 Consider external secret storage. Not Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-remediations-122) Shared 







 5.5 Extensible admission control 



Section 5.5 Extensible admission control benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 5.5.1 Configure Image Provenance using ImagePolicyWebhook admission controller. Not Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-remediations-122) Shared 







 5.6 General policies 



Section 5.6 General policies benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 5.6.1 Create administrative boundaries between resources using namespaces. Not Scored 1 Pass Shared
<ScoreDistribution value="Iris-setosa" recordCount="33" confidence="0.314285714285714"/>
<ScoreDistribution value="Iris-versicolor" recordCount="35" confidence="0.333333333333333"/>
<ScoreDistribution value="Iris-virginica" recordCount="37" confidence="0.352380952380952"/>
<Node id="2" score="Iris-setosa" recordCount="33">
<SimplePredicate field="petal_length" operator="lessThan" value="2.6"/>
<ScoreDistribution value="Iris-setosa" recordCount="33" confidence="1"/>
<ScoreDistribution value="Iris-versicolor" recordCount="0" confidence="0"/>
<ScoreDistribution value="Iris-virginica" recordCount="0" confidence="0"/>
</Node>
<Node id="3" score="Iris-virginica" recordCount="72" defaultChild="7">
<SimplePredicate field="petal_length" operator="greaterOrEqual" value="2.6"/>
<ScoreDistribution value="Iris-setosa" recordCount="0" confidence="0"/>
<ScoreDistribution value="Iris-versicolor" recordCount="35" confidence="0.486111111111111"/>
<ScoreDistribution value="Iris-virginica" recordCount="37" confidence="0.513888888888889"/>
<Node id="6" score="Iris-versicolor" recordCount="37">
<SimplePredicate field="petal_length" operator="lessThan" value="4.85"/>
The value lies in the range of 0.0 to 1.0.
* high_frequency_loss indicates the probability that the audio signal is missing the upper half of its frequency content.



* A value close to 1.0 typically indicates artificially up-sampled audio, which negatively impacts the accuracy of the transcription results.
* A value at or near 0.0 indicates that the audio signal is good and has a full spectrum.
* A value around 0.5 means that detection of the frequency content is unreliable or unavailable.





The following fields of the AudioMetricsDetails object provide histograms for signal characteristics. Each field provides an array of AudioMetricsHistogramBin objects. A single unit in each histogram is calculated based on a sampling_interval length of audio.



* direct_current_offset defines a histogram of the cumulative direct current (DC) component of the audio signal.
* clipping_rate defines a histogram of the clipping rate for the audio segments. The clipping rate is defined as the fraction of samples in the segment that reach the maximum or minimum value that is offered by the audio quantization range.

The service auto-detects either a 16-bit Pulse-Code Modulation (PCM) audio range (-32768 to +32767) or a unit range (-1.0 to +1.0). The clipping rate is between 0.0 and 1.0. Higher values indicate possible degradation of speech recognition.
* speech_level defines a histogram of the signal level in segments of the audio that contain speech. The signal level is computed as the Root-Mean-Square (RMS) value in a decibel (dB) scale normalized to the range 0.0 (minimum level) to 1.0 (maximum level).
* non_speech_level defines a histogram of the signal level in segments of the audio that do not contain speech. The signal level is computed as the RMS value in a decibel scale normalized to the range 0.0 (minimum level) to 1.0 (maximum level).



Each AudioMetricsHistogramBin object describes a bin with defined begin and end boundaries.
Section 2 Etcd Node Configuration benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 2.1 Ensure that the --cert-file and --key-file options are set as appropriate. Scored 1 Pass IBM 
 2.2 Ensure that the --client-cert-auth option is set to true. Scored 1 Pass IBM 
 2.3 Ensure that the --auto-tls option is not set to true. Scored 1 Pass IBM 
 2.4 Ensure that the --peer-cert-file and --peer-key-file options are set as appropriate. Scored 1 Pass IBM 
 2.5 Ensure that the --peer-client-cert-auth option is set to true. Scored 1 Pass IBM 
 2.6 Ensure that the --peer-auto-tls option is not set to true. Scored 1 Pass IBM 
 2.7 Ensure that a unique Certificate Authority is used for etcd. Not Scored 2 Pass IBM 







 3 Control plane configuration 

Review the Control Plane Configuration results of the version 1.5 CIS Kubernetes benchmark.



 3.1 Authentication and authorization 



Section 3.1 Authentication and Authorization benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 3.1.1 Client certificate authentication should not be used for users. Not Scored 2 Pass Shared 







 3.2 Logging 



Section 3.2 Logging benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 3.2.1 Ensure that a minimal audit policy is created. Scored 1 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-124cis-benchmark-remediations-124) Shared 
 3.2.2 Ensure that the audit policy covers key security concerns. Not Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-124cis-benchmark-remediations-124) Shared 









 4 Worker node security configuration 

Review the Worker Node Security Configuration results of the version 1.5 CIS Kubernetes benchmark.



 4.1 Worker node configuration files