base on CISO Assistant is a one-stop-shop for GRC, covering Risk, AppSec, Compliance/Audit Management, Privacy and supporting +80 frameworks worldwide with auto-mapping: NIST CSF, ISO 27001, SOC2, CIS, PCI DSS, NIS2, CMMC, PSPF, GDPR, HIPAA, Essential Eight, NYDFS-500, DORA, NIST AI RMF, 800-53, CyFun, AirCyber, NCSC, ECC, SCF and so much mor <p align="center"> Star the project 🌟 to get releases notification and help growing the community! </p> <p align="center"> <a href="https://trendshift.io/repositories/9343" target="_blank"><img src="https://trendshift.io/api/badge/repositories/9343" alt="intuitem%2Fciso-assistant-community | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a> <br /> <a href="https://intuitem.com">intuitem.com</a> · <a href="https://intuitem.com/trial">SaaS Free trial</a> · <a href="https://roadmap.productboard.com/c483ebdf-87df-4dc2-96dc-a2e8c66aac63">Roadmap</a> · <a href="https://intuitem.gitbook.io/ciso-assistant" target="_blank">Docs</a> · <a href="#supported-languages-">Languages</a> · <a href="https://discord.gg/qvkaMdQ8da">Discord</a> · <a href="#supported-frameworks-">Frameworks</a> <br /> </p>  [](https://www.codefactor.io/repository/github/intuitem/ciso-assistant-community) [](https://github.com/intuitem/ciso-assistant-community/actions/workflows/backend-api-tests.yml) [](https://github.com/intuitem/ciso-assistant-community/actions/workflows/functional-tests.yml)  [](https://app.fossa.com/projects/git%2Bgithub.com%2Fab-smith%2Fciso-assistant-community?ref=badge_small) CISO Assistant offers a fresh perspective on Cybersecurity Management and **GRC** (Governance, Risk, and Compliance) practices: - Designed as a central hub to connect multiple cybersecurity concepts with smart linking between objects, - Built as a **multi-paradigm** tool that adapts to different backgrounds, methodologies, and expectations, - Explicitly **decouples** compliance from cybersecurity controls, enabling reusability across the platform, - Promotes **reusability** and interlinking instead of redundant work, - Developed with an **API-first** approach to support both UI interaction and external **automation**, - Comes packed with a wide range of built-in standards, security controls, and threat libraries, - Offers an **open format** to customize and reuse your own objects and frameworks, - Includes built-in **risk assessment** and **remediation tracking** workflows, - Supports custom frameworks via a simple syntax and flexible tooling, - Provides rich **import/export** capabilities across various channels and formats (UI, CLI, Kafka, reports, etc.). Our vision is to create a **one-stop-shop** for cybersecurity management—modernizing GRC through **simplification** and **interoperability**. As practitioners working with cybersecurity and IT professionals, we've faced the same issues: tool fragmentation, data duplication, and a lack of intuitive, integrated solutions. CISO Assistant was born from those lessons, and we're building a community around **pragmatic**, **common-sense** principles. We’re constantly evolving with input from users and customers. Like an octopus 🐙, CISO Assistant keeps growing extra arms—bringing clarity, automation, and productivity to cybersecurity teams while reducing the effort of data input and output. --- ## Core Concepts Here’s a snapshot of the fundamental building blocks in CISO Assistant:  For full details, check the [data model documentation](documentation/architecture/data-model.md). --- ## Features Explore the full range of features and capabilities:  CISO Assistant is developed and maintained by [Intuitem](https://intuitem.com/), a company specialized in Cybersecurity, Cloud, and Data/AI. --- ## Decoupling Concept At the heart of CISO Assistant lies the **decoupling principle**, which enables powerful use cases and major time savings: - Reuse past assessments across scopes or frameworks, - Evaluate a single scope against multiple frameworks simultaneously, - Let CISO Assistant handle reporting and consistency checks so you can focus on remediation, - Separate control implementation from compliance tracking. Here is an illustration of the **decoupling** principle and its advantages: <https://github.com/user-attachments/assets/87bd4497-5cc2-4221-aeff-396f6b6ebe62> ## System architecture  ## Quick Start 🚀 > [!TIP] > The easiest way to get started is through the [free trial of cloud instance available here](https://intuitem.com/trial). Alternatively, once you have _Docker_ and _Docker-compose_ installed, on your workstation or server: clone the repo: ``` git clone --single-branch -b main https://github.com/intuitem/ciso-assistant-community.git ``` and run the starter script ```sh ./docker-compose.sh ``` If you are looking for other installation options for self-hosting, check the [config builder](./config/) and the [docs](https://intuitem.gitbook.io/ciso-assistant). > [!NOTE] > The docker-compose script uses prebuilt Docker images supporting most of the standard hardware architecture. > If you're using **Windows**, Make sure to have [WSL](https://learn.microsoft.com/en-us/windows/wsl/install) installed and trigger the script within a WSL command line. It will feed Docker Desktop on your behalf. The docker compose file can be adjusted to pass extra parameters to suit your setup (e.g. Mailer settings). > [!WARNING] > If you're getting warnings or errors about image's platform not matching host platform, raise an issue with the details and we'll add it shortly after. You can also use `docker-compose-build.sh` instead (see below) to build for your specific architecture. > [!CAUTION] > Don't use the `main` branch code directly for production as it's the merge upstream and can have breaking changes during our development. Either use the `tags` for stable versions or prebuilt images. ## End-user Documentation Check out the online documentation on <https://intuitem.gitbook.io/ciso-assistant>. ## Supported frameworks 🐙 1. ISO 27001:2022 🌐 2. NIST Cyber Security Framework (CSF) v1.1 🇺🇸 3. NIST Cyber Security Framework (CSF) v2.0 🇺🇸 4. NIS2 🇪🇺 5. SOC2 🇺🇸 6. PCI DSS 4.0 💳 7. CMMC v2 🇺🇸 8. PSPF 🇦🇺 9. General Data Protection Regulation (GDPR): Full text and checklist from GDPR.EU 🇪🇺 10. Essential Eight 🇦🇺 11. NYDFS 500 with 2023-11 amendments 🇺🇸 12. DORA (Act, RTS, ITS and GL) 🇪🇺 13. NIST AI Risk Management Framework 🇺🇸🤖 14. NIST SP 800-53 rev5 🇺🇸 15. France LPM/OIV rules 🇫🇷 16. CCB CyberFundamentals Framework 🇧🇪 17. NIST SP-800-66 (HIPAA) 🏥 18. HDS/HDH 🇫🇷 19. OWASP Application Security Verification Standard (ASVS) 🐝🖥️ 20. RGS v2.0 🇫🇷 21. AirCyber ✈️🌐 22. Cyber Resilience Act (CRA) 🇪🇺 23. TIBER-EU 🇪🇺 24. NIST Privacy Framework 🇺🇸 25. TISAX (VDA ISA) v5.1 and v6.0 🚘 26. ANSSI hygiene guide 🇫🇷 27. Essential Cybersecurity Controls (ECC) 🇸🇦 28. CIS Controls v8\* 🌐 29. CSA CCM (Cloud Controls Matrix)\* ☁️ 30. FADP (Federal Act on Data Protection) 🇨🇭 31. NIST SP 800-171 rev2 (2021) 🇺🇸 32. ANSSI : recommandations de sécurité pour un système d'IA générative 🇫🇷🤖 33. NIST SP 800-218: Secure Software Development Framework (SSDF) 🖥️ 34. GSA FedRAMP rev5 ☁️🇺🇸 35. Cadre Conformité Cyber France (3CF) v1 (2021) ✈️🇫🇷 36. ANSSI : SecNumCloud ☁️🇫🇷 37. Cadre Conformité Cyber France (3CF) v2 (2024) ✈️🇫🇷 38. ANSSI : outil d’autoévaluation de gestion de crise cyber 💥🇫🇷 39. BSI: IT-Grundschutz-Kompendium 🇩🇪 40. NIST SP 800-171 rev3 (2024) 🇺🇸 41. ENISA: 5G Security Controls Matrix 🇪🇺 42. OWASP Mobile Application Security Verification Standard (MASVS) 🐝📱 43. Agile Security Framework (ASF) - baseline - by intuitem 🤗 44. ISO 27001:2013 🌐 (For legacy and migration) 45. EU AI Act 🇪🇺🤖 46. FBI CJIS 🇺🇸👮 47. Operational Technology Cybersecurity Controls (OTCC) 🇸🇦 48. Secure Controls Framework (SCF) 🇺🇸🌐 49. NCSC Cyber Assessment Framework (CAF) 🇬🇧 50. California Consumer Privacy Act (CCPA) 🇺🇸 51. California Consumer Privacy Act Regulations 🇺🇸 52. NCSC Cyber Essentials 🇬🇧 53. Directive Nationale de la Sécurité des Systèmes d'Information (DNSSI) Maroc 🇲🇦 54. Part-IS ✈️🇪🇺 55. ENS Esquema Nacional de seguridad 🇪🇸 56. Korea ISA ISMS-P 🇰🇷 57. Swiss ICT minimum standard 🇨🇭 58. Adobe Common Controls Framework (CCF) 🌐 59. BSI Cloud Computing Compliance Criteria Catalogue (C5) 🇩🇪 60. Référentiel d’Audit de la Sécurité des Systèmes d’Information, ANCS Tunisie 🇹🇳 61. ECB Cyber resilience oversight expectations for financial market infrastructures 🇪🇺 62. Mindeststandard-des-BSI-zur-Nutzung-externer-Cloud-Dienste (Version 2.1) 🇩🇪 63. Formulaire d'évaluation de la maturité - niveau fondamental (DGA) 🇫🇷 64. NIS2 technical and methodological requirements 2024/2690 🇪🇺 65. Saudi Arabian Monetary Authority (SAMA) Cybersecurity Framework 🇸🇦 66. Guide de sécurité des données (CNIL) 🇫🇷 67. International Traffic in Arms Regulations (ITAR) 🇺🇸 68. Federal Trade Commission (FTC) Standards for Safeguarding Customer Information 🇺🇸 69. OWASP's checklist for LLM governance and security 🌐 70. Recommandations pour les architectures des systèmes d’information sensibles ou à diffusion restreinte (ANSSI) 🇫🇷 71. CIS benchmark for Kubernetes v1.10 🌐 72. De tekniske minimumskrav for statslige myndigheder 🇩🇰 73. Google SAIF framework 🤖 74. Recommandations relatives à l'administration sécurisée des SI (ANSSI) 🇫🇷 75. Prudential Standard CPS 230 - Operational Risk Management (APRA) 🇦🇺 76. Prudential Standard CPS 234 - Information Security (APRA) 🇦🇺 ### Community contributions 1. PGSSI-S (Politique Générale de Sécurité des Systèmes d'Information de Santé) 🇫🇷 2. ANSSI : Recommandations de configuration d'un système GNU/Linux 🇫🇷 3. PSSI-MCAS (Politique de sécurité des systèmes d’information pour les ministères chargés des affaires sociales) 🇫🇷 4. ANSSI : Recommandations pour la protection des systèmes d'information essentiels 🇫🇷 5. ANSSI : Recommandations de sécurité pour l'architecture d'un système de journalisation 🇫🇷 6. ANSSI : Recommandations de sécurité relatives à TLS 🇫🇷 7. New Zealand Information Security Manual (NZISM) 🇳🇿 8. Clausier de sécurité numérique du Club RSSI Santé 🇫🇷 9. Référentiel National de Sécurité de l’Information (RNSI), MPT Algérie 🇩🇿 10. Misure minime di sicurezza ICT per le pubbliche amministrazioni, AGID Italia 🇮🇹 11. Framework Nazionale CyberSecurity v2, FNCS Italia 🇮🇹 12. Framework Nazionale per la Cybersecurity e la Data Protection, ACN Italia 🇮🇹 13. PSSIE du Bénin, ANSSI Bénin 🇧🇯 <br/> > [!NOTE] > Frameworks with `*` require an extra manual step of getting the latest Excel sheet through their website as their license prevent direct usage. <br/> Checkout the [library](/backend/library/libraries/) and [tools](/tools/) for the Domain Specific Language used and how you can define your own. ### Coming soon - Indonesia PDP 🇮🇩 - VCS framework from ENX - OWASP SAMM - COBAC R-2024/01 - ICO Data protection self-assessment 🇬🇧 - NIST 800-82 - ASD ISM 🇦🇺 - Baseline informatiebeveiliging Overheid (BIO) 🇳🇱 - and much more: just ask on [Discord](https://discord.gg/qvkaMdQ8da). If it's an open standard, we'll do it for you, _free of charge_ 😉 ## Add your own library A library can be a framework, a catalog of threats or reference controls, and even a custom risk matrix. Take a look at the `tools` directory and its [dedicated README](tools/README.md). The `convert_library.py` script will help you create your library from a simple Excel file. Once you have structured your items in that format, just run the script and use the resulting yaml file. You can also find some specific converters in the tools directory (e.g. for CIS or CCM Controls). There is also a tool to facilitate the creation of mappings, called `prepare_mapping.py` that will create an Excel file based on two framework libraries in yaml. Once properly filled, this Excel file can be processed by the `convert_library.py` tool to get the resulting mapping library. ## Community Join our [open Discord community](https://discord.gg/qvkaMdQ8da) to interact with the team and other GRC experts. ## Testing the cloud version > The fastest and easiest way to get started is through the [free trial of cloud instance available here](https://intuitem.com/trial). ## Testing locally 🚀 To run CISO Assistant locally in a straightforward way, you can use Docker compose. 0. Update docker Make sure you have a recent version of docker (>= 27.0). 1. Clone the repository ```sh git clone --single-branch -b main https://github.com/intuitem/ciso-assistant-community.git cd ciso-assistant-community ``` 2. Launch docker-compose script for prebuilt images: ```sh ./docker-compose.sh ``` _Alternatively_, you can use this variant to build the docker images for your specific architecture: ```sh ./docker-compose-build.sh ``` When asked for, enter your email and password for your superuser. You can then reach CISO Assistant using your web browser at [https://localhost:8443/](https://localhost:8443/) For the following executions, use "docker compose up" directly. ## Setting up CISO Assistant for development ### Requirements - Python 3.12+ - pip 20.3+ - poetry 2.0+ - node 22+ - npm 10.2+ - pnpm 9.0+ - yaml-cpp (brew install yaml-cpp libyaml or apt install libyaml-cpp-dev) ### Running the backend 1. Clone the repository. ```sh git clone [email protected]:intuitem/ciso-assistant-community.git cd ciso-assistant-community ``` 2. Create a file in the parent folder (e.g. ../myvars) and store your environment variables within it by copying and modifying the following code and replace `"<XXX>"` by your private values. Take care not to commit this file in your git repo. **Mandatory variables** All variables in the backend have handy default values. **Recommended variables** ```sh export DJANGO_DEBUG=True # Default url is set to http://localhost:5173 but you can change it, e.g. to use https with a caddy proxy export CISO_ASSISTANT_URL=https://localhost:8443 # Setup a development mailer with Mailhog for example export EMAIL_HOST_USER='' export EMAIL_HOST_PASSWORD='' export [email protected] export EMAIL_HOST=localhost export EMAIL_PORT=1025 export EMAIL_USE_TLS=True ``` **Other variables** ```sh # CISO Assistant will use SQLite by default, but you can setup PostgreSQL by declaring these variables export POSTGRES_NAME=ciso-assistant export POSTGRES_USER=ciso-assistantuser export POSTGRES_PASSWORD=<XXX> export POSTGRES_PASSWORD_FILE=<XXX> # alternative way to specify password export DB_HOST=localhost export DB_PORT=5432 # optional, default value is 5432 # CISO Assistant will use filesystem storage backend bu default. # You can use a S3 Bucket by declaring these variables # The S3 bucket must be created before starting CISO Assistant export USE_S3=True export AWS_ACCESS_KEY_ID=<XXX> export AWS_SECRET_ACCESS_KEY=<XXX> export AWS_STORAGE_BUCKET_NAME=<your-bucket-name> export AWS_S3_ENDPOINT_URL=<your-bucket-endpoint> # Add a second backup mailer (will be deprecated, not recommended anymore) export EMAIL_HOST_RESCUE=<XXX> export EMAIL_PORT_RESCUE=587 export EMAIL_HOST_USER_RESCUE=<XXX> export EMAIL_HOST_PASSWORD_RESCUE=<XXX> export EMAIL_USE_TLS_RESCUE=True # You can define the email of the first superuser, useful for automation. A mail is sent to the superuser for password initialization export CISO_SUPERUSER_EMAIL=<XXX> # By default, Django secret key is generated randomly at each start of CISO Assistant. This is convenient for quick test, # but not recommended for production, as it can break the sessions (see # this [topic](https://stackoverflow.com/questions/15170637/effects-of-changing-djangos-secret-key) for more information). # To set a fixed secret key, use the environment variable DJANGO_SECRET_KEY. export DJANGO_SECRET_KEY=... # Logging configuration export LOG_LEVEL=INFO # optional, default value is INFO. Available options: DEBUG, INFO, WARNING, ERROR, CRITICAL export LOG_FORMAT=plain # optional, default value is plain. Available options: json, plain # Authentication options export AUTH_TOKEN_TTL=3600 # optional, default value is 3600 seconds (60 minutes). It defines the time to live of the authentication token export AUTH_TOKEN_AUTO_REFRESH=True # optional, default value is True. It defines if the token TTL should be refreshed automatically after each request authenticated with the token export AUTH_TOKEN_AUTO_REFRESH_TTL=36000 # optional, default value is 36000 seconds (10 hours). It defines the time to live of the authentication token after auto refresh. You can disable it by setting it to 0. ``` 3. Install poetry Visit the poetry website for instructions: <https://python-poetry.org/docs/#installation> 4. Install required dependencies. ```sh poetry install ``` 5. Recommended: Install the pre-commit hooks. ```sh pre-commit install ``` 6. If you want to setup Postgres: - Launch one of these commands to enter in Postgres: - `psql as superadmin` - `sudo su postgres` - `psql` - Create the database "ciso-assistant" - `create database ciso-assistant;` - Create user "ciso-assistantuser" and grant it access - `create user ciso-assistantuser with password '<POSTGRES_PASSWORD>';` - `grant all privileges on database ciso-assistant to ciso-assistantuser;` 7. If you want to setup s3 bucket: - Choose your s3 provider or try s3 feature with miniO with this command: - `docker run -p 9000:9000 -p 9001:9001 -e "MINIO_ROOT_USER=XXX" -e "MINIO_ROOT_PASSWORD=XXX" quay.io/minio/minio server /data --console-address ":9001"` - You can now check your bucket on http://localhost:9001 - Fill the login with the credentials you filled on the docker run env variables - Export in the backend directory all the env variables asked about S3 - You can see the list above in the recommanded variables 8. Apply migrations. ```sh poetry run python manage.py migrate ``` 9. Create a Django superuser, that will be CISO Assistant administrator. > If you have set a mailer and CISO_SUPERUSER_EMAIL variable, there's no need to create a Django superuser with `createsuperuser`, as it will be created automatically on first start. You should receive an email with a link to setup your password. ```sh poetry run python manage.py createsuperuser ``` 10. Run development server. ```sh poetry run python manage.py runserver ``` 11. for Huey (tasks runner) - prepare a mailer for testing. - run `python manage.py run_huey -w 2 -k process` or equivalent in a separate shell. - you can use `MAIL_DEBUG` to have mail on the console for easier debug ### Running the frontend 1. cd into the frontend directory ```shell cd frontend ``` 2. Install dependencies ```bash npm install -g pnpm pnpm install ``` 3. Start a development server (make sure that the django app is running) ```bash pnpm run dev ``` 4. Reach the frontend on <http://localhost:5173> > [!NOTE] > Safari will not properly work in this setup, as it requires https for secure cookies. The simplest solution is to use Chrome or Firefox. An alternative is to use a caddy proxy. Please see the [readme file](frontend/README.md) in frontend directory for more information on this. 5. Environment variables All variables in the frontend have handy default values. If you move the frontend on another host, you should set the following variable: PUBLIC_BACKEND_API_URL. Its default value is <http://localhost:8000/api>. The PUBLIC_BACKEND_API_EXPOSED_URL is necessary for proper functioning of the SSO. It points to the URL of the API as seen from the browser. It should be equal to the concatenation of CISO_ASSISTANT_URL (in the backend) with "/api". When you launch "node server" instead of "pnpm run dev", you need to set the ORIGIN variable to the same value as CISO_ASSISTANT_URL in the backend (e.g. <http://localhost:3000>). ### Managing migrations The migrations are tracked by version control, <https://docs.djangoproject.com/en/4.2/topics/migrations/#version-control> For the first version of the product, it is recommended to start from a clean migration. Note: to clean existing migrations, type: ```sh find . -path "*/migrations/*.py" -not -name "__init__.py" -delete find . -path "*/migrations/*.pyc" -delete ``` After a change (or a clean), it is necessary to re-generate migration files: ```sh poetry run python manage.py makemigrations poetry run python manage.py migrate ``` These migration files should be tracked by version control. ### Test suite To run API tests on the backend, simply type "poetry run pytest" in a shell in the backend folder. To run functional tests on the frontend, do the following actions: - in the frontend folder, launch the following command: ```shell tests/e2e-tests.sh ``` The goal of the test harness is to prevent any regression, i.e. all the tests shall be successful, both for backend and frontend. ## API and Swagger - The API is available only on dev mode. To get that, you need to switch on the backend, for instance, `export DJANGO_DEBUG=True` - The API documentation will be available on `<backend_endpoint>/api/schema/swagger/`, for instance <http://127.0.0.1:8000/api/schema/swagger/> To interact with it: - call `/api/iam/login/` with your credentials in the body to get the token - pass it then as a header `Authorization: Token {token}` for your next calls. Notice it's `Token` not `Bearer`. ## Setting CISO Assistant for production The docker-compose-prod.yml highlights a relevant configuration with a Caddy proxy in front of the frontend. It exposes API calls only for SSO. Note that docker-compose.yml exposes the full API, which is not yet recommended for production. Set DJANGO_DEBUG=False for security reason. > [!NOTE] > The frontend cannot infer the host automatically, so you need to either set the ORIGIN variable, or the HOST_HEADER and PROTOCOL_HEADER variables. Please see [the sveltekit doc](https://kit.svelte.dev/docs/adapter-node#environment-variables-origin-protocolheader-hostheader-and-port-header) on this tricky issue. Beware that this approach does not work with "pnpm run dev", which should not be a worry for production. > [!NOTE] > Caddy needs to receive a SNI header. Therefore, for your public URL (the one declared in CISO_ASSISTANT_URL), you need to use a FQDN, not an IP address, as the SNI is not transmitted by a browser if the host is an IP address. Another tricky issue! ## Supported languages 🌐 - FR: French - EN: English - AR: Arabic - PT: Portuguese - ES: Spanish - DE: German - NL: Dutch - IT: Italian - PL: Polish - RO: Romanian - HI: Hindi - UR: Urdu - CS: Czech - SV: Swedish - ID: Indonesian - DA: Danish - HU: Hungarian ## Contributors 🤝 <a href="https://github.com/intuitem/ciso-assistant-community/graphs/contributors"> <img src="https://contrib.rocks/image?repo=intuitem/ciso-assistant-community&columns=9" /> </a> ## Built With 💜 - [Django](https://www.djangoproject.com/) - Python Web Development Framework - [SvelteKit](https://kit.svelte.dev/) - Frontend Framework - [eCharts](https://echarts.apache.org) - Charting library - [unovis](https://unovis.dev) - Complementary charting library - [Gunicorn](https://gunicorn.org/) - Python WSGI HTTP Server for UNIX - [Caddy](https://caddyserver.com) - The coolest reverse Proxy - [Gitbook](https://www.gitbook.com) - Documentation platform - [PostgreSQL](https://www.postgresql.org/) - Open Source RDBMS - [SQLite](https://www.sqlite.org/index.html) - Open Source RDBMS - [Docker](https://www.docker.com/) - Container Engine - [inlang](https://inlang.com/) - The ecosystem to globalize your software - [Huey](https://huey.readthedocs.io/en/latest/) - A lightweight task queue ## Security Great care has been taken to follow security best practices. Please report any issue to <[email protected]>. ## License This repository contains the source code for both the Open Source edition of CISO Assistant (Community Edition), released under the AGPL v3, as well as the commercial edition of CISO Assistant (Pro and Enterprise Editions), released under the intuitem Commercial Software License. This mono-repository approach is adopted for simplicity. All the files within the top-level "enterprise" directory are released under the intuitem Commercial Software License. All the files outside the top-level "enterprise" directory are released under the [AGPLv3](https://choosealicense.com/licenses/agpl-3.0/). See [LICENSE.md](./LICENSE.md) for details. For more details about the commercial editions, you can reach us on <[email protected]>. Unless otherwise noted, all files are © intuitem. ## Activity  ", Assign "at most 3 tags" to the expected json: {"id":"9343","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"