{"id":3212,"date":"2026-11-14T17:55:00","date_gmt":"2026-11-14T17:55:00","guid":{"rendered":"https:\/\/www.cancershospitals.com\/blog\/?p=3212"},"modified":"2026-11-15T11:55:00","modified_gmt":"2026-11-15T11:55:00","slug":"kubesecops-eight-risky-permissions","status":"publish","type":"post","link":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/","title":{"rendered":"Eight Risky Permissions Every KubernetesSecOps Review Should Catch"},"content":{"rendered":"<p>Access reviews in a large organisation usually start with a spreadsheet and end with an argument about which entries really matter. In a Kubernetes cluster the same argument happens over permission rules, and it is the centrepiece of KubernetesSecOps: deciding who may change the cluster and what that power implies. This list sets out eight permissions that look modest in a manifest but carry far more reach than their names suggest. The framing is analytical: for each item, what it lets someone do, why the effect is wider than expected, and what to check.<\/p>\n<p>The source for the grouping is the Ops Atlas, which catalogues risky grants in its coverage of the access layer; you can read the original in <a href=\"https:\/\/www.xopsschool.com\/kubernetessecops\/\">the KubernetesSecOps entry at the Ops Atlas<\/a>. The commentary and the ordering below are mine, and the scenarios are generic illustrations rather than reports from any real organisation.<\/p>\n<h2>First, why permissions deserve an audit<\/h2>\n<p>The permission system, called RBAC, reached general availability in 2017, so it is mature and widely used. Maturity breeds complacency. Roles accumulate, copies get made for one-off tasks and a role created &#8220;temporarily&#8221; is still there three years later. Because the access check is the first real gate after identity, and because read requests never pass beyond it, a mistake here is more costly than a mistake further down the chain.<\/p>\n<h2>Eight grants that deserve a second look<\/h2>\n<h3>1. Listing or watching secrets<\/h3>\n<p>Permission to list or watch secrets does not sound dramatic. In practice it returns the full content of every secret in scope, not just their names. Anybody holding it can read passwords, tokens and keys in bulk. Check which identities have it and whether it is really needed cluster-wide or only inside a single namespace.<\/p>\n<h3>2. Writing workloads<\/h3>\n<p>The ability to create or change a workload is an indirect route to almost everything else. A new pod can mount any secret in its namespace and can run under any service account in that namespace. Treat workload-write rights as equivalent to a bundle of the rights those workloads can reach.<\/p>\n<h3>3. Exec, attach and ephemeral containers<\/h3>\n<p>These let a person open a session inside a running container. From there they inherit whatever the container can see: mounted secrets, the service account token, network position. A wrinkle from the Atlas: up to release 1.35 the WebSocket flavour of exec asked only for &#8220;get&#8221; on the exec sub-resource, so a rule that looked read-only could still open a shell. Look for broad rules and for old assumptions about verbs.<\/p>\n<h3>4. Escalate, bind and impersonate<\/h3>\n<p>These three verbs let a holder grant themselves more access, attach more powerful roles to others or act as another identity. A role that carries them can undo any other control in the audit. They belong to a very short list of identities and should be absent from everyday roles.<\/p>\n<h3>5. Proxy access to nodes<\/h3>\n<p>The nodes proxy sub-resource gives a route to the machine-level agent that manages containers on each node. That agent has its own interface and its calls bypass the checks and logs that apply at the main API. A rule mentioning it deserves scrutiny out of proportion to its length.<\/p>\n<h3>6. Minting service-account tokens<\/h3>\n<p>If someone can create tokens for a service account, they can become that account whenever they like. Bound, time-limited tokens have been the default since release 1.22, which helps, but the permission to mint them is still a keys-to-the-room right.<\/p>\n<h3>7. Approving certificate requests<\/h3>\n<p>Certificate signing requests allow clients to obtain identity credentials. A role that can approve them can create credentials for identities that did not exist a minute ago. It is a quiet way to build a durable back door, so confirm that approval rights are held by automation you can name.<\/p>\n<h3>8. Editing admission webhook configurations and patching namespaces<\/h3>\n<p>Webhook configurations define the checkpoints for every request. Whoever can edit them can switch the checkpoint off or point it somewhere else. Namespace patch rights have a similar effect because labels on a namespace often decide which standards apply to it. Together they let someone shape the rules that are meant to constrain them.<\/p>\n<h2>Putting two of the grants together<\/h2>\n<p>The danger rarely comes from one item in isolation. Imagine a generic team role that is allowed to create workloads in its own namespace and to open sessions in running containers. Neither right looks alarming alone. Combined, a member can start a pod under a privileged service account that happens to live in that namespace, open a shell in it and then read whatever that account can read. The path never touches the word &#8220;secrets&#8221; in the role, yet it ends at the secrets.<\/p>\n<p>That is why the audit routine below asks for a sentence of justification per grant and why the Atlas points out that workload-write rights implicitly reach secrets and service accounts. Reading rules one line at a time hides the chains; sketching the chains on a whiteboard reveals them in an hour.<\/p>\n<p>A reasonable measure of progress is the number of such chains you can still draw. Start with a baseline count in the first round, repeat the whiteboard session after remediation, and expect the figure to fall. If it climbs instead, new roles are being created faster than they are reviewed, which is a process problem and not a technical one. Report the count to whoever owns the budget so the trend has a sponsor.<\/p>\n<h2>What the evidence says about doing this routinely<\/h2>\n<p>The Atlas recommends a review cadence for this layer: a full look at roles every quarter, with the benchmark check alongside, and a floor of no more than twenty-four months between reviews. It also cautions that scanner output alone is no proof of health, since scanners can ignore resource-name restrictions and miss permissions that arrive through operators. Treat a scan as a prompt for questions and not as a verdict.<\/p>\n<p>One extra rule is a hard one: nobody should be placed in the built-in system:masters group, because membership bypasses permission checks entirely. If someone in your inventory shows up there, treat it as an incident of configuration and fix it, not as a style choice.<\/p>\n<h2>A short audit routine<\/h2>\n<ol>\n<li>Export every role and binding, and label each by owner: a person, a team or an automation.<\/li>\n<li>Search the export for the eight patterns above and list every hit.<\/li>\n<li>Beside each hit, note in a line why the grant exists; when that line proves hard to write, flag the grant for removal.<\/li>\n<li>Replace cluster-wide grants with namespace-scoped ones wherever the work allows it.<\/li>\n<li>Attach a named owner and an expiry to every exception you keep, then calendar the expiry.<\/li>\n<li>Repeat the exercise on schedule and compare counts between rounds.<\/li>\n<\/ol>\n<h2>Reading the numbers without fooling yourself<\/h2>\n<p>An evidence-minded reviewer wants measurable output. Counts of risky grants per namespace, the proportion held by named automation rather than people, and the age of the oldest exception are all measurable and trend-friendly. Raw alert counts are less so. The Atlas gives a worked illustration where a monthly alert stream was mostly noise until expected activity by on-call staff was filtered out; actionable alerts then made up a far larger slice. The takeaway is to filter by cause before you judge the signal.<\/p>\n<h2>Related reading on this site<\/h2>\n<p>If your interest lies in the delivery side, the <a href=\"https:\/\/www.cancershospitals.com\/blog\/master-modern-software-delivery-the-complete-guide-to-devops-sre-and-cloud-native-engineering\/\">overview of software delivery with DevOps, SRE and cloud-native practice<\/a> gives context for where these permissions sit in daily engineering work. For readers who like the idea of external verification, the <a href=\"https:\/\/www.cancershospitals.com\/blog\/evaluating-cancer-hospitals-abroad-why-accreditation-counts\/\">article on accreditation when judging hospitals overseas<\/a> illustrates the same instinct that drives audits: ask for independent evidence rather than relying on self-description.<\/p>\n<p>Whichever route you take, begin with the first two items on the list. Secrets and workload writes cover the largest share of practical exposure, and fixing them shrinks the problem to a size a small team can manage in a quarter.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Eight Kubernetes permission grants that look harmless but reach far, with an evidence-minded audit routine for KubernetesSecOps reviewers.<\/p>\n","protected":false},"author":12,"featured_media":3213,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1171],"tags":[],"class_list":["post-3212","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-healthcare-it"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Eight Risky Permissions Every KubernetesSecOps Review Should Catch - Best Cancers Hospitals<\/title>\n<meta name=\"description\" content=\"Eight Kubernetes permissions that carry more reach than they seem, plus a six-step KubernetesSecOps audit routine and ways to measure progress.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Eight Risky Permissions Every KubernetesSecOps Review Should Catch - Best Cancers Hospitals\" \/>\n<meta property=\"og:description\" content=\"Eight Kubernetes permissions that carry more reach than they seem, plus a six-step KubernetesSecOps audit routine and ways to measure progress.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/\" \/>\n<meta property=\"og:site_name\" content=\"Best Cancers Hospitals\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-14T17:55:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-15T11:55:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.cancershospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1464771-banner.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Ananya Sharma\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ananya Sharma\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/kubesecops-eight-risky-permissions\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/kubesecops-eight-risky-permissions\\\/\"},\"author\":{\"name\":\"Ananya Sharma\",\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/#\\\/schema\\\/person\\\/ff1b0ec6e90a997ae9dab530a024a0d2\"},\"headline\":\"Eight Risky Permissions Every KubernetesSecOps Review Should Catch\",\"datePublished\":\"2026-11-14T17:55:00+00:00\",\"dateModified\":\"2026-11-15T11:55:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/kubesecops-eight-risky-permissions\\\/\"},\"wordCount\":1319,\"image\":{\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/kubesecops-eight-risky-permissions\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1464771-banner.png\",\"articleSection\":[\"Healthcare IT\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/kubesecops-eight-risky-permissions\\\/\",\"url\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/kubesecops-eight-risky-permissions\\\/\",\"name\":\"Eight Risky Permissions Every KubernetesSecOps Review Should Catch - Best Cancers Hospitals\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/kubesecops-eight-risky-permissions\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/kubesecops-eight-risky-permissions\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1464771-banner.png\",\"datePublished\":\"2026-11-14T17:55:00+00:00\",\"dateModified\":\"2026-11-15T11:55:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/#\\\/schema\\\/person\\\/ff1b0ec6e90a997ae9dab530a024a0d2\"},\"description\":\"Eight Kubernetes permissions that carry more reach than they seem, plus a six-step KubernetesSecOps audit routine and ways to measure progress.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/kubesecops-eight-risky-permissions\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/kubesecops-eight-risky-permissions\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/kubesecops-eight-risky-permissions\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1464771-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1464771-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/kubesecops-eight-risky-permissions\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Eight Risky Permissions Every KubernetesSecOps Review Should Catch\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/\",\"name\":\"My blog\",\"description\":\"Your Global Guide to the Best Cancer Hospitals and Life-Saving Treatments\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/#\\\/schema\\\/person\\\/ff1b0ec6e90a997ae9dab530a024a0d2\",\"name\":\"Ananya Sharma\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/df4b733d0a431808cb5983ad62a4aeae33ccdb603a9d795b36beab1c5461249a?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/df4b733d0a431808cb5983ad62a4aeae33ccdb603a9d795b36beab1c5461249a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/df4b733d0a431808cb5983ad62a4aeae33ccdb603a9d795b36beab1c5461249a?s=96&d=mm&r=g\",\"caption\":\"Ananya Sharma\"},\"url\":\"https:\\\/\\\/www.cancershospitals.com\\\/blog\\\/author\\\/ananya-sharma\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Eight Risky Permissions Every KubernetesSecOps Review Should Catch - Best Cancers Hospitals","description":"Eight Kubernetes permissions that carry more reach than they seem, plus a six-step KubernetesSecOps audit routine and ways to measure progress.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/","og_locale":"en_US","og_type":"article","og_title":"Eight Risky Permissions Every KubernetesSecOps Review Should Catch - Best Cancers Hospitals","og_description":"Eight Kubernetes permissions that carry more reach than they seem, plus a six-step KubernetesSecOps audit routine and ways to measure progress.","og_url":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/","og_site_name":"Best Cancers Hospitals","article_published_time":"2026-11-14T17:55:00+00:00","article_modified_time":"2026-11-15T11:55:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.cancershospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1464771-banner.png","type":"image\/png"}],"author":"Ananya Sharma","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ananya Sharma","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/#article","isPartOf":{"@id":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/"},"author":{"name":"Ananya Sharma","@id":"https:\/\/www.cancershospitals.com\/blog\/#\/schema\/person\/ff1b0ec6e90a997ae9dab530a024a0d2"},"headline":"Eight Risky Permissions Every KubernetesSecOps Review Should Catch","datePublished":"2026-11-14T17:55:00+00:00","dateModified":"2026-11-15T11:55:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/"},"wordCount":1319,"image":{"@id":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cancershospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1464771-banner.png","articleSection":["Healthcare IT"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/","url":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/","name":"Eight Risky Permissions Every KubernetesSecOps Review Should Catch - Best Cancers Hospitals","isPartOf":{"@id":"https:\/\/www.cancershospitals.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/#primaryimage"},"image":{"@id":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cancershospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1464771-banner.png","datePublished":"2026-11-14T17:55:00+00:00","dateModified":"2026-11-15T11:55:00+00:00","author":{"@id":"https:\/\/www.cancershospitals.com\/blog\/#\/schema\/person\/ff1b0ec6e90a997ae9dab530a024a0d2"},"description":"Eight Kubernetes permissions that carry more reach than they seem, plus a six-step KubernetesSecOps audit routine and ways to measure progress.","breadcrumb":{"@id":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/#primaryimage","url":"https:\/\/www.cancershospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1464771-banner.png","contentUrl":"https:\/\/www.cancershospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1464771-banner.png","width":1200,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/www.cancershospitals.com\/blog\/kubesecops-eight-risky-permissions\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.cancershospitals.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Eight Risky Permissions Every KubernetesSecOps Review Should Catch"}]},{"@type":"WebSite","@id":"https:\/\/www.cancershospitals.com\/blog\/#website","url":"https:\/\/www.cancershospitals.com\/blog\/","name":"My blog","description":"Your Global Guide to the Best Cancer Hospitals and Life-Saving Treatments","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.cancershospitals.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.cancershospitals.com\/blog\/#\/schema\/person\/ff1b0ec6e90a997ae9dab530a024a0d2","name":"Ananya Sharma","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/df4b733d0a431808cb5983ad62a4aeae33ccdb603a9d795b36beab1c5461249a?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/df4b733d0a431808cb5983ad62a4aeae33ccdb603a9d795b36beab1c5461249a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/df4b733d0a431808cb5983ad62a4aeae33ccdb603a9d795b36beab1c5461249a?s=96&d=mm&r=g","caption":"Ananya Sharma"},"url":"https:\/\/www.cancershospitals.com\/blog\/author\/ananya-sharma\/"}]}},"_links":{"self":[{"href":"https:\/\/www.cancershospitals.com\/blog\/wp-json\/wp\/v2\/posts\/3212","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cancershospitals.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cancershospitals.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cancershospitals.com\/blog\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cancershospitals.com\/blog\/wp-json\/wp\/v2\/comments?post=3212"}],"version-history":[{"count":1,"href":"https:\/\/www.cancershospitals.com\/blog\/wp-json\/wp\/v2\/posts\/3212\/revisions"}],"predecessor-version":[{"id":3328,"href":"https:\/\/www.cancershospitals.com\/blog\/wp-json\/wp\/v2\/posts\/3212\/revisions\/3328"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cancershospitals.com\/blog\/wp-json\/wp\/v2\/media\/3213"}],"wp:attachment":[{"href":"https:\/\/www.cancershospitals.com\/blog\/wp-json\/wp\/v2\/media?parent=3212"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cancershospitals.com\/blog\/wp-json\/wp\/v2\/categories?post=3212"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cancershospitals.com\/blog\/wp-json\/wp\/v2\/tags?post=3212"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}