{"id":8845,"date":"2021-05-17T23:15:44","date_gmt":"2021-05-17T20:15:44","guid":{"rendered":"https:\/\/kifarunix.com\/?p=8845"},"modified":"2024-03-18T22:23:43","modified_gmt":"2024-03-18T19:23:43","slug":"install-zeek-on-ubuntu","status":"publish","type":"post","link":"https:\/\/kifarunix.com\/install-zeek-on-ubuntu\/","title":{"rendered":"Install Zeek on Ubuntu 20.04"},"content":{"rendered":"\n<p>Follow through this tutorial to learn how to install Zeek  on Ubuntu 20.04. <a aria-label=\"Zeek (opens in a new tab)\" href=\"https:\/\/zeek.org\/\" target=\"_blank\" rel=\"noreferrer noopener\" class=\"rank-math-link\">Zeek<\/a>, formerly Bro IDS, is the world&#8217;s leading passive open source&nbsp;network security monitoring tool.<\/p>\n\n\n\n<p><em>Zeek is not an active security device, like a firewall or intrusion prevention system. Rather, Zeek sits on a \u201csensor,\u201d a hardware, software, virtual, or cloud platform that quietly and unobtrusively observes network traffic. Zeek interprets what it sees and creates compact, high-fidelity transaction logs, file content, and fully customized output, suitable for manual review on disk or in a more analyst-friendly tool like a security and information event management (SIEM) system<\/em>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Installing Zeek on Ubuntu 20.04<\/h2>\n\n\n\n<p>Zeek can be installed by <a href=\"https:\/\/docs.zeek.org\/en\/lts\/install.html#installing-zeek\" target=\"_blank\" rel=\"noreferrer noopener nofollow\" class=\"rank-math-link\">building it from the source code<\/a> or by directly via the <a href=\"#install-zeek-from-apt\" class=\"rank-math-link\">Zeek APT repositories<\/a>.<\/p>\n\n\n\n<p>In this tutorial, we will choose the later.<\/p>\n\n\n\n<p>To install Zeek from the Zeek APT repositories;<\/p>\n\n\n\n<p>Add Zeek repository to Ubuntu 20.04:<\/p>\n\n\n\n<pre id=\"block-a365d415-0482-492d-9a1f-ee13b977fc10\" class=\"wp-block-preformatted\">echo 'deb http:\/\/download.opensuse.org\/repositories\/security:\/zeek\/xUbuntu_20.04\/ \/' | sudo tee \/etc\/apt\/sources.list.d\/security:zeek.list<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>curl -fsSL https:\/\/download.opensuse.org\/repositories\/security:zeek\/xUbuntu_20.04\/Release.key | gpg --dearmor | sudo tee \/etc\/apt\/trusted.gpg.d\/security_zeek.gpg &gt; \/dev\/null<\/code><\/pre>\n\n\n\n<p>Run system update;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>apt update<\/code><\/pre>\n\n\n\n<p>Zeek 4.0.1 is the current stable release as of this writing, confirm the same by running the command below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>apt-cache policy zeek<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>zeek:\n  Installed: (none)\n  Candidate: 4.0.1-0\n  Version table:\n     4.0.1-0 500\n        500 http:\/\/download.opensuse.org\/repositories\/security:\/zeek\/xUbuntu_20.04  Packages<\/code><\/pre>\n\n\n\n<p>You can then install Zeek by running the command below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>apt install zeek<\/code><\/pre>\n\n\n\n<p>During the installation, you will be prompted for some Postfix settings, choose Internet Site and enter your system FQDN.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Configuring Zeek on Ubuntu 20.04<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">Configure the Run-Time Environment<\/h4>\n\n\n\n<p>By default, Zeek is installed under <code><strong>\/opt\/zeek<\/strong><\/code>.<\/p>\n\n\n\n<p>To begin with, add Zeek binary path to PATH;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>echo \"export PATH=$PATH:\/opt\/zeek\/bin\" &gt;&gt; ~\/.bashrc<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>source ~\/.bashrc<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Define the Local Networks to Monitor<\/h4>\n\n\n\n<p>Next, you need to tell Zeek which local networks to monitor. This can be specified in the <code><strong>\/opt\/zeek\/etc\/networks.cfg<\/strong><\/code> configuration file.<\/p>\n\n\n\n<p>The default networks defined are <strong>10.0.0.0\/8, 172.16.0.0\/16, 192.168.0.0\/16<\/strong>. So, in our case, the network  we want to monitor is <strong>192.168.59.0\/24<\/strong>.<\/p>\n\n\n\n<p>Hence;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>vim \/opt\/zeek\/etc\/networks.cfg<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\n# List of local networks in CIDR notation, optionally followed by a\n# descriptive tag.\n# For example, \"10.0.0.0\/8\" or \"fe80::\/64\" are valid prefixes.\n\n#10.0.0.0\/8          Private IP space\n#172.16.0.0\/12       Private IP space\n#192.168.0.0\/16      Private IP space\n<strong>192.168.59.0\/24      Kifarunix-demo IP space<\/strong>\n<\/code><\/pre>\n\n\n\n<p>Save the file and exit once you made your network configuration changes.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Configure Zeek Cluster<\/h4>\n\n\n\n<p>Zeek can be run in standalone mode or in a cluster setup. To define whether to run in a cluster or standalone setup, you need to edit the <code><strong>\/opt\/zeek\/etc\/node.cfg<\/strong><\/code> configuration file.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><em>For a standalone configuration, there must be only one Zeek node defined in this file.<\/em><\/li>\n\n\n\n<li><em>For a cluster configuration, at a minimum there must be a manager node, a proxy node, and one or more worker nodes.<\/em><\/li>\n<\/ul>\n\n\n\n<p>According to Zeek quickstart guide, <em>using the standalone \/ single process mode of Zeek is not suitable for setups with significant amounts of traffic. In these cases one will almost certainly want to make use of a Zeek cluster, even on a single system<\/em>.<\/p>\n\n\n\n<p>Therefore, we will see how to setup Zeek cluster. You can have a look at <a aria-label=\"Zeek cluster architecture (opens in a new tab)\" href=\"https:\/\/docs.zeek.org\/en\/master\/cluster-setup.html#architecture\" target=\"_blank\" rel=\"noreferrer noopener nofollow\" class=\"rank-math-link\">Zeek cluster architecture<\/a>.<\/p>\n\n\n\n<p>The default Zeek node configuration is like;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>cat \/opt\/zeek\/etc\/node.cfg<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\n# Example ZeekControl node configuration.\n#\n# This example has a standalone node ready to go except for possibly changing\n# the sniffing interface.\n\n# This is a complete standalone configuration.  Most likely you will\n# only need to change the interface.\n[zeek]\ntype=standalone\nhost=localhost\ninterface=eth0\n\n## Below is an example clustered configuration. If you use this,\n## remove the [zeek] node above.\n\n#[logger-1]\n#type=logger\n#host=localhost\n#\n#[manager]\n#type=manager\n#host=localhost\n#\n#[proxy-1]\n#type=proxy\n#host=localhost\n#\n#[worker-1]\n#type=worker\n#host=localhost\n#interface=eth0\n#\n#[worker-2]\n#type=worker\n#host=localhost\n#interface=eth0\n<\/code><\/pre>\n\n\n\n<p>Since we are running a single node Zeek Cluster in this setup, comment out the Zeek standalone configuration, section under <code><strong>[zeek]<\/strong><\/code> and define host address for your Zeek <code><strong>logger<\/strong><\/code>, <code><strong>manager<\/strong><\/code>, <code><strong>proxy<\/strong><\/code> and <code><strong>worker<\/strong><\/code>.<\/p>\n\n\n\n<p>So what are these components;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>logger<\/strong>: <em>it is an optional Zeek process that receives log messages from the rest of the nodes in the cluster. It can be used instead of the manager to reduce the load on the manager itself<\/em>.<\/li>\n\n\n\n<li><strong>manager<\/strong>:  <em>receives log messages and notices from the rest of the nodes in the Zeek cluster if no logger is defined<\/em>. <\/li>\n\n\n\n<li><strong>proxy<\/strong>: <em>is a Zeek process that may be used to offload data storage or any arbitrary workload. A cluster may contain multiple proxy nodes<\/em>.<\/li>\n\n\n\n<li><strong>worker<\/strong>: <em>is the Zeek process that sniffs network traffic and does protocol analysis on the reassembled traffic streams.<\/em><\/li>\n<\/ul>\n\n\n\n<p>So below is our single node Zeek cluster configuration setup;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>cat \/opt\/zeek\/etc\/node.cfg<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\n# Example ZeekControl node configuration.\n#\n# This example has a standalone node ready to go except for possibly changing\n# the sniffing interface.\n\n# This is a complete standalone configuration.  Most likely you will\n# only need to change the interface.\n#[zeek]\n#type=standalone\n#host=localhost\n#interface=eth0\n\n## Below is an example clustered configuration. If you use this,\n## remove the [zeek] node above.\n\n[kifarunix-demo-zeek-logger]\ntype=logger\nhost=192.168.59.16\n#\n[kifarunix-demo-zeek-manager]\ntype=manager\nhost=192.168.59.16\n#\n[kifarunix-demo-zeek-proxy]\ntype=proxy\nhost=192.168.59.16\n#\n[kifarunix-demo-zeek-worker]\ntype=worker\nhost=192.168.59.16\ninterface=enp0s8\n#\n[kifarunix-demo-worker-lo]\ntype=worker\nhost=localhost\ninterface=lo\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Review Global ZeekControl configuration file<\/h4>\n\n\n\n<p>Next, you need to review the global ZeekControl configuration file, <code><strong>\/opt\/zeek\/etc\/zeekctl.cfg<\/strong><\/code>.<\/p>\n\n\n\n<p>Most of the default values in configuration files should suffice. The only change you might want to make or update here is the recipient address for all emails sent out by Zeek and ZeekControl, if you have any set. The default value is root@localhost.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Validate Zeek Configuration<\/h4>\n\n\n\n<p>Before you can install and start Zeek, you need to validate the configuration file;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>zeekctl check<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\nHint: Run the zeekctl \"deploy\" command to get started.\nkifarunix-demo-zeek-logger scripts are ok.\nkifarunix-demo-zeek-manager scripts are ok.\nkifarunix-demo-zeek-proxy scripts are ok.\nkifarunix-demo-zeek-worker scripts are ok.\nkifarunix-demo-worker-lo scripts are ok.\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Deploy ZeekControl Configurations<\/h4>\n\n\n\n<p>If all is fine, install ZeekControl configuration and start the Zeek instance;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>zeekctl deploy<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\nchecking configurations ...\ninstalling ...\ncreating policy directories ...\ninstalling site policies ...\ngenerating cluster-layout.zeek ...\ngenerating local-networks.zeek ...\ngenerating zeekctl-config.zeek ...\ngenerating zeekctl-config.sh ...\nstopping ...\nstopping workers ...\nstopping proxy ...\nstopping manager ...\nstopping logger ...\nstarting ...\nstarting logger ...\nstarting manager ...\nstarting proxy ...\nstarting workers ...\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Check the status of Zeek Instance<\/h4>\n\n\n\n<p>You can check the status of Zeek instance by executing;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>zeekctl status<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\nName         Type    Host             Status    Pid    Started\nkifarunix-demo-zeek-logger logger  192.168.59.16    running   17911  17 May 03:52:41\nkifarunix-demo-zeek-manager manager 192.168.59.16    running   17962  17 May 03:52:43\nkifarunix-demo-zeek-proxy proxy   192.168.59.16    running   18011  17 May 03:52:45\nkifarunix-demo-zeek-worker worker  192.168.59.16    running   18081  17 May 03:52:48\nkifarunix-demo-worker-lo worker  localhost        running   18082  17 May 03:52:48\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Checking Zeek Logs<\/h4>\n\n\n\n<p>Zeek will start analyzing traffic according to a default policy and write the log results in&nbsp;<code><strong>\/opt\/zeek\/logs\/current<\/strong><\/code>&nbsp;directory.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>ls -1 \/opt\/zeek\/logs\/current\/<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\nbroker.log\ncapture_loss.log\ncluster.log\nconn.log\ndhcp.log\nknown_services.log\nloaded_scripts.log\nnotice.log\npacket_filter.log\nreporter.log\nstats.log\nstderr.log\nstdout.log\nweird.log\n<\/code><\/pre>\n\n\n\n<p><em>Some logs that are worth explicit mention:<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><em><code><strong>conn.log<\/strong><\/code>: Contains an entry for every connection seen on the wire, with basic properties such as time and duration, originator and responder IP addresses, services and ports, payload size, and much more. This log provides a comprehensive record of the network\u2019s activity.<\/em><\/li>\n\n\n\n<li><em><code><strong>notice.log<\/strong><\/code>: Identifies specific activity that Zeek recognizes as potentially interesting, odd, or bad.  Such activity is called a \u201cnotice\u201d.<\/em><\/li>\n\n\n\n<li><em><code><strong>known_services.log<\/strong><\/code>: This log file contains the services detected on the local network and are known to be actively used by the clients on the network. It helps in enumerating what all services are observed on a local network and if they all are intentional and known to the network administrator.<\/em><\/li>\n\n\n\n<li><em><code><strong>weird.log<\/strong><\/code>: Contains unusual or exceptional activity that can indicate malformed connections, traffic that doesn\u2019t conform to a particular protocol, malfunctioning or misconfigured hardware\/services, or even an attacker attempting to avoid\/confuse a sensor.<\/em><\/li>\n\n\n\n<li><strong>(protocol).log<\/strong> such as (dns.log, dhcp.log, http.log, snmp.log):  contains information for packets found in each respective protocol. <\/li>\n<\/ul>\n\n\n\n<p>Sample <strong>conn.log<\/strong> logs;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>tail \/opt\/zeek\/logs\/current\/conn.log<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\n1621277534.729878\tCY3bmP18QlSIvSFxej\t192.168.59.16\t8132\t192.168.59.16\t80\ttcp\t-\t-\t-\t-\tRSTRH\tT\tT\t0\t^r\t00\t1\t40\t-\n1621277534.729881\tCGVzYD19RQxUT0Vzq\t192.168.59.16\t8133\t192.168.59.16\t80\ttcp\t-\t-\t-\t-\tS0\tT\tT\t0\tS\t140\t0\t0\t-\n1621277534.729883\tC8jp1t2D0NHoUeOiF1\t192.168.59.16\t8133\t192.168.59.16\t80\ttcp\t-\t-\t-\t-\tRSTRH\tT\tT\t0\t^r\t00\t1\t40\t-\n1621277564.065743\tCduRKb4f4bLM38gakl\t192.168.59.16\t47762\t192.168.59.16\t58282\ttcp\t-\t-\t-\t-\tOTH\tT\tT\t0\tCcc00\t0\t0\t-\n1621277564.065833\tCRgk0dMeT9AeMyROd\t192.168.59.16\t47762\t192.168.59.16\t58288\ttcp\t-\t-\t-\t-\tOTH\tT\tT\t0\tCcc00\t0\t0\t-\n1621277564.215195\tCg09q71OaurnFkIdRe\t192.168.59.16\t38834\t192.168.59.16\t47761\ttcp\t-\t-\t-\t-\tOTH\tT\tT\t0\tCc\t00\t0\t0\t-\n1621277566.725573\tCG17M71tH9TV52bBe7\t192.168.59.16\t38836\t192.168.59.16\t47761\ttcp\t-\t-\t-\t-\tOTH\tT\tT\t0\tCc\t00\t0\t0\t-\n1621277574.895432\tC2aJF016ENvM3nF6da\t192.168.59.16\t34700\t192.168.59.16\t80\ttcp\t-\t-\t-\t-\tOTH\tT\tT\t0\tC\t00\t0\t0\t-\n1621277570.315909\tCQp7gp31EAsSvqgIn1\t192.168.59.16\t38846\t192.168.59.16\t47761\ttcp\t-\t-\t-\t-\tOTH\tT\tT\t0\tCc\t00\t0\t0\t-\n1621277574.895458\tCIP6UASndf9AtymV2\t192.168.59.16\t34700\t192.168.59.16\t80\ttcp\t-\t-\t-\t-\tOTH\tT\tT\t0\t^cC00\t0\t0\t-\n<\/code><\/pre>\n\n\n\n<p>The fields and types are;<\/p>\n\n\n\n<pre class=\"scroll-box\"><code>\n#fields\nts\tuid\tid.orig_h\tid.orig_p\tid.resp_h\tid.resp_p\tproto\tservice\tduration\torig_bytes\tresp_bytes\tconn_state\tlocal_orig\tlocal_resp\tmissed_bytes\thistory\torig_pkts\torig_ip_bytes\tresp_pkts\tresp_ip_bytes\ttunnel_parents\n#types\ntime\tstring\taddr\tport\taddr\tport\tenum\tstring\tinterval\tcount\tcount\tstring\tbool\tbool\tcount\tstring\tcount\tcount\tcount\tcount\tset[string]\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Checking Zeek Node Processes<\/h4>\n\n\n\n<p>You can check processes running on each node by executing;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>zeekctl ps.zeek &lt;node&gt;<\/code><\/pre>\n\n\n\n<p>For example, to check processes on Zeek manager node;<\/p>\n\n\n\n<pre id=\"block-549cf091-8fdc-4abb-b81c-1d8846ea937e\" class=\"wp-block-preformatted\">zeekctl ps.zeek kifarunix-demo-zeek-manager <\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\n        USER         PID    PPID %CPU %MEM    VSZ   RSS TT       S  STARTED     TIME COMMAND\n>>> 192.168.59.16\n   (-) root       17911   17905  0.1  4.3 821252 88788 ?        S 03:52:41 00:00:02 zeek\n   (+) root       17962   17956  0.0  4.3 642664 89200 ?        S 03:52:43 00:00:01 zeek\n   (-) root       18011   18005  0.0  4.2 640972 87516 ?        S 03:52:45 00:00:01 zeek\n   (-) root       18081   18069  0.1 10.7 772672 219204 ?       S 03:52:47 00:00:03 zeek\n   (-) root       18082   18071  0.1 10.7 772148 218668 ?       S 03:52:47 00:00:03 zeek\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Reference<\/h3>\n\n\n\n<p><a aria-label=\"Zeek Quick Start Guide (opens in a new tab)\" href=\"https:\/\/docs.zeek.org\/en\/lts\/quickstart.html\" target=\"_blank\" rel=\"noreferrer noopener\" class=\"rank-math-link\">Installing Zee<\/a><a aria-label=\" (opens in a new tab)\" href=\"https:\/\/docs.zeek.org\/en\/lts\/install.html\" target=\"_blank\" rel=\"noreferrer noopener\" class=\"rank-math-link\">k<\/a><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Other Tutorials<\/h3>\n\n\n\n<p><a href=\"https:\/\/kifarunix.com\/install-and-configure-aide-on-debian-10\/\" target=\"_blank\" aria-label=\" (opens in a new tab)\" rel=\"noreferrer noopener\" class=\"rank-math-link\">Install and Configure AIDE on Debian 10<\/a><\/p>\n\n\n\n<p><a aria-label=\" (opens in a new tab)\" href=\"https:\/\/kifarunix.com\/install-modsecurity-3-with-apache-in-a-docker-container\/\" target=\"_blank\" rel=\"noreferrer noopener\" class=\"rank-math-link\">Install ModSecurity 3 with Apache in a Docker Container<\/a><\/p>\n\n\n\n<p><a aria-label=\" (opens in a new tab)\" href=\"https:\/\/kifarunix.com\/install-and-setup-suricata-on-ubuntu-18-04\/\" target=\"_blank\" rel=\"noreferrer noopener\" class=\"rank-math-link\">Install and Setup Suricata on Ubuntu 18.04<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Follow through this tutorial to learn how to install Zeek on Ubuntu 20.04. Zeek, formerly Bro IDS, is the world&#8217;s leading passive open source&nbsp;network security<\/p>\n","protected":false},"author":3,"featured_media":8852,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_lock_modified_date":false,"footnotes":""},"categories":[34,121],"tags":[3543,3544,3541,3545,3553,3547,252,3546,3542,3552,3548,3549,3550],"class_list":["post-8845","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-security","category-howtos","tag-install-bro-ids","tag-install-zeek-ids-linux","tag-install-zeek-ubuntu","tag-install-zeek-ubuntu-20-04","tag-logger","tag-nsm","tag-proxy","tag-security-monitoring","tag-ubuntu-20-04-install-zeek","tag-worker","tag-zeek-nsm","tag-zeekctl","tag-zeekctl-deploy","generate-columns","tablet-grid-50","mobile-grid-100","grid-parent","grid-50","resize-featured-image"],"_links":{"self":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/8845"}],"collection":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/comments?post=8845"}],"version-history":[{"count":11,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/8845\/revisions"}],"predecessor-version":[{"id":21811,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/8845\/revisions\/21811"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media\/8852"}],"wp:attachment":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media?parent=8845"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/categories?post=8845"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/tags?post=8845"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}