bodyType

customContents

entityId

printArticlePageQuery

filter

article

body

urlAlias

articleSectionsContent

articleSeoArticle

articleSourceHeaderArticle

contentSchemaRenderContent

contentSubHeadlineContent

contentHeadlineContent

mainImagePrintArticleArticle

authorBlockPrintArticleArticle

contentSponsorTagContent

articlePianoPaywallContent

scmpYoutubeContent

hooksTrackPageViewArticle

query printArticlePageQuery(
  $entityId: String!
  $customContents: [CustomContentInput]
  $bodyType: BodyFormatTypeEnum
) {
  article(filter: {entityId: $entityId}) {
    entityId
    body(customContents: $customContents, type: $bodyType) {
      json
    }
    urlAlias
    ...articleSectionsContent
    ...articleSeoArticle_3o8td4
    ...articleSourceHeaderArticle
    ...contentSchemaRenderContent
    ...contentSubHeadlineContent
    ...contentHeadlineContent
    ...mainImagePrintArticleArticle
    ...authorBlockPrintArticleArticle
    ...contentSponsorTagContent
    ...articlePianoPaywallContent
    ...scmpYoutubeContent
    ...hooksTrackPageViewArticle
    id
  }
}

fragment articlePianoPaywallContent on Content {
  __isContent: __typename
  ...hooksPaywallPromiseContent
}

fragment articleSectionsContent on Content {
  __isContent: __typename
  sections {
    value {
      ...helpersCheckIfNewsSectionInFirstIndexSection
      ...entityLink
      name
      id
    }
  }
}

fragment articleSeoArticle_3o8td4 on Article {
  ...hooksArticleSeoArticle
  ...helpersCheckIsPostiesArticle
  ...helpersGetArticleTypeArticle
  entityId
  publishedDate
  updatedDate
  summary {
    text
  }
  subHeadline {
    text
  }
  body(customContents: $customContents, type: $bodyType) {
    text
  }
  keywords
  sections {
    value {
      name
      id
    }
  }
  topics {
    name
    entityId
    id
  }
  urlAlias
  authors {
    name
    id
  }
  images {
    style(filter: {style: "768x768"}) {
      url
    }
  }
  readingTime
}

fragment articleSourceHeaderArticle on Article {
  urlAlias
  ...entityLink
}

fragment authorBlockPrintArticleArticle on Article {
  ...defaultArticleDateContent
  ...authorNamesArticle
}

fragment authorNameAuthor on Author {
  ...entityLink
  name
  entityUuid
}

fragment authorNamesArticle on Article {
  authorLocations
  authors {
    entityId
    location
    ...authorNameAuthor
    id
  }
}

fragment blockquoteQuoteContent on Content {
  __isContent: __typename
  ...contentShareWidgetContent
}

fragment checkersCheckContentContainsStarlingImageContent on Content {
  __isContent: __typename
  topics {
    entityId
    id
  }
}

fragment contentHeadlineContent on Content {
  __isContent: __typename
  headline
  socialHeadline
  ...contentHeadlineTagContent
  ...helpersUseContentSponsorContent
}

fragment contentHeadlineTagContent on Content {
  __isContent: __typename
  ...hooksContentHeadlineTagContent
}

fragment contentNewsletterWidgetContent on Content {
  __isContent: __typename
  topics {
    relatedNewsletters {
      ...helpersMassageToNewsletterItemNewsletter
      id
    }
    id
  }
  sections {
    value {
      relatedNewsletters {
        ...helpersMassageToNewsletterItemNewsletter
        id
      }
      id
    }
  }
  ... on Article {
    relatedNewsletters {
      ...helpersMassageToNewsletterItemNewsletter
      id
    }
  }
}

fragment contentSchemaRenderContent on Content {
  __isContent: __typename
  ...blockquoteQuoteContent
  ...imageContent
  ...inlineWidgetContent
  ...photoGalleryWidgetContent
  ...scmpYoutubeContent
}

fragment contentShareWidgetContent on Content {
  __isContent: __typename
  entityId
  urlAlias
  shortUrl
  socialHeadline
  headline
}

fragment contentSponsorTagContent on Content {
  __isContent: __typename
  ...helpersUseContentSponsorContent
}

