Merge branch 'PRWLR-7300-create-ia-c-provider' into PRWLR-7318-add-ia-c-provider-tests

prowler/compliance/kubernetes/cis_1.10_kubernetes.json

@@ -708,7 +708,7 @@
         {
           "Section": "1 Control Plane Components",
           "SubSection": "1.2 API Server",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Automated",
           "Description": "Automate service accounts management.",
           "RationaleStatement": "When you create a pod, if you do not specify a service account, it is automatically assigned the `default` service account in the same namespace. You should create your own service account and let the API server manage its security tokens.",
@@ -731,7 +731,7 @@
         {
           "Section": "1 Control Plane Components",
           "SubSection": "1.2 API Server",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Automated",
           "Description": "Reject creating objects in a namespace that is undergoing termination.",
           "RationaleStatement": "Setting admission control policy to `NamespaceLifecycle` ensures that objects cannot be created in non-existent namespaces, and that namespaces undergoing termination are not used for creating the new objects. This is recommended to enforce the integrity of the namespace termination process and also for the availability of the newer objects.",
@@ -754,7 +754,7 @@
         {
           "Section": "1 Control Plane Components",
           "SubSection": "1.2 API Server",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Automated",
           "Description": "Limit the `Node` and `Pod` objects that a kubelet could modify.",
           "RationaleStatement": "Using the `NodeRestriction` plug-in ensures that the kubelet is restricted to the `Node` and `Pod` objects that it could modify as defined. Such kubelets will only be allowed to modify their own `Node` API object, and only modify `Pod` API objects that are bound to their node.",
@@ -1458,7 +1458,7 @@
       "Attributes": [
         {
           "Section": "2 etcd",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Use a different certificate authority for etcd from the one used for Kubernetes.",
           "RationaleStatement": "etcd is a highly available key-value store used by Kubernetes deployments for persistent storage of all of its REST API objects. Its access should be restricted to specifically designated clients and peers only. Authentication to etcd is based on whether the certificate presented was issued by a trusted certificate authority. There is no checking of certificate attributes such as common name or subject alternative name. As such, if any attackers were able to gain access to any certificate issued by the trusted certificate authority, they would be able to gain full access to the etcd database.",
@@ -1563,7 +1563,7 @@
         {
           "Section": "3 Control Plane Configuration",
           "SubSection": "3.2 Logging",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Ensure that the audit policy created for the cluster covers key security concerns.",
           "RationaleStatement": "Security audit logs should cover access and modification of key resources in the cluster, to enable them to form an effective part of a security environment.",
@@ -1967,7 +1967,7 @@
         {
           "Section": "4 Worker Nodes",
           "SubSection": "4.2 Kubelet",
-          "Profile": "Level 2 - Worker Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Security relevant information should be captured. The eventRecordQPS on the Kubelet configuration can be used to limit the rate at which events are gathered and sets the maximum event creations per second. Setting this too low could result in relevant events not being logged, however the unlimited setting of `0` could result in a denial of service on the kubelet.",
           "RationaleStatement": "It is important to capture all events and not restrict event creation. Events are an important source of security information and analytics that ensure that your environment is consistently monitored using the event data.",
@@ -2549,7 +2549,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.2 Ensure that the cluster has at least one active policy control mechanism in place",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Do not generally permit containers to be run as the root user.",
           "RationaleStatement": "Containers may run as any Linux user. Containers which run as the root user, whilst constrained by Container Runtime security features still have a escalated likelihood of container breakout.Ideally, all containers should run as a defined non-UID 0 user.There should be at least one admission control policy defined which does not permit root containers.If you need to run root containers, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
@@ -2618,7 +2618,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.2 Ensure that the cluster has at least one active policy control mechanism in place",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Do not generally permit containers with capabilities",
           "RationaleStatement": "Containers run with a default set of capabilities as assigned by the Container Runtime. Capabilities are parts of the rights generally granted on a Linux system to the root user.In many cases applications running in containers do not require any capabilities to operate, so from the perspective of the principal of least privilege use of capabilities should be minimized.",
@@ -2727,7 +2727,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.3 Network Policies and CNI",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Use network policies to isolate traffic in your cluster network.",
           "RationaleStatement": "Running different applications on the same Kubernetes cluster creates a risk of one compromised application attacking a neighboring application. Network segmentation is important to ensure that containers can communicate only with those they are supposed to. A network policy is a specification of how selections of pods are allowed to communicate with each other and other network endpoints. Network Policies are namespace scoped. When a network policy is introduced to a given namespace, all traffic not allowed by the policy is denied. However, if there are no network policies in a namespace all traffic will be allowed into and out of the pods in that namespace.",
@@ -2750,7 +2750,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.4 Secrets Management",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Kubernetes supports mounting secrets as data volumes or as environment variables. Minimize the use of environment variable secrets.",
           "RationaleStatement": "It is reasonably common for application code to log out its environment (particularly in the event of an error). This will include any secret values passed in as environment variables, so secrets can easily be exposed to any user or entity who has access to the logs.",
@@ -2771,7 +2771,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.4 Secrets Management",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Consider the use of an external secrets storage and management system, instead of using Kubernetes Secrets directly, if you have more complex secret management needs. Ensure the solution requires authentication to access secrets, has auditing of access to and use of secrets, and encrypts secrets. Some solutions also make it easier to rotate secrets.",
           "RationaleStatement": "Kubernetes supports secrets as first-class objects, but care needs to be taken to ensure that access to secrets is carefully limited. Using an external secrets provider can ease the management of access to secrets, especially where secrests are used across both Kubernetes and non-Kubernetes environments.",
@@ -2792,7 +2792,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.5 Extensible Admission Control",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Configure Image Provenance for your deployment.",
           "RationaleStatement": "Kubernetes supports plugging in provenance rules to accept or reject the images in your deployments. You could configure such rules to ensure that only approved images are deployed in the cluster.",
@@ -2836,7 +2836,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.7 General Policies",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Enable `docker/default` seccomp profile in your pod definitions.",
           "RationaleStatement": "Seccomp (secure computing mode) is used to restrict the set of system calls applications can make, allowing cluster administrators greater control over the security of workloads running in the cluster. Kubernetes disables seccomp profiles by default for historical reasons. You should enable it to ensure that the workloads have restricted actions available within the container.",
@@ -2857,7 +2857,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.7 General Policies",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Apply Security Context to Your Pods and Containers",
           "RationaleStatement": "A security context defines the operating system security settings (uid, gid, capabilities, SELinux role, etc..) applied to a container. When designing your containers and pods, make sure that you configure the security context for your pods, containers, and volumes. A security context is a property defined in the deployment yaml. It controls the security parameters that will be assigned to the pod/container/volume. There are two levels of security context: pod level security context, and container level security context.",
@@ -2878,7 +2878,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.7 General Policies",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Kubernetes provides a default namespace, where objects are placed if no namespace is specified for them. Placing objects in this namespace makes application of RBAC and other controls more difficult.",
           "RationaleStatement": "Resources in a Kubernetes cluster should be segregated by namespace, to allow for security controls to be applied at that level and to make it easier to manage resources.",

prowler/compliance/kubernetes/cis_1.11_kubernetes.json

@@ -708,7 +708,7 @@
         {
           "Section": "1 Control Plane Components",
           "SubSection": "1.2 API Server",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Automated",
           "Description": "Automate service accounts management.",
           "RationaleStatement": "When you create a pod, if you do not specify a service account, it is automatically assigned the `default` service account in the same namespace. You should create your own service account and let the API server manage its security tokens.",
@@ -731,7 +731,7 @@
         {
           "Section": "1 Control Plane Components",
           "SubSection": "1.2 API Server",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Automated",
           "Description": "Reject creating objects in a namespace that is undergoing termination.",
           "RationaleStatement": "Setting admission control policy to `NamespaceLifecycle` ensures that objects cannot be created in non-existent namespaces, and that namespaces undergoing termination are not used for creating the new objects. This is recommended to enforce the integrity of the namespace termination process and also for the availability of the newer objects.",
@@ -754,7 +754,7 @@
         {
           "Section": "1 Control Plane Components",
           "SubSection": "1.2 API Server",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Automated",
           "Description": "Limit the `Node` and `Pod` objects that a kubelet could modify.",
           "RationaleStatement": "Using the `NodeRestriction` plug-in ensures that the kubelet is restricted to the `Node` and `Pod` objects that it could modify as defined. Such kubelets will only be allowed to modify their own `Node` API object, and only modify `Pod` API objects that are bound to their node.",
@@ -1501,7 +1501,7 @@
       "Attributes": [
         {
           "Section": "2 etcd",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Use a different certificate authority for etcd from the one used for Kubernetes.",
           "RationaleStatement": "etcd is a highly available key-value store used by Kubernetes deployments for persistent storage of all of its REST API objects. Its access should be restricted to specifically designated clients and peers only.   Authentication to etcd is based on whether the certificate presented was issued by a trusted certificate authority. There is no checking of certificate attributes such as common name or subject alternative name. As such, if any attackers were able to gain access to any certificate issued by the trusted certificate authority, they would be able to gain full access to the etcd database.",
@@ -1606,7 +1606,7 @@
         {
           "Section": "3 Control Plane Configuration",
           "SubSection": "3.2 Logging",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Ensure that the audit policy created for the cluster covers key security concerns.",
           "RationaleStatement": "Security audit logs should cover access and modification of key resources in the cluster, to enable them to form an effective part of a security environment.",
@@ -2010,7 +2010,7 @@
         {
           "Section": "4 Worker Nodes",
           "SubSection": "4.2 Kubelet",
-          "Profile": "Level 2 - Worker Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Security relevant information should be captured. The eventRecordQPS on the Kubelet configuration can be used to limit the rate at which events are gathered and sets the maximum event creations per second. Setting this too low could result in relevant events not being logged, however the unlimited setting of `0` could result in a denial of service on the kubelet.",
           "RationaleStatement": "It is important to capture all events and not restrict event creation. Events are an important source of security information and analytics that ensure that your environment is consistently monitored using the event data.",
@@ -2163,7 +2163,7 @@
         {
           "Section": "4 Worker Nodes",
           "SubSection": "4.2 Kubelet",
-          "Profile": "Level 2 - Worker Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Ensuring that `--IPAddressDeny` is set to Any will facilitate allowlisting of only IP addresses that are explicitly set with the `--IPAddressAllow` parameter which will block unspecified IP addresses from communicating with the **kubelet** component.",
           "RationaleStatement": "By default, Kubernetes allows any IP address to communicate with the **kubelet** component IP restrictions and IP whitelisting are security best practices and reduce the attack surface of the **kubelet**.",
@@ -2634,7 +2634,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.2 Pod Security Standards",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Do not generally permit containers to be run as the root user.",
           "RationaleStatement": "Containers may run as any Linux user. Containers which run as the root user, whilst constrained by Container Runtime security features still have a escalated likelihood of container breakout.  Ideally, all containers should run as a defined non-UID 0 user.  There should be at least one admission control policy defined which does not permit root containers.  If you need to run root containers, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
@@ -2703,7 +2703,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.2 Pod Security Standards",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Do not generally permit containers with capabilities",
           "RationaleStatement": "Containers run with a default set of capabilities as assigned by the Container Runtime. Capabilities are parts of the rights generally granted on a Linux system to the root user.  In many cases applications running in containers do not require any capabilities to operate, so from the perspective of the principal of least privilege use of capabilities should be minimized.",
@@ -2812,7 +2812,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.3 Network Policies and CNI",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Use network policies to isolate traffic in your cluster network.",
           "RationaleStatement": "Running different applications on the same Kubernetes cluster creates a risk of one compromised application attacking a neighboring application. Network segmentation is important to ensure that containers can communicate only with those they are supposed to. A network policy is a specification of how selections of pods are allowed to communicate with each other and other network endpoints.   Network Policies are namespace scoped. When a network policy is introduced to a given namespace, all traffic not allowed by the policy is denied. However, if there are no network policies in a namespace all traffic will be allowed into and out of the pods in that namespace.",
@@ -2835,7 +2835,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.4 Secrets Management",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Kubernetes supports mounting secrets as data volumes or as environment variables. Minimize the use of environment variable secrets.",
           "RationaleStatement": "It is reasonably common for application code to log out its environment (particularly in the event of an error). This will include any secret values passed in as environment variables, so secrets can easily be exposed to any user or entity who has access to the logs.",
@@ -2856,7 +2856,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.4 Secrets Management",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Consider the use of an external secrets storage and management system, instead of using Kubernetes Secrets directly, if you have more complex secret management needs. Ensure the solution requires authentication to access secrets, has auditing of access to and use of secrets, and encrypts secrets. Some solutions also make it easier to rotate secrets.",
           "RationaleStatement": "Kubernetes supports secrets as first-class objects, but care needs to be taken to ensure that access to secrets is carefully limited. Using an external secrets provider can ease the management of access to secrets, especially where secrests are used across both Kubernetes and non-Kubernetes environments.",
@@ -2877,7 +2877,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.5 Extensible Admission Control",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Configure Image Provenance for your deployment.",
           "RationaleStatement": "Kubernetes supports plugging in provenance rules to accept or reject the images in your deployments. You could configure such rules to ensure that only approved images are deployed in the cluster.",
@@ -2921,7 +2921,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.6 General Policies",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Enable `docker/default` seccomp profile in your pod definitions.",
           "RationaleStatement": "Seccomp (secure computing mode) is used to restrict the set of system calls applications can make, allowing cluster administrators greater control over the security of workloads running in the cluster. Kubernetes disables seccomp profiles by default for historical reasons. You should enable it to ensure that the workloads have restricted actions available within the container.",
@@ -2942,7 +2942,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.6 General Policies",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Apply Security Context to Your Pods and Containers",
           "RationaleStatement": "A security context defines the operating system security settings (uid, gid, capabilities, SELinux role, etc..) applied to a container. When designing your containers and pods, make sure that you configure the security context for your pods, containers, and volumes. A security context is a property defined in the deployment yaml. It controls the security parameters that will be assigned to the pod/container/volume. There are two levels of security context: pod level security context, and container level security context.",
@@ -2963,7 +2963,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.6 General Policies",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Kubernetes provides a default namespace, where objects are placed if no namespace is specified for them. Placing objects in this namespace makes application of RBAC and other controls more difficult.",
           "RationaleStatement": "Resources in a Kubernetes cluster should be segregated by namespace, to allow for security controls to be applied at that level and to make it easier to manage resources.",

prowler/compliance/kubernetes/cis_1.8_kubernetes.json

@@ -708,7 +708,7 @@
         {
           "Section": "1 Control Plane Components",
           "SubSection": "1.2 API Server",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "The SecurityContextDeny admission controller can be used to deny pods which make use of some SecurityContext fields which could allow for privilege escalation in the cluster. This should be used where PodSecurityPolicy is not in place within the cluster.",
           "RationaleStatement": "SecurityContextDeny can be used to provide a layer of security for clusters which do not have PodSecurityPolicies enabled.",
@@ -731,7 +731,7 @@
         {
           "Section": "1 Control Plane Components",
           "SubSection": "1.2 API Server",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Automated",
           "Description": "Automate service accounts management.",
           "RationaleStatement": "When you create a pod, if you do not specify a service account, it is automatically assigned the `default` service account in the same namespace. You should create your own service account and let the API server manage its security tokens.",
@@ -754,7 +754,7 @@
         {
           "Section": "1 Control Plane Components",
           "SubSection": "1.2 API Server",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Automated",
           "Description": "Reject creating objects in a namespace that is undergoing termination.",
           "RationaleStatement": "Setting admission control policy to `NamespaceLifecycle` ensures that objects cannot be created in non-existent namespaces, and that namespaces undergoing termination are not used for creating the new objects. This is recommended to enforce the integrity of the namespace termination process and also for the availability of the newer objects.",
@@ -777,7 +777,7 @@
         {
           "Section": "1 Control Plane Components",
           "SubSection": "1.2 API Server",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Automated",
           "Description": "Limit the `Node` and `Pod` objects that a kubelet could modify.",
           "RationaleStatement": "Using the `NodeRestriction` plug-in ensures that the kubelet is restricted to the `Node` and `Pod` objects that it could modify as defined. Such kubelets will only be allowed to modify their own `Node` API object, and only modify `Pod` API objects that are bound to their node.",
@@ -1481,7 +1481,7 @@
       "Attributes": [
         {
           "Section": "2 Etcd",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Use a different certificate authority for etcd from the one used for Kubernetes.",
           "RationaleStatement": "etcd is a highly available key-value store used by Kubernetes deployments for persistent storage of all of its REST API objects. Its access should be restricted to specifically designated clients and peers only.   Authentication to etcd is based on whether the certificate presented was issued by a trusted certificate authority. There is no checking of certificate attributes such as common name or subject alternative name. As such, if any attackers were able to gain access to any certificate issued by the trusted certificate authority, they would be able to gain full access to the etcd database.",
@@ -1586,7 +1586,7 @@
         {
           "Section": "3 Control Plane Configuration",
           "SubSection": "3.2 Logging",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Ensure that the audit policy created for the cluster covers key security concerns.",
           "RationaleStatement": "Security audit logs should cover access and modification of key resources in the cluster, to enable them to form an effective part of a security environment.",
@@ -1990,7 +1990,7 @@
         {
           "Section": "4 Worker Nodes",
           "SubSection": "4.2 Kubelet",
-          "Profile": "Level 2 - Worker Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Security relevant information should be captured. The eventRecordQPS on the Kubelet configuration can be used to limit the rate at which events are gathered and sets the maximum event creations per second. Setting this too low could result in relevant events not being logged, however the unlimited setting of `0` could result in a denial of service on the kubelet.",
           "RationaleStatement": "It is important to capture all events and not restrict event creation. Events are an important source of security information and analytics that ensure that your environment is consistently monitored using the event data.",
@@ -2551,7 +2551,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.2 Pod Security Standards",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Automated",
           "Description": "Do not generally permit containers to be run as the root user.",
           "RationaleStatement": "Containers may run as any Linux user. Containers which run as the root user, whilst constrained by Container Runtime security features still have a escalated likelihood of container breakout.  Ideally, all containers should run as a defined non-UID 0 user.  There should be at least one admission control policy defined which does not permit root containers.  If you need to run root containers, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
@@ -2620,7 +2620,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.2 Pod Security Standards",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Do not generally permit containers with capabilities",
           "RationaleStatement": "Containers run with a default set of capabilities as assigned by the Container Runtime. Capabilities are parts of the rights generally granted on a Linux system to the root user.  In many cases applications running in containers do not require any capabilities to operate, so from the perspective of the principal of least privilege use of capabilities should be minimized.",
@@ -2729,7 +2729,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.3 Network Policies and CNI",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Use network policies to isolate traffic in your cluster network.",
           "RationaleStatement": "Running different applications on the same Kubernetes cluster creates a risk of one compromised application attacking a neighboring application. Network segmentation is important to ensure that containers can communicate only with those they are supposed to. A network policy is a specification of how selections of pods are allowed to communicate with each other and other network endpoints.   Network Policies are namespace scoped. When a network policy is introduced to a given namespace, all traffic not allowed by the policy is denied. However, if there are no network policies in a namespace all traffic will be allowed into and out of the pods in that namespace.",
@@ -2752,7 +2752,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.4 Secrets Management",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Kubernetes supports mounting secrets as data volumes or as environment variables. Minimize the use of environment variable secrets.",
           "RationaleStatement": "It is reasonably common for application code to log out its environment (particularly in the event of an error). This will include any secret values passed in as environment variables, so secrets can easily be exposed to any user or entity who has access to the logs.",
@@ -2773,7 +2773,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.4 Secrets Management",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Consider the use of an external secrets storage and management system, instead of using Kubernetes Secrets directly, if you have more complex secret management needs. Ensure the solution requires authentication to access secrets, has auditing of access to and use of secrets, and encrypts secrets. Some solutions also make it easier to rotate secrets.",
           "RationaleStatement": "Kubernetes supports secrets as first-class objects, but care needs to be taken to ensure that access to secrets is carefully limited. Using an external secrets provider can ease the management of access to secrets, especially where secrests are used across both Kubernetes and non-Kubernetes environments.",
@@ -2794,7 +2794,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.4 Secrets Management",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Configure Image Provenance for your deployment.",
           "RationaleStatement": "Kubernetes supports plugging in provenance rules to accept or reject the images in your deployments. You could configure such rules to ensure that only approved images are deployed in the cluster.",
@@ -2838,7 +2838,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.7 General Policies",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Enable `docker/default` seccomp profile in your pod definitions.",
           "RationaleStatement": "Seccomp (secure computing mode) is used to restrict the set of system calls applications can make, allowing cluster administrators greater control over the security of workloads running in the cluster. Kubernetes disables seccomp profiles by default for historical reasons. You should enable it to ensure that the workloads have restricted actions available within the container.",
@@ -2859,7 +2859,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.7 General Policies",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Apply Security Context to Your Pods and Containers",
           "RationaleStatement": "A security context defines the operating system security settings (uid, gid, capabilities, SELinux role, etc..) applied to a container. When designing your containers and pods, make sure that you configure the security context for your pods, containers, and volumes. A security context is a property defined in the deployment yaml. It controls the security parameters that will be assigned to the pod/container/volume. There are two levels of security context: pod level security context, and container level security context.",
@@ -2880,7 +2880,7 @@
         {
           "Section": "5 Policies",
           "SubSection": "5.7 General Policies",
-          "Profile": "Level 2 - Master Node",
+          "Profile": "Level 2",
           "AssessmentStatus": "Manual",
           "Description": "Kubernetes provides a default namespace, where objects are placed if no namespace is specified for them. Placing objects in this namespace makes application of RBAC and other controls more difficult.",
           "RationaleStatement": "Resources in a Kubernetes cluster should be segregated by namespace, to allow for security controls to be applied at that level and to make it easier to manage resources.",

prowler/lib/check/compliance_models.py

@@ -3,7 +3,7 @@ import sys
 from enum import Enum
 from typing import Optional, Union
 
-from pydantic import BaseModel, ValidationError, root_validator
+from pydantic.v1 import BaseModel, ValidationError, root_validator
 
 from prowler.lib.check.utils import list_compliance_modules
 from prowler.lib.logger import logger
@@ -69,6 +69,10 @@ class CIS_Requirement_Attribute_Profile(str, Enum):
 
     Level_1 = "Level 1"
     Level_2 = "Level 2"
+    E3_Level_1 = "E3 Level 1"
+    E3_Level_2 = "E3 Level 2"
+    E5_Level_1 = "E5 Level 1"
+    E5_Level_2 = "E5 Level 2"
 
 
 class CIS_Requirement_Attribute_AssessmentStatus(str, Enum):

prowler/lib/check/models.py

@@ -7,7 +7,7 @@ from dataclasses import asdict, dataclass, is_dataclass
 from enum import Enum
 from typing import Any, Dict, Optional, Set
 
-from pydantic import BaseModel, ValidationError, validator
+from pydantic.v1 import BaseModel, ValidationError, validator
 
 from prowler.config.config import Provider
 from prowler.lib.check.compliance_models import Compliance

prowler/lib/outputs/asff/asff.py

@@ -2,7 +2,7 @@ from json import dump
 from os import SEEK_SET
 from typing import Optional
 
-from pydantic import BaseModel, validator
+from pydantic.v1 import BaseModel, validator
 
 from prowler.config.config import prowler_version, timestamp_utc
 from prowler.lib.logger import logger

prowler/lib/outputs/compliance/aws_well_architected/models.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 
 class AWSWellArchitectedModel(BaseModel):

prowler/lib/outputs/compliance/cis/models.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 
 class AWSCISModel(BaseModel):

prowler/lib/outputs/compliance/ens/models.py

@@ -1,4 +1,4 @@
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 
 class AWSENSModel(BaseModel):

prowler/lib/outputs/compliance/generic/models.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 
 class GenericComplianceModel(BaseModel):

prowler/lib/outputs/compliance/iso27001/models.py

@@ -1,4 +1,4 @@
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 
 class AWSISO27001Model(BaseModel):

prowler/lib/outputs/compliance/kisa_ismsp/models.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 
 class AWSKISAISMSPModel(BaseModel):

prowler/lib/outputs/compliance/mitre_attack/models.py

@@ -1,4 +1,4 @@
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 
 class AWSMitreAttackModel(BaseModel):

prowler/lib/outputs/compliance/prowler_threatscore/models.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 
 class ProwlerThreatScoreAWSModel(BaseModel):

prowler/lib/outputs/finding.py

@@ -3,7 +3,7 @@ from datetime import datetime
 from types import SimpleNamespace
 from typing import Optional, Union
 
-from pydantic import BaseModel, Field, ValidationError
+from pydantic.v1 import BaseModel, Field, ValidationError
 
 from prowler.config.config import prowler_version
 from prowler.lib.check.models import (

prowler/providers/aws/lib/arn/models.py

@@ -1,7 +1,7 @@
 import os
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.providers.aws.exceptions.exceptions import AWSIAMRoleARNMissingFieldsError
 

prowler/providers/aws/services/accessanalyzer/accessanalyzer_service.py

@@ -1,7 +1,7 @@
 from typing import Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/account/account_service.py

@@ -2,7 +2,7 @@ from typing import Optional
 from venv import logger
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.providers.aws.lib.service.service import AWSService
 

prowler/providers/aws/services/acm/acm_service.py

@@ -1,7 +1,7 @@
 from datetime import datetime
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/apigateway/apigateway_service.py

@@ -1,7 +1,7 @@
 from typing import Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/apigatewayv2/apigatewayv2_service.py

@@ -1,7 +1,7 @@
 from typing import Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/appstream/appstream_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/appsync/appsync_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/athena/athena_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel, Field
+from pydantic.v1 import BaseModel, Field
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/autoscaling/autoscaling_service.py

@@ -1,4 +1,4 @@
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/awslambda/awslambda_service.py

@@ -7,7 +7,7 @@ from typing import Any, Optional
 
 import requests
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/backup/backup_service.py

@@ -2,7 +2,7 @@ from datetime import datetime
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/bedrock/bedrock_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/cloudformation/cloudformation_service.py

@@ -1,7 +1,7 @@
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/cloudfront/cloudfront_service.py

@@ -1,7 +1,7 @@
 from enum import Enum
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/cloudtrail/cloudtrail_service.py

@@ -2,7 +2,7 @@ from datetime import datetime, timedelta
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/cloudwatch/cloudwatch_service.py

@@ -3,7 +3,7 @@ from datetime import datetime, timezone
 from typing import Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/codeartifact/codeartifact_service.py

@@ -2,7 +2,7 @@ from enum import Enum
 from typing import Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/codebuild/codebuild_service.py

@@ -1,7 +1,7 @@
 import datetime
 from typing import List, Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/cognito/cognito_service.py

@@ -1,7 +1,7 @@
 from datetime import datetime
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/config/config_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/datasync/datasync_service.py

@@ -1,7 +1,7 @@
 from typing import Dict, List, Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel, Field
+from pydantic.v1 import BaseModel, Field
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/directconnect/directconnect_service.py

@@ -1,7 +1,7 @@
 from typing import Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/directoryservice/directoryservice_service.py

@@ -3,7 +3,7 @@ from enum import Enum
 from typing import Optional, Union
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/dlm/dlm_service.py

@@ -1,4 +1,4 @@
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.providers.aws.lib.service.service import AWSService

prowler/providers/aws/services/dms/dms_service.py

@@ -1,7 +1,7 @@
 import json
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/documentdb/documentdb_service.py

@@ -1,7 +1,7 @@
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/drs/drs_service.py

@@ -1,5 +1,5 @@
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/dynamodb/dynamodb_service.py

@@ -2,7 +2,7 @@ import json
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/ec2/ec2_service.py

@@ -3,7 +3,7 @@ from ipaddress import IPv4Address, IPv6Address, ip_address
 from typing import Optional, Union
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/ecr/ecr_service.py

@@ -3,7 +3,7 @@ from json import loads
 from typing import Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/ecs/ecs_service.py

@@ -1,7 +1,7 @@
 from re import sub
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/efs/efs_service.py

@@ -2,7 +2,7 @@ import json
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/eks/eks_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/elasticache/elasticache_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/elasticbeanstalk/elasticbeanstalk_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/elb/elb_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/elbv2/elbv2_service.py

@@ -1,7 +1,7 @@
 from typing import Dict, Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/emr/emr_service.py

@@ -2,7 +2,7 @@ from enum import Enum
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/eventbridge/eventbridge_service.py

@@ -2,7 +2,7 @@ import json
 from typing import Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/firehose/firehose_service.py

@@ -2,7 +2,7 @@ from enum import Enum
 from typing import Dict, List, Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel, Field
+from pydantic.v1 import BaseModel, Field
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/fms/fms_service.py

@@ -1,5 +1,5 @@
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/fsx/fsx_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/glacier/glacier_service.py

@@ -2,7 +2,7 @@ import json
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/globalaccelerator/globalaccelerator_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/glue/glue_service.py

@@ -2,7 +2,7 @@ import json
 from typing import Dict, List, Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel, Field
+from pydantic.v1 import BaseModel, Field
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/guardduty/guardduty_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/iam/iam_service.py

@@ -3,7 +3,7 @@ from datetime import datetime
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.config.config import encoding_format_utf_8
 from prowler.lib.logger import logger

prowler/providers/aws/services/inspector2/inspector2_service.py

@@ -1,4 +1,4 @@
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.providers.aws.lib.service.service import AWSService

prowler/providers/aws/services/kafka/kafka_service.py

@@ -1,4 +1,4 @@
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/kinesis/kinesis_service.py

@@ -1,7 +1,7 @@
 from enum import Enum
 from typing import Dict, List, Optional
 
-from pydantic import BaseModel, Field
+from pydantic.v1 import BaseModel, Field
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/kms/kms_service.py

@@ -1,7 +1,7 @@
 import json
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/lightsail/lightsail_service.py

@@ -1,6 +1,6 @@
 from typing import Dict, List
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/macie/macie_service.py

@@ -1,4 +1,4 @@
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.providers.aws.lib.service.service import AWSService

prowler/providers/aws/services/memorydb/memorydb_service.py

@@ -1,4 +1,4 @@
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/mq/mq_service.py

@@ -1,7 +1,7 @@
 from enum import Enum
 from typing import Dict, List
 
-from pydantic import BaseModel, Field
+from pydantic.v1 import BaseModel, Field
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/neptune/neptune_service.py

@@ -1,7 +1,7 @@
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/networkfirewall/networkfirewall_service.py

@@ -1,7 +1,7 @@
 from enum import Enum
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/opensearch/opensearch_service.py

@@ -1,7 +1,7 @@
 from json import JSONDecodeError, loads
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/organizations/organizations_service.py

@@ -2,7 +2,7 @@ import json
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/rds/rds_service.py

@@ -2,7 +2,7 @@ from datetime import datetime
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/redshift/redshift_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/resourceexplorer2/resourceexplorer2_service.py

@@ -1,5 +1,5 @@
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/route53/route53_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/s3/s3_service.py

@@ -2,7 +2,7 @@ import json
 from typing import Dict, List, Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel, Field
+from pydantic.v1 import BaseModel, Field
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/sagemaker/sagemaker_service.py

@@ -1,7 +1,7 @@
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/secretsmanager/secretsmanager_service.py

@@ -2,7 +2,7 @@ import json
 from datetime import datetime, timezone
 from typing import Dict, List, Optional
 
-from pydantic import BaseModel, Field
+from pydantic.v1 import BaseModel, Field
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/securityhub/securityhub_service.py

@@ -1,7 +1,7 @@
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/servicecatalog/servicecatalog_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/ses/ses_service.py

@@ -1,7 +1,7 @@
 from json import loads
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/shield/shield_service.py

@@ -1,4 +1,4 @@
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.providers.aws.lib.service.service import AWSService

prowler/providers/aws/services/sns/sns_service.py

@@ -2,7 +2,7 @@ from json import loads
 from typing import Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/sqs/sqs_service.py

@@ -2,7 +2,7 @@ from json import loads
 from typing import Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/ssm/ssm_service.py

@@ -4,7 +4,7 @@ from enum import Enum
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/ssmincidents/ssmincidents_service.py

@@ -1,5 +1,5 @@
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/stepfunctions/stepfunctions_service.py

@@ -3,7 +3,7 @@ from enum import Enum
 from typing import Dict, List, Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel, Field
+from pydantic.v1 import BaseModel, Field
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/storagegateway/storagegateway_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/transfer/transfer_service.py

@@ -1,7 +1,7 @@
 from enum import Enum
 from typing import Dict, List
 
-from pydantic import BaseModel, Field
+from pydantic.v1 import BaseModel, Field
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/trustedadvisor/trustedadvisor_service.py

@@ -1,7 +1,7 @@
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.providers.aws.lib.service.service import AWSService

prowler/providers/aws/services/vpc/vpc_service.py

@@ -2,7 +2,7 @@ import json
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/waf/waf_service.py

@@ -1,6 +1,6 @@
 from typing import Dict, List, Optional
 
-from pydantic import BaseModel, Field
+from pydantic.v1 import BaseModel, Field
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/wafv2/wafv2_service.py

@@ -2,7 +2,7 @@ from enum import Enum
 from typing import Optional
 
 from botocore.exceptions import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/wellarchitected/wellarchitected_service.py

@@ -1,7 +1,7 @@
 from typing import Optional
 
 from botocore.client import ClientError
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/aws/services/workspaces/workspaces_service.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.lib.logger import logger
 from prowler.lib.scan_filters.scan_filters import is_resource_filtered

prowler/providers/azure/models.py

@@ -1,6 +1,6 @@
 from typing import Optional
 
-from pydantic import BaseModel
+from pydantic.v1 import BaseModel
 
 from prowler.config.config import output_file_timestamp
 from prowler.providers.common.models import ProviderOutputOptions