{"id":1951,"date":"2026-06-19T16:06:09","date_gmt":"2026-06-19T10:36:09","guid":{"rendered":"https:\/\/adilfahim.com\/myblog\/sap-systems-running-on-rise-7-things-basis-teams\/"},"modified":"2026-06-19T16:23:14","modified_gmt":"2026-06-19T10:53:14","slug":"sap-systems-running-on-rise-7-things-basis-teams","status":"publish","type":"post","link":"https:\/\/adilfahim.com\/myblog\/sap-systems-running-on-rise-7-things-basis-teams\/","title":{"rendered":"7 Things SAP Basis Teams Must Know About Systems Running on RISE with SAP"},"content":{"rendered":"<p>If your organization is running \u2014 or planning to run \u2014 SAP systems on RISE with SAP, you&#8217;ve probably noticed something: the narrative from SAP makes it sound like Basis teams can kick back and relax. &#8220;SAP handles the infrastructure, the patching, the operations&#8230;&#8221; But anyone who&#8217;s actually worked with RISE knows the reality is more nuanced.<\/p>\n<p><em>Full disclosure: RISE with SAP is essentially HEC (HANA Enterprise Cloud) on hyperscaler infrastructure (Azure, AWS, GCP), wrapped in a new commercial and operating model. The core ECS (Enterprise Cloud Services) engine hasn&#8217;t fundamentally changed \u2014 but your responsibilities have.<\/em><\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_85 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<label for=\"ez-toc-cssicon-toggle-item-6a354f743c02e\" class=\"ez-toc-cssicon-toggle-label\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/label><input type=\"checkbox\"  id=\"ez-toc-cssicon-toggle-item-6a354f743c02e\"  aria-label=\"Toggle\" \/><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/adilfahim.com\/myblog\/sap-systems-running-on-rise-7-things-basis-teams\/#1_SAP_Still_Manages_the_Infrastructure_%E2%80%94_But_Your_Basis_Team_Stays_Busy\" >1. SAP Still Manages the Infrastructure \u2014 But Your Basis Team Stays Busy<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/adilfahim.com\/myblog\/sap-systems-running-on-rise-7-things-basis-teams\/#2_The_OSS_Notes_Library_Is_Your_Survival_Guide\" >2. The OSS Notes Library Is Your Survival Guide<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/adilfahim.com\/myblog\/sap-systems-running-on-rise-7-things-basis-teams\/#3_The_RACI_Triangle_Customer_SAP_Partner_%E2%80%94_You_Need_All_Three\" >3. The RACI Triangle: Customer, SAP, Partner \u2014 You Need All Three<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/adilfahim.com\/myblog\/sap-systems-running-on-rise-7-things-basis-teams\/#4_Security_Doesnt_Get_Easier_%E2%80%94_It_Gets_Different\" >4. Security Doesn&#8217;t Get Easier \u2014 It Gets Different<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/adilfahim.com\/myblog\/sap-systems-running-on-rise-7-things-basis-teams\/#5_Transports_and_System_Copies_Still_Run_Through_Your_Team\" >5. Transports and System Copies Still Run Through Your Team<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/adilfahim.com\/myblog\/sap-systems-running-on-rise-7-things-basis-teams\/#6_Backup_Monitoring_and_Incident_Response_Require_New_Processes\" >6. Backup, Monitoring, and Incident Response Require New Processes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/adilfahim.com\/myblog\/sap-systems-running-on-rise-7-things-basis-teams\/#7_Your_Career_Path_Expands_%E2%80%94_Not_Contracts\" >7. Your Career Path Expands \u2014 Not Contracts<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/adilfahim.com\/myblog\/sap-systems-running-on-rise-7-things-basis-teams\/#Conclusion_Know_What_Youre_Signing_Up_For\" >Conclusion: Know What You&#8217;re Signing Up For<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"1_SAP_Still_Manages_the_Infrastructure_%E2%80%94_But_Your_Basis_Team_Stays_Busy\"><\/span>1. SAP Still Manages the Infrastructure \u2014 But Your Basis Team Stays Busy<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Let&#8217;s clear up the biggest misconception first. Yes, under RISE, SAP takes responsibility for OS patching, database management, backup and recovery, and system-level monitoring. But that doesn&#8217;t mean your Basis team has nothing to do.<\/p>\n<p>As the <a href=\"https:\/\/www.legupsoftware.com\/expert_insights\/sap-rise-is-there-a-role-for-a-customers-basis-team\" target=\"_blank\" rel=\"noopener\">RISE Roles and Responsibilities document<\/a> makes clear, customers retain responsibility for:<\/p>\n<ul>\n<li>Transport management and RFC management<\/li>\n<li>User role administration and authorization<\/li>\n<li>System monitoring, memory management, sizing, and capacity planning<\/li>\n<li>Pre- and post-refresh activities<\/li>\n<li>Testing and validation of all patches (even SAP-applied ones)<\/li>\n<li>All non-critical security patching (CVSS below 8)<\/li>\n<\/ul>\n<p>In fact, many experienced Basis teams report spending significant time coordinating with \u2014 and sometimes guiding \u2014 the junior RISE Basis engineers assigned to their account by the MSPs SAP contracts with. Your internal expertise doesn&#8217;t become obsolete. It becomes more strategic.<\/p>\n<p>As I covered in my earlier post about <a href=\"https:\/\/adilfahim.com\/myblog\/rise-with-sap-and-sap-basis-consultant\/\" target=\"_blank\">RISE with SAP and the Evolution of the SAP BASIS Consultant<\/a>, this shift from &#8220;doing&#8221; to &#8220;orchestrating&#8221; is the single biggest change for Basis teams moving to RISE.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"2_The_OSS_Notes_Library_Is_Your_Survival_Guide\"><\/span>2. The OSS Notes Library Is Your Survival Guide<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>One of the most valuable resources for managing <strong>SAP systems on RISE with SAP<\/strong> is the comprehensive collection of OSS notes maintained by SAP&#8217;s ECS team. These aren&#8217;t optional reading \u2014 they&#8217;re the operational manual for your RISE environment.<\/p>\n<p>Here are the ones you absolutely need to bookmark:<\/p>\n<table border=\"1\" cellpadding=\"6\" style=\"border-collapse:collapse;width:100%;font-size:14px;\">\n<tr style=\"background:#0f172a;color:#fff;\">\n<th>OSS Note<\/th>\n<th>What It Covers<\/th>\n<th>Priority<\/th>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/me.sap.com\/notes\/3344326\/E\" target=\"_blank\" rel=\"noopener\">3344326<\/a><\/td>\n<td>FAQ: Private Cloud Landscape (ECS Landscape)<\/td>\n<td>\u2b50 Critical<\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/me.sap.com\/notes\/3351928\/E\" target=\"_blank\" rel=\"noopener\">3351928<\/a><\/td>\n<td>FAQ: ECS ABAP System User Management<\/td>\n<td>\u2b50 Critical<\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/me.sap.com\/notes\/3250501\/E\" target=\"_blank\" rel=\"noopener\">3250501<\/a><\/td>\n<td>Mandatory Security Parameters for ABAP Systems in ECS<\/td>\n<td>\u2b50 Critical<\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/me.sap.com\/notes\/3480723\/E\" target=\"_blank\" rel=\"noopener\">3480723<\/a><\/td>\n<td>Security Parameters for HANA Databases in ECS<\/td>\n<td>\u2b50 Critical<\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/me.sap.com\/notes\/3572444\/E\" target=\"_blank\" rel=\"noopener\">3572444<\/a><\/td>\n<td>Standard Backup Policy for RISE Production Systems<\/td>\n<td>\ud83d\udd25 High<\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/me.sap.com\/notes\/2597323\" target=\"_blank\" rel=\"noopener\">2597323<\/a><\/td>\n<td>Transport Directory Between RISE and On-Premise TMS<\/td>\n<td>\ud83d\udd25 High<\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/me.sap.com\/notes\/3441135\/E\" target=\"_blank\" rel=\"noopener\">3441135<\/a><\/td>\n<td>System Copy Service Request Handling for ECS<\/td>\n<td>\ud83d\udd25 High<\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/me.sap.com\/notes\/3286240\" target=\"_blank\" rel=\"noopener\">3286240<\/a><\/td>\n<td>Client Administrative Actions Restrictions<\/td>\n<td>\ud83d\udd25 High<\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/me.sap.com\/notes\/3517086\/E\" target=\"_blank\" rel=\"noopener\">3517086<\/a><\/td>\n<td>Non-Security Parameters for ABAP in ECS<\/td>\n<td>\ud83d\udccb Medium<\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/me.sap.com\/notes\/3336611\" target=\"_blank\" rel=\"noopener\">3336611<\/a><\/td>\n<td>Standard Service Ports in ECS<\/td>\n<td>\ud83d\udccb Medium<\/td>\n<\/tr>\n<\/table>\n<p>I recommend creating a dedicated folder in your SAP Notes viewer and subscribing to updates on these notes \u2014 especially the security ones (3250501, 3480723) which get updated regularly as SAP&#8217;s baseline evolves.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"3_The_RACI_Triangle_Customer_SAP_Partner_%E2%80%94_You_Need_All_Three\"><\/span>3. The RACI Triangle: Customer, SAP, Partner \u2014 You Need All Three<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>One of the most common failure points in RISE engagements is unclear ownership. The operating model creates a three-way accountability structure that works brilliantly when everyone knows their lane, and falls apart when they don&#8217;t.<\/p>\n<p><strong>The RACI breakdown for SAP systems on RISE with SAP:<\/strong><\/p>\n<ul>\n<li><strong>SAP<\/strong> is Accountable for the platform \u2014 infrastructure, uptime, managed services, and the software baseline.<\/li>\n<li><strong>The Implementation Partner<\/strong> is Responsible for configuration, customization, data migration, and project delivery.<\/li>\n<li><strong>The Customer (Your Team)<\/strong> is Accountable for business outcomes \u2014 process decisions, user adoption, organizational readiness, and ongoing governance.<\/li>\n<\/ul>\n<p>This means your Basis team needs to operate as a <strong>cloud service manager<\/strong>, not a server administrator. You&#8217;re no longer patching the OS \u2014 but you&#8217;re accountable for ensuring the patches don&#8217;t break your critical business processes. You&#8217;re not managing the HANA database daily \u2014 but you own the performance governance and capacity planning.<\/p>\n<p>As we discussed in the <a href=\"https:\/\/adilfahim.com\/myblog\/from-sap-basis-to-cloud-architect-is-it-time-to-make-the-switch\/\" target=\"_blank\">transition from SAP BASIS to Cloud Architect<\/a>, this shift requires a fundamentally different mindset \u2014 one focused on orchestration, governance, and vendor management rather than hands-on technical execution.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"4_Security_Doesnt_Get_Easier_%E2%80%94_It_Gets_Different\"><\/span>4. Security Doesn&#8217;t Get Easier \u2014 It Gets Different<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Here&#8217;s a hard truth: moving to RISE doesn&#8217;t make your SAP security posture simpler. It changes the threat model and shifts where you need to focus.<\/p>\n<p>SAP&#8217;s ECS team applies a defined security baseline \u2014 documented in OSS notes 3250501 (ABAP) and 3480723 (HANA). But the customer remains responsible for:<\/p>\n<ul>\n<li>User administration and role design across the landscape<\/li>\n<li>Segregation of duties and GRC compliance<\/li>\n<li>Application-level security (authorizations, critical transactions)<\/li>\n<li>Secure configuration of interfaces and integrations<\/li>\n<li>Managing security for BTP extensions and side-by-side scenarios<\/li>\n<li>Ensuring compliance with your organization&#8217;s audit requirements<\/li>\n<\/ul>\n<p>SAP applies critical security patches automatically, but only those that can be applied without manual intervention. Everything else \u2014 testing, non-critical patches, additional remediation \u2014 falls to your team.<\/p>\n<p>This is why I included security as a major pillar in my <a href=\"https:\/\/adilfahim.com\/myblog\/sap-security-audit-checklist\/\" target=\"_blank\">SAP Security Audit Checklist: Complete Guide for BASIS Administrators<\/a>. The fundamentals haven&#8217;t changed \u2014 you still need a robust security framework. What&#8217;s changed is <em>how<\/em> you implement it within the RISE boundaries.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"5_Transports_and_System_Copies_Still_Run_Through_Your_Team\"><\/span>5. Transports and System Copies Still Run Through Your Team<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>One of the biggest surprises for teams migrating to <strong>SAP systems on RISE with SAP<\/strong> is discovering that transport management doesn&#8217;t get handed over to SAP. Your Basis team still owns the transport chain \u2014 it just works differently now.<\/p>\n<p>Key OSS note <a href=\"https:\/\/me.sap.com\/notes\/2597323\" target=\"_blank\" rel=\"noopener\">2597323<\/a> covers transport directory setup between RISE and on-premise TMS landscapes. And note <a href=\"https:\/\/me.sap.com\/notes\/3441135\/E\" target=\"_blank\" rel=\"noopener\">3441135<\/a> details the system copy service request process \u2014 you submit a ticket to ECS, they handle the database copy, but your team handles all pre- and post-copy activities.<\/p>\n<p>Similarly, client administration is restricted in ECS-managed systems (note <a href=\"https:\/\/me.sap.com\/notes\/3286240\" target=\"_blank\" rel=\"noopener\">3286240<\/a>). You can&#8217;t just create or delete clients at will. Understanding these limitations before you need them will save you a lot of frustrated ticket exchanges with SAP support.<\/p>\n<p>For a deeper comparison of operational tools, check out my analysis of <a href=\"https:\/\/adilfahim.com\/myblog\/sap-cloud-alm-vs-solution-manager-5-critical-functions-for-sap-it-team\/\" target=\"_blank\">SAP Cloud ALM vs Solution Manager: 5 Critical Functions<\/a> \u2014 because Cloud ALM is the operations backbone for RISE environments.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"6_Backup_Monitoring_and_Incident_Response_Require_New_Processes\"><\/span>6. Backup, Monitoring, and Incident Response Require New Processes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Under RISE, SAP handles the standard backup policy (documented in OSS note <a href=\"https:\/\/me.sap.com\/notes\/3572444\/E\" target=\"_blank\" rel=\"noopener\">3572444<\/a>), but you still need to:<\/p>\n<ul>\n<li>Understand the recovery point and time objectives (RPO\/RTO) in your contract<\/li>\n<li>Test backups by requesting system refreshes through the ECS service request process<\/li>\n<li>Monitor application-level health \u2014 SAP monitors the infrastructure, but you monitor the business processes<\/li>\n<li>Define escalation paths for incidents that cross the boundary between your application and SAP&#8217;s managed layer<\/li>\n<\/ul>\n<p>The incident management process also changes. You don&#8217;t SSH into the server anymore \u2014 you open a service request through SAP&#8217;s ECS portal (see note <a href=\"https:\/\/me.sap.com\/notes\/3399927\/E\" target=\"_blank\" rel=\"noopener\">3399927<\/a> for how to create cases). This means your troubleshooting skills need to shift from &#8220;fix it yourself&#8221; to &#8220;diagnose and describe accurately so SAP can fix it.&#8221;<\/p>\n<p>For monitoring specifically, <a href=\"https:\/\/adilfahim.com\/myblog\/sap-cloud-alm\/\" target=\"_blank\">SAP Cloud ALM<\/a> is the recommended platform, and note <a href=\"https:\/\/me.sap.com\/notes\/3576114\/E\" target=\"_blank\" rel=\"noopener\">3576114<\/a> covers a common issue \u2014 no systems showing in the RISE System View. Bookmark that one.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"7_Your_Career_Path_Expands_%E2%80%94_Not_Contracts\"><\/span>7. Your Career Path Expands \u2014 Not Contracts<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>I hear this concern all the time from Basis colleagues: &#8220;If SAP handles the infrastructure, what&#8217;s left for me?&#8221;<\/p>\n<p>The answer, based on real experience from teams already in RISE: <strong>more than you think, and at a higher level.<\/strong><\/p>\n<p>As <strong>SAP systems on RISE with SAP<\/strong> become the norm, Basis professionals are evolving into:<\/p>\n<ul>\n<li><strong>Cloud Platform Administrators<\/strong> \u2014 managing BTP subaccounts, entitlements, and connectivity<\/li>\n<li><strong>Integration Architects<\/strong> \u2014 designing and governing the extension landscape<\/li>\n<li><strong>Security and Compliance Managers<\/strong> \u2014 owning the application-layer security posture<\/li>\n<li><strong>Vendor and Service Managers<\/strong> \u2014 coordinating SAP, hyperscalers, and internal teams<\/li>\n<li><strong>Automation Engineers<\/strong> \u2014 building Terraform pipelines, Automation Pilot workflows, and CI\/CD processes<\/li>\n<\/ul>\n<p>This aligns with what we explored in the <a href=\"https:\/\/adilfahim.com\/myblog\/sap-basis-to-cloud-platform-administrator-roadmap\/\" target=\"_blank\">4-Tier Roadmap: From SAP Basis Admin to Cloud Platform Administrator<\/a>. The trajectory is clear \u2014 from system guardian to platform orchestrator.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Conclusion_Know_What_Youre_Signing_Up_For\"><\/span>Conclusion: Know What You&#8217;re Signing Up For<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The biggest risk with <strong>SAP systems on RISE with SAP<\/strong> isn&#8217;t technical \u2014 it&#8217;s assuming that &#8220;managed by SAP&#8221; means &#8220;managed for you.&#8221; Your Basis team remains critical to the success of a RISE engagement. What changes is <em>what<\/em> you manage and <em>how<\/em> you manage it.<\/p>\n<p>Start by bookmarking those OSS notes. Review the RACI boundaries with your team. And invest in the skills \u2014 cloud platform management, automation, security governance \u2014 that turn a RISE transition from a threat to your role into the biggest career opportunity in SAP right now.<\/p>\n<p><em>What&#8217;s been your experience with SAP systems on RISE? Drop a comment below or connect with me to share your story.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>SAP systems running on RISE with SAP require Basis teams to shift from infrastructure maintenance to strategic oversight. Here are 7 things every Basis admin must know.<\/p>\n","protected":false},"author":1,"featured_media":1954,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1241,1238],"tags":[1280,1279,1283,1282,1286,1284,1281,1285,1278],"class_list":["post-1951","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sap-basis","category-sap-cloud","tag-ecs-oss-notes-sap","tag-rise-with-sap-basis","tag-sap-basis-cloud-transformation","tag-sap-basis-rise-migration","tag-sap-cloud-platform-administration","tag-sap-ecs-security-parameters","tag-sap-rise-operations","tag-sap-rise-responsibilities","tag-sap-systems-on-rise-with-sap"],"_links":{"self":[{"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/posts\/1951","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/comments?post=1951"}],"version-history":[{"count":2,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/posts\/1951\/revisions"}],"predecessor-version":[{"id":1953,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/posts\/1951\/revisions\/1953"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/media\/1954"}],"wp:attachment":[{"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/media?parent=1951"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/categories?post=1951"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/tags?post=1951"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}