fragment contentSubHeadlineContent on Content {
  __isContent: __typename
  subHeadline {
    json
  }
  summary {
    json
  }
  ...contentSchemaRenderContent
}

fragment defaultArticleDateContent on Content {
  __isContent: __typename
  ...hooksArticleDateUtilsContent
}

fragment entityLink on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  __typename
  entityId
  entityUuid
  urlAlias
  urlRedirect {
    toUrl
    id
  }
  application {
    entityId
    id
  }
  ... on Section {
    fullSectionPath {
      entityId
      id
    }
    parentSection
  }
  ...helpersAppBarVariantBase
  ...helpersApplicationBase
  ...helpersCheckIsPlusArticle
  ...helpersStyleSectionContent
}

fragment helpersAppBarVariantBase on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  ...helpersCheckIsLiveArticle
  ...helpersCheckIsPlusPage
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostiesPage
  ...helpersCheckIsPostMagazineArticle
  ...helpersCheckIsStyleArticle
  ...helpersSectionContent
  ...helpersStyleSectionContent
}

fragment helpersApplicationBase on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostiesPage
  ...helpersCheckIsPlusPage
}

fragment helpersCheckIfNewsSectionInFirstIndexSection on Section {
  name
}

fragment helpersCheckIsAmpEnabledArticle on Article {
  entityId
  types {
    value {
      entityId
      id
    }
  }
  sections {
    value {
      entityId
      id
    }
  }
  disableOffPlatformContent
  sponsorType
  published
  ...helpersCheckIsPlusArticle
  ...helpersCheckIsPostiesArticle
}

fragment helpersCheckIsLiveArticle on Article {
  flattenTypeIds
  liveArticle {
    status
    id
  }
}

fragment helpersCheckIsMainTopicContent on Content {
  __isContent: __typename
  topics {
    entityId
    id
  }
}

fragment helpersCheckIsPlusArticle on Content {
  __isContent: __typename
  ... on Article {
    paywallTypes {
      entityUuid
      id
    }
  }
}

fragment helpersCheckIsPlusPage on Page {
  urlAlias
}

