feat: add statement regarding secrets

Author: xdxxxdx

README.md

@@ -149,3 +149,5 @@ GitHub may be utilized for version control; however, code should be treated as a
 In accordance with the [deployEMDS Information Security Policy](https://acatechev.sharepoint.de/:b:/r/sites/EuropeanMobilityDataSpaceDeploymentConsortiumspace/Freigegebene%20Dokumente/General/07_Security%20Policy/2024-02-16%20Information%20security%20policy_DeployEMDS_V1.5_CLEAN.pdf?csf=1&web=1&e=SwIPb1), section 7.1 "Information asset protection responsibility," we are required to evaluate all information assets used or created during the project. This evaluation should adhere to the checklist provided in the risk assessment template (Annex 1, pp. 15) . The Security Advisory Board (SAB) and Project Security Officer (PSO) should only be consulted if information security concerns arise, such as when any question on the checklist is answered affirmatively.
 
 This process ensures compliance with our security protocols and safeguards the intellectual property and sensitive information.
+
+Please note: secret keys have been redacted in this repository and must be replaced with user-provided keys to ensure functionality.

tests/README.md

@@ -19,3 +19,5 @@ Definitions and deliverables and are organized in a tree that reflects the proje
 ```
 
 The structure will be used to implement comparative reviews to align the results of testing facilities. For this reason, it is advisable to follow the publication guidelines, although improvements are always welcome, and they can be requested via issues.
+
+Please notice: any secret keys have been intentionally redacted and will need to be replaced by user-provided keys to ensure functionality

web/docs/tech-testing/way-of-working.mdx

@@ -76,4 +76,5 @@ The following testing facilities are currently proposed:
 | ~~Fiware+iShare~~ | ~~i4Trust~~                                         | ~~TBD~~                                                    | ~~Gernot (Fiware)~~                    | ~~imec~~       | ~~Cefriel~~                   | ~~Deprecated, will not test~~                                                                                                                     |
 | ~~EDC+XFSC~~      | ~~EDC v0.7 with some XFSC components~~              | ~~Catalog, identity provider, wallet from XFSC (Eclipse)~~ | ~~Christoph Lange-Bever (Fraunhofer)~~ | ~~TBD~~        | ~~TBD~~                       | ~~Info session completed, difficult deployment and lower maturity~~                                                                               |
 * **Technical buddies** are either commercial providers or experienced partners who help deploying the stacks.
-* The **Test squads** are deployEMDS WP2 workgroup _"Building blocks"_ partners that are responsible for phase 0 and phase 1.
+* The **Test squads** are deployEMDS WP2 workgroup _"Building blocks"_ partners that are responsible for phase 0 and phase 1.
+* Please notice: any secret keys have been intentionally redacted and will need to be replaced by user-provided keys to ensure functionality.