{"id":2274,"date":"2026-06-01T19:18:07","date_gmt":"2026-06-01T19:18:07","guid":{"rendered":"https:\/\/www.pickplace.de\/?post_type=glossary&#038;p=2274"},"modified":"2026-06-01T19:21:00","modified_gmt":"2026-06-01T19:21:00","slug":"iec-62443","status":"publish","type":"glossary","link":"https:\/\/www.pickplace.de\/en\/glossar\/iec-62443\/","title":{"rendered":"IEC 62443"},"content":{"rendered":"<p class=\"wp-block-paragraph\">IEC 62443 is a series of international standards for <a href=\"https:\/\/www.pickplace.de\/en\/embedded-systems-cybersecurity\/\" data-type=\"page\" data-id=\"954\">Cybersecurity<\/a> Industrial automation and control systems. It describes terms, models, processes, and technical requirements for Industrial Automation and Control Systems, or IACS for short. For embedded systems and industrial electronics, it is primarily relevant wherever controllers, sensors, gateways, industrial PCs, network devices, or software components are used in production facilities.<\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Content<\/h2><nav><ul><li class=\"\"><a href=\"#was-bedeutet-iec-62443\">What does IEC 62443 cover?<\/a><\/li><li class=\"\"><a href=\"#wie-funktioniert-iec-62443\">How does IEC 62443 work?<\/a><\/li><li class=\"\"><a href=\"#die-wichtigsten-teile-fur-produkthersteller\">The most important parts of the standard for product manufacturers<\/a><ul><li class=\"\"><a href=\"#iec-62443-3-2\">IEC 62443-3-2<\/a><\/li><li class=\"\"><a href=\"#zones-und-conduits-nach-iec-62443\">Zones and Conduits<\/a><\/li><li class=\"\"><a href=\"#warum-zones-und-conduits-wichtig-sind\">Meaning for ICAS manufacturers<\/a><\/li><li class=\"\"><a href=\"#iec-62443-4-1\">IEC 62443-4-1<\/a><\/li><li class=\"\"><a href=\"#iec-62443-4-2\">IEC 62443-4-2<\/a><\/li><\/ul><\/li><li class=\"\"><a href=\"#verwendungsrahmen-der-iec-62443\">IEC 62443 Usage Framework<\/a><\/li><li class=\"\"><a href=\"#grenzen-und-typische-missverstandnisse\">Boundaries and typical misunderstandings<\/a><\/li><\/ul><\/nav><\/div>\n\n\n\n<h2 id=\"was-bedeutet-iec-62443\" class=\"wp-block-heading\">What does IEC 62443 cover?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">IEC 62443 addresses cybersecurity in industrial environments. It is intended for several roles: plant operators, automation system integrators, and component manufacturers. The standard series differentiates between requirements for organizations, systems, development processes, and individual components.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The term IACS encompasses automation and control systems that monitor, regulate, or control industrial processes. This includes, for example, controllers, operator stations, engineering systems, network infrastructure, industrial software, and embedded devices. IEC 62443 considers such systems not just as IT systems, but as components of technical facilities where availability, integrity, controlled access, and protection against manipulation can have technical consequences.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For embedded devices and industrial electronics, three parts of the standards series are particularly influential:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>IEC 62443-3-2 for security risk assessment in system design<\/li>\n\n\n\n<li>IEC 62443-4-1 for the secure product development process<\/li>\n\n\n\n<li>IEC 62443-4-2 for technical safety requirements for components<\/li>\n<\/ul>\n\n\n\n<div class=\"wp-block-stackable-image stk-block-image stk-block stk-d6fa40e\" data-block-id=\"d6fa40e\"><style>.stk-d6fa40e .stk-img-figcaption{text-align:center !important;}.stk-d6fa40e .stk-img-wrapper{width:null% !important;height:nullpx !important;}<\/style><figure><span class=\"stk-img-wrapper stk-image--shape-stretch\"><img loading=\"lazy\" decoding=\"async\" class=\"stk-img wp-image-2277\" src=\"https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/06\/image.png\" width=\"1049\" height=\"645\" alt=\"Diagram of IEC 62443 Security Building Blocks for IACS: General, Policies, System, Component; Focus on embedded software.\" srcset=\"https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/06\/image.png 1049w, https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/06\/image-300x184.png 300w, https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/06\/image-1024x630.png 1024w, https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/06\/image-768x472.png 768w, https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/06\/image-18x12.png 18w\" sizes=\"auto, (max-width: 1049px) 100vw, 1049px\"\/><\/span><figcaption class=\"stk-img-figcaption\"><em>Preliminary Outline of IEC 62443 (Source: <a href=\"https:\/\/www.evs.ee\/en\/en-iec-62443-4-2-2019-praa-2026\" target=\"_blank\" rel=\"noopener\">EVS<\/a>)<\/em><\/figcaption><\/figure><\/div>\n\n\n\n<h2 id=\"wie-funktioniert-iec-62443\" class=\"wp-block-heading\">How does IEC 62443 work?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The series of standards works on a risk-oriented basis. First, the subject under consideration is described. In IEC 62443-3-2, the System Under Consideration, or SUC for short, is delineated for this purpose. This system is examined with its environment, its interfaces, and its architecture.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Subsequently, the system is divided into zones and transitions. A zone groups components with comparable security requirements. A transition describes the connection between zones. Risks are analyzed for each zone and transition. This includes considering vulnerabilities, threats, existing countermeasures, and potential consequences.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A target security level is derived from this assessment. This security level describes the level of protection that is to be aimed for in a zone, transition, system, or component. The security level is not a general quality grade. It refers to the threat profiles, resources, and capabilities of potential attackers, as well as the intended application context.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For products, IEC 62443-4-1 supplements this view with requirements for the development process. It describes how manufacturers capture security requirements, make secure architecture and implementation decisions, perform security testing, handle vulnerabilities, manage updates, and provide security documentation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">IEC 62443-4-2 focuses on the component level. It describes the technical security functions that industrial components must provide when designed for a specific Security Level. The standard considers embedded devices, host devices, network devices, and software applications.<\/p>\n\n\n\n<h2 id=\"die-wichtigsten-teile-fur-produkthersteller\" class=\"wp-block-heading\">The most important parts of the standard for product manufacturers<\/h2>\n\n\n\n<h3 id=\"iec-62443-3-2\" class=\"wp-block-heading\">IEC 62443-3-2<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">IEC 62443-3-2 addresses security risk assessment for system design. It provides a method for deriving security requirements from a specific industrial architecture.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The process begins with a description of the system under consideration. Then, zones and transitions are defined. Risks are identified and assessed for these areas. This leads to target security levels and subsequently derived security requirements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical threats in an industrial environment concern availability, integrity, and confidentiality. Examples include interference with control functions, blocked safety-related equipment, suppressed warning messages, altered measured values, manipulated operating parameters, or spied-upon access credentials. IEC 62443-3-2 does not assess such threats in isolation but in the context of system architecture, vulnerabilities, and existing security measures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For embedded and industrial electronics, this part of the standard is significant because the requirements for a device often arise from the system environment. A controller, a sensor, or a gateway may have different requirements in an isolated zone compared to an architecture with a direct connection to higher-level systems or external services.<\/p>\n\n\n\n<h3 id=\"zones-und-conduits-nach-iec-62443\" class=\"wp-block-heading\">Zones and Conduits<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The concept of Zones and Conduits is one of the central architectural principles in the risk section. It serves to view industrial systems not as one large, uniform network, but to divide them into security-relevant areas. The goal is not only better overview, but above all the controlled limitation of communication, access, and potential attack impacts.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A zone is a group of systems, components, or network segments that are intended to be treated similarly from a security perspective. The systems within a zone therefore have comparable protection requirements, similar functionalities, or comparable risks. For example, a zone can consist of several controllers of a machine, an HMI with the associated controllers, an engineering network, or an area with particularly critical process functions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What's important: A zone is not necessarily identical to an IP subnet, a control cabinet, or a physical plant. Such features can help with the definition, but they are not solely decisive. A zone is primarily a security and architectural decision. It describes which systems are considered together and what protection profile should apply to these systems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In contrast, a conduit describes the connection between zones. Communication takes place between two or more zones via a conduit. These can be physical network connections, firewall rules, VPN connections, remote access routes, protocol transitions, or application interfaces. The conduit is therefore not just \u201ethe cable\u201c between two areas, but the defined and controlled communication relationship between zones.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The crucial point is: Not every zone is allowed to communicate freely with every other zone. Instead, it's determined which communication is necessary, which protocols may be used, which systems are allowed to talk to each other, and what security measures are needed at the transitions. It is precisely at these transitions that the most important security mechanisms of a segmented industrial architecture are created.<\/p>\n\n\n\n<div class=\"wp-block-stackable-image stk-block-image stk-block stk-2eb4588\" data-block-id=\"2eb4588\"><style>.stk-2eb4588 .stk-img-figcaption{text-align:center !important;font-style:italic !important;}.stk-2eb4588 .stk-img-wrapper{width:70% !important;}<\/style><figure><span class=\"stk-img-wrapper stk-image--shape-stretch\"><img loading=\"lazy\" decoding=\"async\" class=\"stk-img wp-image-2278\" src=\"https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/06\/cra-iec-62443-zone-conduit-concept.jpg\" width=\"1000\" height=\"750\" alt=\"Zones and Conduits Model in IEC 62443\" srcset=\"https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/06\/cra-iec-62443-zone-conduit-concept.jpg 1000w, https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/06\/cra-iec-62443-zone-conduit-concept-300x225.jpg 300w, https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/06\/cra-iec-62443-zone-conduit-concept-768x576.jpg 768w, https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/06\/cra-iec-62443-zone-conduit-concept-16x12.jpg 16w\" sizes=\"auto, (max-width: 1000px) 100vw, 1000px\"\/><\/span><figcaption class=\"stk-img-figcaption\">Zones and Conduits Model in IEC 62443<\/figcaption><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">In practice, a zone can be, for example, a plant network in which one or more PLCs, decentralized I\/O modules, drives, sensors, fieldbuses, and possibly also wireless interfaces are grouped together. The zone then describes a functional and safety-related area of the plant. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Zone transitions are the points where communication with other zones becomes possible. These include, for example, connections to an HMI network, an engineering network, a control system, a cloud connection, or remote maintenance access. In the IEC 62443 context, such transitions are considered conduits or at least described via conduits.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What is important here is that maintenance interfaces, service ports, USB access points, wireless interfaces, diagnostic adapters, temporary engineering connections, or remote access solutions can also be entry points into a zone. From an attacker's perspective, these are precisely the points of interest because they enable communication into a protected area. Therefore, it must also be documented which communication paths exist into and out of the zone, which of them are permanently active, which are used only for maintenance or commissioning, and what protective measures are applied at these transition points. <\/p>\n\n\n\n<h3 id=\"warum-zones-und-conduits-wichtig-sind\" class=\"wp-block-heading\">Meaning for ICAS manufacturers<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Manufacturers of industrial electronics should classify early in the IEC-62443 consideration what role their device will play in the later plant architecture. A device can be an asset within a zone, for example a controller, a sensor, an actuator, an HMI, or an embedded gateway within a functional plant section. However, it can also perform a transitional function between two zones, for instance, when it forwards communication, translates protocols, enables remote access, transmits data towards IT, cloud, or historian, or is used as a gateway between the machine and control levels.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This distinction is relevant for security. A device within a zone must meet the security requirements of that zone. In contrast, a device in a conduit directly influences which communication between zones is possible and what attack vectors arise from it. In this case, it's not just about securing the device itself, but also about access control, protocol limiting, authentication, logging, updateability, and the question of whether unwanted communication between zones can be prevented.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For manufacturers, this means that the security requirements for a product depend not only on its function but also on its architectural role within the overall system. An identical embedded device can be evaluated differently depending on its use case. Different requirements apply to a local participant within a zone compared to a device that connects two network areas or transmits data from an OT zone to other systems. Therefore, the intended use scenarios for the device, the supported communication relationships, and the security mechanisms available at zone boundaries should be documented as early as the product development stage.<\/p>\n\n\n\n<h3 id=\"iec-62443-4-1\" class=\"wp-block-heading\">IEC 62443-4-1<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">IEC 62443-4-1 describes requirements for a Secure Product Development Lifecycle. This part of the standard therefore addresses the development process, not individual technical functions of a product.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The requirements are structured into practices. These include security management, specification of security requirements, secure design, secure implementation, security verification and validation, handling of security-related issues, security update management, and security documentation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The approach aligns with the principle of Security by Design. Security requirements should be considered during requirements analysis, design, implementation, testing, release, and maintenance. For manufacturers of embedded systems, this means, for example, that authentication, update mechanisms, logging, secure default configurations, or the handling of vulnerabilities are not considered only after product release.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">IEC 62443-4-1 also uses Maturity Levels. These describe how development processes are implemented and controlled. The levels range from ad-hoc processes, through documented and organization-wide defined processes, to processes that are improved based on metrics and feedback.<\/p>\n\n\n\n<h3 id=\"iec-62443-4-2\" class=\"wp-block-heading\">IEC 62443-4-2<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">IEC 62443-4-2 describes technical security requirements for components of industrial automation and control systems. This part of the standard concerns individual products, for example, controllers, sensors, switches, industrial firewalls, gateways, host systems, or software applications.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The standard distinguishes component classes such as Software Applications, Embedded Devices, Host Devices, and Network Devices. Embedded Devices are particularly relevant for industrial electronics because many control, measurement, communication, and field devices are implemented as embedded systems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The IEC 62443-4-2 divides its technical requirements into seven Foundational Requirements:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Identification and Authentication Control<\/li>\n\n\n\n<li>Use Control<\/li>\n\n\n\n<li>System Integrity<\/li>\n\n\n\n<li>Data Confidentiality<\/li>\n\n\n\n<li>Restricted Data Flow<\/li>\n\n\n\n<li>Timely Response to Events<\/li>\n\n\n\n<li>Resource Availability<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These requirements concern, among other things, identification and authentication, access control, protection of system integrity, data confidentiality, limitation of data flows, reaction to security-related events, and availability of resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">IEC 62443-4-2 is closely related to IEC 62443-4-1. A component claiming conformity with IEC 62443-4-2 must have been created through a development process that complies with IEC 62443-4-1. Technical security functions and the development process are therefore considered together.<\/p>\n\n\n\n<h2 id=\"verwendungsrahmen-der-iec-62443\" class=\"wp-block-heading\">IEC 62443 Usage Framework<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">IEC 62443 is used in industrial automation environments. These include manufacturing plants, process plants, power supply, machinery, industrial networks, control technology, and systems with IT-OT coupling.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For operators, the standards facilitate the structuring of protection measures for facilities and control systems. For integrators, they help divide systems into zones and transitions and translate safety requirements into architectural decisions. For manufacturers, they serve as a framework for development processes and technical safety functions of components.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For industrial electronics, the reference often arises from component requirements. An IIoT gateway, an industrial firewall, a programmable logic controller, or a condition monitoring sensor can include functions that are rated according to IEC 62443-4-2. For IIoT components, additional questions arise because such devices often communicate with cloud services, bundle multiple functions in one device, or are permanently accessible via network interfaces.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">IEC 62443 separates system considerations, process requirements, and technical component requirements. This separation prevents a single component from being considered sufficiently protected in a blanket manner without an understanding of its environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The series of standards uses Security Levels. These levels describe the intended level of protection in relation to threats and the operational context. A higher Security Level is not automatically required for every product or zone. The selection is based on the risk assessment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Zones and transitions form an architectural model for industrial systems. They help to spatially or logically structure communication relationships, protection requirements, and technical measures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For manufacturers, the standard series connects the development process and product function. IEC 62443-4-1 describes how to develop secure products. IEC 62443-4-2 describes the security functions that components must provide.<\/p>\n\n\n\n<h2 id=\"grenzen-und-typische-missverstandnisse\" class=\"wp-block-heading\">Boundaries and typical misunderstandings<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A common misunderstanding is to treat IEC 62443 as a pure checklist. The standard series requires consideration of system boundaries, deployment context, architecture, threats, and development processes. Without a risk assessment, a Security Level cannot be properly justified.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Another misunderstanding concerns security levels. They do not describe a general seal of approval. They refer to defined threat assumptions and requirements. A component with a specific security level may require additional measures in a different system context.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For regulatory requirements, IEC 62443 can form a basis, but it does not automatically cover every legal framework completely. The sources, for example, describe that IEC 62443-4-1 covers procedural requirements of the <a href=\"https:\/\/www.pickplace.de\/en\/cyber-resilience-act\/\" data-type=\"page\" data-id=\"1867\">Cyber Resilience Act<\/a> can support, but further standards may be required for technical requirements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This very aspect is constantly misunderstood when manufacturers interpret IEC 62443 as direct proof of a \u201ecyber-secure product.\u201c However, the standard series primarily describes processes, roles, responsibilities, and procedures for the development, integration, and operation of secure industrial systems. It is therefore more of a management system than a requirements document.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a manufacturer can attest or certify that its development processes are aligned with IEC 62443. However, this initially only means that specific organizational and technical development processes are defined, documented, and applied.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The <a href=\"https:\/\/www.tuvsud.com\/de-de\/dienstleistungen\/produktpruefung-und-produktzertifizierung\/zertifizierung-nach-iec62443\" target=\"_blank\" rel=\"noopener\">T\u00dcV S\u00dcD<\/a> explicitly offers the following range of services.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Product manufacturer<\/strong>can be certified according to IEC 62443-4-1 (secure product development).<\/li>\n\n\n\n<li><strong>Integrators and service providers<\/strong>can obtain a certificate according to IEC 62443-2-4 (Service Provider Security Program).<\/li>\n\n\n\n<li><strong>For Operators<\/strong>Are certifications according to IEC 62443-2-1 offered<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This does not automatically mean that every product from this manufacturer is cyber-secure or can be safely used in every installation. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A product may have originated from an IEC 62443 compliant development process and still contain vulnerabilities, be incorrectly configured for the specific use case, or not align with the security requirements of a particular zone. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A manufacturer's or supplier's attestation is a helpful proof for integrators, but it does not replace their own risk analysis or verification of whether the specific device is suitable for the intended zone or conduit. Conversely, manufacturers should clearly document what their products actually deliver: What interfaces are available? Which security functions are supported? What assumptions apply to operation? Which configurations are security-relevant? What requirements must be met by the operator or integrator?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">IEC 62443 is therefore not a seal of approval that makes a product generally secure. It is a framework with which security can be systematically addressed. However, the actual proof of security only emerges in the specific context: for a particular product, a particular system architecture, a particular threat situation, and a defined operation.<\/p>","protected":false},"excerpt":{"rendered":"<p>IEC 62443 ist eine internationale Normenreihe f\u00fcr die Cybersicherheit industrieller Automatisierungs- und Steuerungssysteme. Sie beschreibt Begriffe, Modelle, Prozesse und technische Anforderungen f\u00fcr Industrial Automation and Control Systems, kurz IACS. F\u00fcr Embedded-Systeme und Industrieelektronik ist sie vor allem dort ma\u00dfgeblich, wo Steuerungen, Sensoren, Gateways, Industrie-PCs, Netzwerkger\u00e4te oder Softwarekomponenten in Produktionsanlagen eingesetzt werden. Was umfasst die IEC [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"menu_order":0,"template":"","meta":{"footnotes":""},"class_list":["post-2274","glossary","type-glossary","status-publish","hentry"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/glossary\/2274","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/types\/glossary"}],"author":[{"embeddable":true,"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":3,"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/glossary\/2274\/revisions"}],"predecessor-version":[{"id":2279,"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/glossary\/2274\/revisions\/2279"}],"wp:attachment":[{"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/media?parent=2274"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}