{"id":1243,"date":"2026-01-24T10:34:15","date_gmt":"2026-01-24T09:34:15","guid":{"rendered":"https:\/\/regulated-devsecops.com\/uncategorized\/nis2-security-architecture-explained-2\/"},"modified":"2026-03-26T00:39:55","modified_gmt":"2026-03-25T23:39:55","slug":"nis2-security-architecture-explained","status":"publish","type":"post","link":"https:\/\/regulated-devsecops.com\/fr\/regulatory-frameworks\/nis2-security-architecture-explained\/","title":{"rendered":"Architecture de s\u00e9curit\u00e9 NIS2 \u2014 Expliqu\u00e9e"},"content":{"rendered":"\n<p>La directive NIS2 renforce consid\u00e9rablement les exigences en mati\u00e8re de cybers\u00e9curit\u00e9 et de gestion des risques pour les entit\u00e9s essentielles et importantes \u00e0 travers l&rsquo;Union europ\u00e9enne. Contrairement aux approches purement politiques, NIS2 met fortement l&rsquo;accent sur <strong>les contr\u00f4les techniques, la pr\u00e9paration op\u00e9rationnelle et les mesures de s\u00e9curit\u00e9 d\u00e9montrables<\/strong>.<\/p>\n\n\n\n<p>Cette page explique une <strong>architecture de s\u00e9curit\u00e9 NIS2 de r\u00e9f\u00e9rence<\/strong>, montrant comment la gouvernance, les pipelines CI\/CD et les syst\u00e8mes op\u00e9rationnels fonctionnent ensemble pour r\u00e9pondre aux obligations NIS2 en pratique.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>NIS2 Security Architecture (Overview)<\/strong><\/h2>\n\n\n\n<!-- GeneratePress Inline SVG \u2013 Regulated DevSecOps -->\n<figure class=\"gp-rds-diagram\">\n   <svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\"\n     viewBox=\"0 0 1200 420\"\n     role=\"img\"\n     aria-labelledby=\"title desc\"\n     data-theme=\"light\">\n\n  <title id=\"title\">NIS2 Security Architecture<\/title>\n  <desc id=\"desc\">\n    Reference architecture illustrating governance, secure CI\/CD,\n    operations, incident management and supply chain security under NIS2.\n  <\/desc>\n\n  <style>\n    :root{\n      --bg:transparent;\n      --text:#0f172a;\n      --muted:#475569;\n      --stroke:#cbd5e1;\n      --card:#ffffff;\n      --accent:#2563eb;\n      --accentSoft:#dbeafe;\n    }\n\n    .txt{font-family:ui-sans-serif,system-ui,-apple-system,Segoe UI,Roboto,Arial;}\n    .title{font-weight:700;font-size:22px;fill:var(--text);}\n    .sub{font-size:14px;fill:var(--muted);}\n    .label{font-weight:600;font-size:14px;fill:var(--text);}\n    .small{font-size:12px;fill:var(--muted);}\n\n    .card{fill:var(--card);stroke:var(--stroke);stroke-width:1.5;rx:14;}\n    .chip{fill:transparent;stroke:var(--stroke);stroke-width:1.5;rx:6;}\n    .chipText{font-weight:600;font-size:12px;fill:var(--text);}\n\n    .flow{fill:none;stroke:var(--stroke);stroke-width:2.5;stroke-linecap:round;}\n    .arrow{marker-end:url(#arrow);}\n\n    .band{fill:transparent;stroke:var(--stroke);stroke-width:1.5;rx:18;stroke-dasharray:6 6;}\n    .bandText{font-weight:700;font-size:12px;fill:var(--muted);letter-spacing:.04em;}\n\n    .hl .card{stroke:var(--accent);}\n    .hl .chip{stroke:var(--accent);fill:var(--accentSoft);}\n  <\/style>\n\n  <defs>\n    <marker id=\"arrow\" viewBox=\"0 0 10 10\" refX=\"9\" refY=\"5\"\n            markerWidth=\"7\" markerHeight=\"7\" orient=\"auto\">\n      <path d=\"M0 0 L10 5 L0 10 Z\" fill=\"var(--stroke)\"\/>\n    <\/marker>\n  <\/defs>\n\n  <!-- Header -->\n  <text class=\"txt title\" x=\"40\" y=\"44\">NIS2 Security Architecture<\/text>\n  <text class=\"txt sub\" x=\"40\" y=\"70\">\n    Governance \u2022 Secure CI\/CD \u2022 Operations \u2022 Incident Management\n  <\/text>\n\n  <!-- Cross-cutting evidence -->\n  <rect class=\"band\" x=\"40\" y=\"320\" width=\"1120\" height=\"70\"\/>\n  <text class=\"txt bandText\" x=\"60\" y=\"345\">CONTINUOUS SECURITY EVIDENCE<\/text>\n\n  <g transform=\"translate(60,356)\">\n    <rect class=\"chip\" width=\"170\" height=\"28\"\/>\n    <text class=\"txt chipText\" x=\"85\" y=\"19\" text-anchor=\"middle\">Security logs<\/text>\n  <\/g>\n  <g transform=\"translate(250,356)\">\n    <rect class=\"chip\" width=\"190\" height=\"28\"\/>\n    <text class=\"txt chipText\" x=\"95\" y=\"19\" text-anchor=\"middle\">Risk &amp; control records<\/text>\n  <\/g>\n  <g transform=\"translate(460,356)\">\n    <rect class=\"chip\" width=\"210\" height=\"28\"\/>\n    <text class=\"txt chipText\" x=\"105\" y=\"19\" text-anchor=\"middle\">Supply chain evidence<\/text>\n  <\/g>\n  <g transform=\"translate(690,356)\">\n    <rect class=\"chip\" width=\"200\" height=\"28\"\/>\n    <text class=\"txt chipText\" x=\"100\" y=\"19\" text-anchor=\"middle\">Monitoring &amp; alerts<\/text>\n  <\/g>\n  <g transform=\"translate(910,356)\">\n    <rect class=\"chip\" width=\"250\" height=\"28\"\/>\n    <text class=\"txt chipText\" x=\"125\" y=\"19\" text-anchor=\"middle\">Incident &amp; response records<\/text>\n  <\/g>\n\n  <!-- Governance -->\n  <g transform=\"translate(40,110)\">\n    <rect class=\"card\" width=\"260\" height=\"180\"\/>\n    <text class=\"txt label\" x=\"18\" y=\"34\">Governance &amp; Risk Management<\/text>\n    <text class=\"txt small\" x=\"18\" y=\"58\">NIS2 organisational measures<\/text>\n\n    <g transform=\"translate(18,82)\">\n      <rect class=\"chip\" width=\"224\" height=\"28\"\/>\n      <text class=\"txt chipText\" x=\"112\" y=\"19\" text-anchor=\"middle\">\n        Cyber risk assessment\n      <\/text>\n    <\/g>\n    <g transform=\"translate(18,114)\">\n      <rect class=\"chip\" width=\"224\" height=\"28\"\/>\n      <text class=\"txt chipText\" x=\"112\" y=\"19\" text-anchor=\"middle\">\n        Policies &amp; accountability\n      <\/text>\n    <\/g>\n  <\/g>\n\n  <!-- Secure CI\/CD -->\n  <g class=\"hl\" transform=\"translate(330,110)\">\n    <rect class=\"card\" width=\"330\" height=\"180\"\/>\n    <text class=\"txt label\" x=\"18\" y=\"34\">Secure Development &amp; CI\/CD<\/text>\n    <text class=\"txt small\" x=\"18\" y=\"58\">Supply chain &amp; change control<\/text>\n\n    <g transform=\"translate(18,82)\">\n      <rect class=\"chip\" width=\"294\" height=\"28\"\/>\n      <text class=\"txt chipText\" x=\"147\" y=\"19\" text-anchor=\"middle\">\n        Secure SDLC &amp; access control\n      <\/text>\n    <\/g>\n    <g transform=\"translate(18,114)\">\n      <rect class=\"chip\" width=\"294\" height=\"28\"\/>\n      <text class=\"txt chipText\" x=\"147\" y=\"19\" text-anchor=\"middle\">\n        Security testing &amp; dependency checks\n      <\/text>\n    <\/g>\n    <g transform=\"translate(18,146)\">\n      <rect class=\"chip\" width=\"294\" height=\"28\"\/>\n      <text class=\"txt chipText\" x=\"147\" y=\"19\" text-anchor=\"middle\">\n        Supply chain integrity &amp; provenance\n      <\/text>\n    <\/g>\n  <\/g>\n\n  <!-- Operations -->\n  <g transform=\"translate(700,110)\">\n    <rect class=\"card\" width=\"260\" height=\"180\"\/>\n    <text class=\"txt label\" x=\"18\" y=\"34\">Operations &amp; Incident Management<\/text>\n    <text class=\"txt small\" x=\"18\" y=\"58\">Detection \u2022 response \u2022 resilience<\/text>\n\n    <g transform=\"translate(18,82)\">\n      <rect class=\"chip\" width=\"224\" height=\"28\"\/>\n      <text class=\"txt chipText\" x=\"112\" y=\"19\" text-anchor=\"middle\">\n        Continuous monitoring\n      <\/text>\n    <\/g>\n    <g transform=\"translate(18,114)\">\n      <rect class=\"chip\" width=\"224\" height=\"28\"\/>\n      <text class=\"txt chipText\" x=\"112\" y=\"19\" text-anchor=\"middle\">\n        Incident response &amp; recovery\n      <\/text>\n    <\/g>\n  <\/g>\n\n  <!-- Flows -->\n  <path class=\"flow arrow\" d=\"M300 200 L330 200\"\/>\n  <path class=\"flow arrow\" d=\"M660 200 L700 200\"\/>\n\n<\/svg>\n\n  <figcaption class=\"gp-rds-caption\">\n    Reference architecture illustrating governance, secure CI\/CD,\n    operations, incident management and supply chain security under NIS2.\n  <\/figcaption>\n<\/figure>\n\n\n\n<p><strong>\u201cNIS2 Security Architecture \u2013 Secure Delivery and Operations\u201d<\/strong><\/p>\n\n\n\n<p>Cette architecture illustre comment les organisations peuvent impl\u00e9menter les exigences NIS2 sur l&rsquo;ensemble du cycle de vie des services num\u00e9riques, de la gouvernance et du d\u00e9veloppement \u00e0 la production et \u00e0 la r\u00e9ponse aux incidents.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Comment lire ce diagramme<\/strong><\/h2>\n\n\n\n<p>Le diagramme est structur\u00e9 <strong>de gauche \u00e0 droite<\/strong>, suivant le cycle de vie de la livraison et de l&rsquo;exploitation des services num\u00e9riques :<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li><strong>Gouvernance et gestion des risques<\/strong><\/li>\n\n\n\n<li><strong>D\u00e9veloppement s\u00e9curis\u00e9 et CI\/CD<\/strong><\/li>\n\n\n\n<li><strong>Op\u00e9rations et gestion des incidents<\/strong><\/li>\n<\/ol>\n\n\n\n<p>A cross-cutting security and evidence layer applies across all components, reflecting NIS2\u2019s emphasis on continuous cybersecurity posture and preparedness.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Couche de gouvernance et de gestion des cyber-risques<\/strong><\/h2>\n\n\n\n<p>La couche de gouvernance refl\u00e8te les exigences NIS2 li\u00e9es \u00e0 la gestion des risques, \u00e0 la responsabilit\u00e9 et aux mesures organisationnelles.<\/p>\n\n\n\n<p>Cette couche comprend :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u00c9valuations des risques de cybers\u00e9curit\u00e9<\/li>\n\n\n\n<li>Politiques et normes de s\u00e9curit\u00e9<\/li>\n\n\n\n<li>R\u00f4les et responsabilit\u00e9s d\u00e9finis<\/li>\n\n\n\n<li>Supervision et revue par la direction<\/li>\n<\/ul>\n\n\n\n<p>Sous NIS2, la responsabilit\u00e9 s&rsquo;\u00e9tend \u00e0 la direction ex\u00e9cutive. L&rsquo;architecture de s\u00e9curit\u00e9 doit donc soutenir une propri\u00e9t\u00e9 claire et un contr\u00f4le d\u00e9montrable.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Couche de d\u00e9veloppement s\u00e9curis\u00e9 et CI\/CD<\/strong><\/h2>\n\n\n\n<p>NIS2 exige explicitement des organisations qu&rsquo;elles impl\u00e9mentent des <strong>pratiques de d\u00e9veloppement s\u00e9curis\u00e9<\/strong> et g\u00e8rent les risques tout au long de la cha\u00eene d&rsquo;approvisionnement.<\/p>\n\n\n\n<p>Dans cette architecture, les pipelines CI\/CD agissent comme points d&rsquo;application pour :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pratiques de d\u00e9veloppement logiciel s\u00e9curis\u00e9<\/li>\n\n\n\n<li>Contr\u00f4le d&rsquo;acc\u00e8s et s\u00e9paration des fonctions<\/li>\n\n\n\n<li>Tests de s\u00e9curit\u00e9 (SAST, analyse de d\u00e9pendances, d\u00e9tection de secrets)<\/li>\n\n\n\n<li>Att\u00e9nuation des risques de la cha\u00eene d&rsquo;approvisionnement<\/li>\n<\/ul>\n\n\n\n<p>Les pipelines CI\/CD garantissent que les contr\u00f4les de s\u00e9curit\u00e9 sont appliqu\u00e9s de mani\u00e8re coh\u00e9rente avant que le logiciel n&rsquo;atteigne les environnements de production.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Couche op\u00e9rations et gestion des incidents<\/strong><\/h2>\n\n\n\n<p>La couche op\u00e9rationnelle r\u00e9pond aux exigences NIS2 en mati\u00e8re de d\u00e9tection, de r\u00e9ponse et de r\u00e9silience.<\/p>\n\n\n\n<p>Les capacit\u00e9s cl\u00e9s incluent :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Surveillance et journalisation continues<\/li>\n\n\n\n<li>D\u00e9tection et classification des incidents<\/li>\n\n\n\n<li>R\u00e9ponse coordonn\u00e9e aux incidents<\/li>\n\n\n\n<li>M\u00e9canismes de r\u00e9cup\u00e9ration et de continuit\u00e9 de service<\/li>\n<\/ul>\n\n\n\n<p>Les pipelines CI\/CD s&rsquo;int\u00e8grent aux op\u00e9rations pour soutenir la rem\u00e9diation rapide et la r\u00e9cup\u00e9ration contr\u00f4l\u00e9e suite aux incidents de s\u00e9curit\u00e9.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>S\u00e9curit\u00e9 de la cha\u00eene d&rsquo;approvisionnement (pr\u00e9occupation transversale)<\/strong><\/h2>\n\n\n\n<p>NIS2 met explicitement l&rsquo;accent sur la s\u00e9curit\u00e9 de la cha\u00eene d&rsquo;approvisionnement. Cette architecture int\u00e8gre les contr\u00f4les de la cha\u00eene d&rsquo;approvisionnement \u00e0 travers le d\u00e9veloppement et les op\u00e9rations :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Validation et surveillance des d\u00e9pendances<\/li>\n\n\n\n<li>Int\u00e9grit\u00e9 des artefacts et provenance<\/li>\n\n\n\n<li>Int\u00e9grations tierces contr\u00f4l\u00e9es<\/li>\n\n\n\n<li>Visibilit\u00e9 sur les services externalis\u00e9s<\/li>\n<\/ul>\n\n\n\n<p>Ces contr\u00f4les r\u00e9duisent l&rsquo;exposition aux attaques de la cha\u00eene d&rsquo;approvisionnement logicielle et aux risques tiers.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Preuves continues et responsabilit\u00e9<\/strong><\/h2>\n\n\n\n<p>\u00c0 travers toutes les couches, l&rsquo;architecture g\u00e9n\u00e8re des <strong>preuves de s\u00e9curit\u00e9 continues<\/strong>, notamment :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Journaux et donn\u00e9es de surveillance<\/li>\n\n\n\n<li>R\u00e9sultats des tests de s\u00e9curit\u00e9<\/li>\n\n\n\n<li>Historiques de d\u00e9ploiement et de changements<\/li>\n\n\n\n<li>Enregistrements de traitement des incidents<\/li>\n<\/ul>\n\n\n\n<p>Ces preuves soutiennent la supervision r\u00e9glementaire, les obligations de signalement d&rsquo;incidents et l&rsquo;analyse post-incident requises par NIS2.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Pourquoi cette architecture est importante pour NIS2<\/strong><\/h2>\n\n\n\n<p>NIS2 exige des organisations qu&rsquo;elles <strong>d\u00e9montrent une gestion efficace des risques de cybers\u00e9curit\u00e9<\/strong>, et pas seulement qu&rsquo;elles la documentent.<\/p>\n\n\n\n<p>Cette architecture permet :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>L&rsquo;application technique des mesures de cybers\u00e9curit\u00e9<\/li>\n\n\n\n<li>Une visibilit\u00e9 continue sur la posture de s\u00e9curit\u00e9<\/li>\n\n\n\n<li>Une d\u00e9tection et une r\u00e9ponse plus rapides aux incidents<\/li>\n\n\n\n<li>Une responsabilit\u00e9 claire entre les \u00e9quipes et la direction<\/li>\n<\/ul>\n\n\n\n<p>En int\u00e9grant la s\u00e9curit\u00e9 dans la livraison et les op\u00e9rations, les organisations peuvent r\u00e9pondre aux attentes NIS2 de mani\u00e8re durable.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>De l&rsquo;architecture \u00e0 l&rsquo;impl\u00e9mentation<\/strong><\/h2>\n\n\n\n<p>Cette architecture fournit une r\u00e9f\u00e9rence de haut niveau. Les d\u00e9tails d&rsquo;impl\u00e9mentation pratique et les guides d&rsquo;audit sont couverts dans le contenu associ\u00e9, notamment :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><a href=\"https:\/\/regulated-devsecops.com\/fr\/ci-cd-security\/\" data-type=\"page\" data-id=\"11\">CI\/CD Security<\/a><\/strong><\/li>\n\n\n\n<li><strong><a href=\"https:\/\/regulated-devsecops.com\/compliance\/\" data-type=\"page\" data-id=\"17\">Compliance<\/a><\/strong><\/li>\n\n\n\n<li><strong><a href=\"https:\/\/regulated-devsecops.com\/fr\/regulatory-frameworks\/ci-cd-red-flags-by-regulation-explained-2\/\" data-type=\"post\" data-id=\"303\">CI\/CD Audit Red Flags<\/a><\/strong><\/li>\n\n\n\n<li><strong><a href=\"https:\/\/regulated-devsecops.com\/fr\/regulatory-frameworks\/before-the-auditor-arrives-ci-cd-audit-readiness-checklist\/\" data-type=\"post\" data-id=\"266\">Before the Auditor Arrives \u2014 Checklist<\/a><\/strong><\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p>La conformit\u00e9 NIS2 commence par l&rsquo;architecture. En int\u00e9grant la gouvernance, le d\u00e9veloppement s\u00e9curis\u00e9, l&rsquo;application CI\/CD et la r\u00e9silience op\u00e9rationnelle dans une architecture de s\u00e9curit\u00e9 unifi\u00e9e, les organisations peuvent r\u00e9pondre aux exigences NIS2 de mani\u00e8re proactive et coh\u00e9rente.<\/p>\n\n\n\n<p>Ce diagramme fournit une compr\u00e9hension claire et partag\u00e9e de la fa\u00e7on dont les obligations de s\u00e9curit\u00e9 NIS2 sont impl\u00e9ment\u00e9es dans les syst\u00e8mes num\u00e9riques modernes.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n    <section class=\"rds-author-box rds-author-box--audit\"\r\n             dir=\"ltr\" lang=\"fr\"\r\n             style=\"border:1px solid rgba(100,116,139,.35);border-radius:14px;padding:16px 18px;margin:26px 0 18px;background:rgba(148,163,184,.08);\">\r\n      <strong style=\"margin:0 0 8px; font-size:14px; font-weight:700; letter-spacing:.02em;\">Contexte \u201caudit-ready\u201d<\/strong>\r\n      <p style=\"margin:0; font-size:14px; line-height:1.55;\">Contenu con\u00e7u pour les environnements r\u00e9glement\u00e9s : contr\u00f4les avant outils, enforcement par politiques dans le CI\/CD, et evidence-by-design pour l\u2019audit.<\/p>\r\n      <p style=\"margin:0; font-size:14px; line-height:1.55;\">Focus sur la tra\u00e7abilit\u00e9, les approbations, la gouvernance des exceptions et la r\u00e9tention des preuves de bout en bout.<\/p>\r\n      <p style=\"margin:0; font-size:14px; line-height:1.55;\">\r\n        <a href=\"https:\/\/regulated-devsecops.com\/fr\/fr\/about\/\">Voir la m\u00e9thodologie sur la page About.<\/a>\r\n      <\/p>\r\n    <\/section>\r\n    \n","protected":false},"excerpt":{"rendered":"<p>La directive NIS2 renforce consid\u00e9rablement les exigences en mati\u00e8re de cybers\u00e9curit\u00e9 et de gestion des risques pour les entit\u00e9s essentielles et importantes \u00e0 travers l&rsquo;Union europ\u00e9enne. Contrairement aux approches purement politiques, NIS2 met fortement l&rsquo;accent sur les contr\u00f4les techniques, la pr\u00e9paration op\u00e9rationnelle et les mesures de s\u00e9curit\u00e9 d\u00e9montrables. Cette page explique une architecture de s\u00e9curit\u00e9 &#8230; <a title=\"Architecture de s\u00e9curit\u00e9 NIS2 \u2014 Expliqu\u00e9e\" class=\"read-more\" href=\"https:\/\/regulated-devsecops.com\/fr\/regulatory-frameworks\/nis2-security-architecture-explained\/\" aria-label=\"En savoir plus sur Architecture de s\u00e9curit\u00e9 NIS2 \u2014 Expliqu\u00e9e\">Lire la suite<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[126],"tags":[],"post_folder":[],"class_list":["post-1243","post","type-post","status-publish","format-standard","hentry","category-regulatory-frameworks"],"_links":{"self":[{"href":"https:\/\/regulated-devsecops.com\/fr\/wp-json\/wp\/v2\/posts\/1243","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/regulated-devsecops.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/regulated-devsecops.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/regulated-devsecops.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/regulated-devsecops.com\/fr\/wp-json\/wp\/v2\/comments?post=1243"}],"version-history":[{"count":0,"href":"https:\/\/regulated-devsecops.com\/fr\/wp-json\/wp\/v2\/posts\/1243\/revisions"}],"wp:attachment":[{"href":"https:\/\/regulated-devsecops.com\/fr\/wp-json\/wp\/v2\/media?parent=1243"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regulated-devsecops.com\/fr\/wp-json\/wp\/v2\/categories?post=1243"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regulated-devsecops.com\/fr\/wp-json\/wp\/v2\/tags?post=1243"},{"taxonomy":"post_folder","embeddable":true,"href":"https:\/\/regulated-devsecops.com\/fr\/wp-json\/wp\/v2\/post_folder?post=1243"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}