fragment helpersCheckIsPostMagazineArticle on Article {
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersCheckIsPostiesArticle on Article {
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersCheckIsPostiesPage on Page {
  urlAlias
}

fragment helpersCheckIsStyleArticle on Content {
  __isContent: __typename
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersGetArticleTypeArticle on Content {
  __isContent: __typename
  ... on Article {
    types {
      value {
        entityId
        id
      }
    }
  }
}

fragment helpersMassageToNewsletterItemNewsletter on Newsletter {
  entityId
  name
  alternativeName
  description {
    text
  }
  summary {
    text
  }
  homepageDescription {
    text
  }
}

fragment helpersSanitizeArticleTypeEntityIdsArticle on Article {
  types {
    value {
      entityId
      id
    }
  }
}

fragment helpersSanitizeAuthorTypesArticle on Article {
  authors {
    types
    id
  }
}

fragment helpersSanitizedAuthorEntityIdsArticle on Article {
  authors {
    entityId
    id
  }
}

fragment helpersSectionContent on Section {
  fullSectionPath {
    entityId
    id
  }
}

fragment helpersStyleSectionContent on Section {
  fullSectionPath {
    entityId
    id
  }
}

fragment helpersUseContentSponsorContent on Content {
  __isContent: __typename
  topics {
    entityId
    sponsor {
      ...sponsorTagSponsor
      name
      type
      id
    }
    id
  }
  ... on Article {
    sponsorType
  }
  ...helpersCheckIsMainTopicContent
}

fragment hooksArticleDateUtilsContent on Content {
  __isContent: __typename
  createdDate
  publishedDate
  updatedDate
}

fragment hooksArticleSeoArticle on Article {
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostMagazineArticle
  ...helpersCheckIsStyleArticle
  ...hooksContentHeadlineTagContent
  ...helpersCheckIsAmpEnabledArticle
  entityId
  headline
  socialHeadline
  types {
    value {
      entityId
      id
    }
  }
  authors {
    entityId
    id
  }
  images {
    generic_og: style(filter: {style: "og_image_scmp_generic"}) {
      url
    }
    styles(filter: {styles: ["og_image_posties_article", "og_postmag", "og_image_style", "og_image_scmp_analysis", "og_image_scmp_explainer", "og_image_scmp_editorial", "og_image_scmp_fact_check", "og_image_scmp_debate", "og_image_scmp_live", "og_image_scmp_obituary", "og_image_scmp_opinion", "og_image_scmp_review", "og_image_scmp_series", "og_image_scmp_generic"]}) {
      url
      style
    }
    type
  }
  urlAlias
}

fragment hooksContentHeadlineTagContent on Content {
  __isContent: __typename
  __typename
  ... on Article {
    types {
      value {
        name
        entityId
        description {
          text
        }
        id
      }
    }
    ...helpersCheckIsStyleArticle
  }
  flag
  sections {
    value {
      name
      id
    }
  }
  ...hooksContentHelperContent
}

fragment hooksContentHelperContent on Content {
  __isContent: __typename
  ...helpersSanitizeArticleTypeEntityIdsArticle
  ...helpersSanitizeAuthorTypesArticle
  ...helpersSanitizedAuthorEntityIdsArticle
  flag
}

fragment hooksPaywallPromiseContent on Content {
  __isContent: __typename
  entityId
  ...helpersCheckIsPostiesArticle
}

fragment hooksTrackPageViewArticle on Article {
  entityId
  publishedDate
  headline
  sections {
    value {
      name
      id
    }
  }
  urlAlias
  authors {
    name
    id
  }
  entityUuid
}

fragment imageContent on Content {
  __isContent: __typename
  headline
  ...checkersCheckContentContainsStarlingImageContent
}

fragment inlineWidgetContent on Content {
  __isContent: __typename
  ...contentNewsletterWidgetContent
}

fragment mainImagePrintArticleArticle on Article {
  images {
    title
    url
    isSlideshow
    size_652x446: style(filter: {style: "652x446"}) {
      url
    }
  }
}

fragment photoGalleryDialogContent on Content {
  __isContent: __typename
  __typename
  ...contentShareWidgetContent
}

fragment photoGalleryWidgetContent on Content {
  __isContent: __typename
  ...photoGalleryDialogContent
}

fragment scmpYoutubeContent on Content {
  __isContent: __typename
  entityId
  urlAlias
  publishedDate
}

fragment sponsorTagSponsor on Sponsor {
  name
  type
  images {
    url
  }
}


sections

types

disableOffPlatformContent

sponsorType

published

headline

socialHeadline

authors

images

publishedDate

updatedDate

summary

subHeadline

keywords

topics

readingTime

authorLocations

entityUuid

Coco Feng

After having its apps removed from app stores and being sued by shareholders in the US, Didi’s cybersecurity review is finally getting under way. A task force of seven Chinese ministries entered the company’s offices on Friday to kick off the country’s first such review, testing new powers that could have a wide-ranging impact on how the country’s biggest technology companies operate.
While rules dictate that several ministries could potentially be involved in cybersecurity reviews, not all of them are involved with Didi’s case and some additional ones have been invited on. Here is a closer look at who is involved and what it means for China’s dominant ride-hailing firm.
Which Chinese ministries are involved in cybersecurity reviews?
According to China’s Cybersecurity Review Measures published in 2020, such reviews are handled by the Cybersecurity Review Office under the Cyberspace Administration of China (CAC).
How an obscure government office has struck fear into China’s Big Tech
The office is backed by 12 ministries: the Cyberspace Administration of China, the National Development and Reform Commission, the Ministry of Industry and Information Technology, the Ministry of Public Security, the Ministry of State Security, the Ministry of Finance, the Ministry of Commerce, the People’s Bank of China, the State Administration for Market Regulation, the State Administration of Radio, Film and Television, the National Administration of State Secrets Protection, and the State Cryptography Administration.
Which ministerial bodies are involved in the cybersecurity review of Didi Chuxing?
Seven ministries are involved with Didi’s review, according to a statement from the CAC on Friday, but only four of them are among the agencies that back the Cybersecurity Review Office.
In addition to the CAC, the bodies from the review office include the Ministry of Public Security, the Ministry of State Security and the State Administration for Market Regulation. The other three agencies are included on an “ad hoc” basis. They are the Ministry of Natural Resources, the Ministry of Transport and the State Administration of Taxation.
Why are an additional three ministries involved in Didi’s probe?
Chinese authorities did not provide details of how the cybersecurity review is being conducted, but it is possible the additional agencies have been brought in because of the specific industry in which Didi operates.

The Ministry of Natural Resources is the regulator in charge of mapping the country, indicating the body might be involved in reviewing Didi’s mapping information, which is considered part of the sensitive data that the company stores.
The involvement of the Ministry of Transport, which is in charge of regulating licensing of taxi services, could mean the review will also examine Didi’s compliance with taxi licensing and driver qualification laws.
The taxation authority’s involvement is also a strong sign that the probe may involve an investigation into possible tax fraud.
Why are some ministries absent from Didi’s review?
Eight of the 12 ministries that back the cybersecurity review office are not currently involved in the Didi probe. The most surprising for industry watchers is the absence of the Ministry of Industry and Information Technology, as the agency has been very active in reviewing apps for excessive user data collection.
The fact that the Ministry of Finance is not involved is also notable. The agency is traditionally in charge of regulating audits for Chinese companies seeking public listings overseas. Didi’s initial public offering in New York, against the wishes of the CAC, is considered the main reason for the company’s current woes.


The Chinese Securities Regulatory Commission and the State Administration of Foreign Exchange were also notably not among the new agencies invited to participate. The two bodies are not part of the Cybersecurity Review Office, but they are directly involved in overseas listings.
The People’s Bank of China, one of the 12 review office ministries, is also not directly involved.
What does the review mean for Didi?
This is China’s first cybersecurity review into a company, so there is no precedent to suggest how things might end for Didi. Many analysts and legal experts say it is too early to tell how the investigation might end or what punishments Didi could face.
The only indication of the situation’s severity is all the ministries involved. On the surface, it does not look good for Didi, if only because having investigators from the state and public security offices knocking at the door is a nightmare scenario for any Chinese company.
Didi won’t be the last IPO to set sail for New York, but is there a storm ahead?
The good news for the ride-hailing giant is that the absence of key regulators suggests the company ticked all the necessary boxes regarding the conventional procedures for an overseas IPO.
What does this mean for future cybersecurity reviews?
As the body for initiating, organising and coordinating cybersecurity reviews, the CAC – and its previously obscure Cybersecurity Review Office – now has even more power over the country’s internet giants. The agency also has the authority to involve other government agencies in specific cases.
While it is impossible to know how the CAC might wield this power in the future, or where other tech companies stand, it appears to already be threatening future overseas listings from Chinese firms.
Cybersecurity reviews have also been launched into Boss Zhipin and Full Truck Alliance. Like Didi, both companies publicly listed in New York in June.


Why does ride-hailing giant Didi’s cybersecurity review involve so many Chinese government agencies and who is absent?

The app of Chinese ride-hailing giant Didi Chuxing is seen on a mobile phone in front of the company logo on July 1. Didi has become the subject of China’s first cybersecurity review, but the many different ministries involved suggest a broad scope. Photo: Reuters

The Didi ride-hailing app on a smartphone arranged in Beijing, China, on Monday, July 5, 2021. China expanded its latest crackdown on the technology industry beyond Didi to include two other companies that recently listed in New York, dealing a blow to global investors while tightening the government’s grip on sensitive online data. Photographer: Yan Cong/Bloomberg

Tech

Policy

Business

China Business

News

China

Knowledge

US-China Relations

Technology


China’s Cybersecurity Review Office is managed by 12 ministries, but only four are involved in Didi’s review with three unrelated agencies invited to join
It is too early to tell how China’s first cybersecurity review of a Big Tech company might end, but it’s already having a chilling effect on US IPOs



Only some of the agencies behind China’s Cybersecurity Review Office are involved in Didi’s investigation, but they offer clues about what regulators might be looking for.


Didi Chuxing

Cybersecurity

Start-ups

Provide background, definition and detail of a specific topic, helping the reader understand how something works or what has happened in the past.  (Eg. What is Nafta? US and Mexico are on the verge of revising trade deal.)


Explainer

Explainer | Why does ride-hailing giant Didi’s cybersecurity review involve so many Chinese government agencies and who is absent?