{"id":785507,"date":"2024-07-09T23:38:51","date_gmt":"2024-07-10T04:38:51","guid":{"rendered":"http:\/\/spaceweekly.com\/?p=785507"},"modified":"2024-07-09T23:38:51","modified_gmt":"2024-07-10T04:38:51","slug":"report-on-unauthorized-access-at-jaxa","status":"publish","type":"post","link":"https:\/\/spaceweekly.com\/?p=785507","title":{"rendered":"Report on Unauthorized Access at JAXA"},"content":{"rendered":"<p> <br \/>\n<\/p>\n<div>\n<div class=\"elem_heading_lv2\">\n<div class=\"elem_center elem_heading_lv2_pad\">\n<p><h2>Report on Unauthorized Access at JAXA<\/h2>\n<p>\t\t\t<!-- \/elem_heading_lv2 --><\/p>\n<\/div>\n<\/div>\n<div class=\"elem_paragraph\">\n<p class=\"right\">Japan Aerospace Exploration Agency<\/p>\n<p>\t\t\t<!-- \/elem_paragraph --><\/div>\n<div class=\"elem_paragraph\">\n<p>\n    \u2003The Japan Aerospace Exploration Agency (JAXA) reports the status of its response to the compromised<br \/>\n    information caused by unauthorized access last year.\n  <\/p>\n<\/div>\n<div class=\"elem_paragraph\">\n<p>\n    \u2003In October last year, based on a notification from an external organization, JAXA recognized unauthorized<br \/>\n    access to internal servers on the JAXA&#8217;s network (hereinafter referred to as &#8220;the incident&#8221;). While JAXA immediately<br \/>\n    took initial measures, such as blocking all malicious communication, we also launched the investigation in<br \/>\n    cooperation with expert organizations and security vendors to understand the incident, developed countermeasures,<br \/>\n    and implemented them.\n  <\/p>\n<\/div>\n<div class=\"elem_paragraph\">\n<p>\n    \u2003The attachment provides an overview of the incident. JAXA confirmed that some of the information we manage<br \/>\n    (related to activities with external organizations and personal information) was compromised.\n  <\/p>\n<\/div>\n<div class=\"elem_paragraph\">\n<p>\n    \u2003We sincerely apologize for any inconvenience to those affected by this incident.\n  <\/p>\n<\/div>\n<div class=\"elem_paragraph\">\n<p>\n    \u2003While we cannot disclose the details of information that was compromised due to the nature of our relationship<br \/>\n    with third parties, we apologized and notified the affected individuals and partners. As of now, JAXA has not<br \/>\n    received any reports of significant disruption to the activities of those involved. We sincerely regret any<br \/>\n    inconvenience this incident may have caused.<br \/>\u2003Although JAXA does not see the severe impact on our activities, including cooperation with domestic and<br \/>\n    international partners, by the incident, we take it very seriously as a matter that could potentially harm<br \/>\n    relationships of trust, and we will strengthen our measures to prevent a recurrence.\n  <\/p>\n<\/div>\n<div class=\"elem_paragraph\">\n<p>\n    \u2003Although a few instances of unauthorized access occurred in 2024, JAXA confirmed that they did not involve any<br \/>\n    compromise of information. Those unauthorized access, including the incident last year, targeted VPN devices.\n  <\/p>\n<\/div>\n<div class=\"elem_paragraph\">\n<p>\n    \u2003JAXA has already implemented short-term measures, such as establishing a system to promptly respond to<br \/>\n    vulnerabilities, and developed permanent measures to further enhance security. We are currently materializing these<br \/>\n    permanent measures and will continue to strengthen our information security measures in the future.\n  <\/p>\n<\/div>\n<hr style=\"background-image: none; margin-top: 1rem;\" \/>\n<div class=\"elem_paragraph\">\n<p>\n    1. JAXA&#8217;s Response<br \/><span style=\"display: block; margin-left: 1rem;\"><br \/>\n      \u2003Based on a notification from external organizations, JAXA immediately took initial actions, such as blocking<br \/>\n      all malicious communications and disconnecting all the compromised servers and computers from the JAXA network.<br \/>\n      Then, we engaged a security vendor to investigate the signs of the compromise and analyze all the compromised<br \/>\n      servers and computers. We discovered malwares and removed them, as well as implemented emergency measures to<br \/>\n      mitigate potential risks, including enhancing the monitoring of internal communications.<br \/>\u2003In addition, since we found the possibility of unauthorized access to Microsoft 365 (&#8220;MS365&#8221;) during the<br \/>\n      investigation, a specialized team from the Microsoft corporation investigated and confirmed that no further<br \/>\n      breaches had occurred.<br \/>\u2003Throughout the implementation of these measures, JAXA has been working closely with external organizations.<br \/>\n      This includes cooperation with the police, the JPCERT Coordination Center, the Information-technology Promotion<br \/>\n      Agency (IPA), and other expert organizations. We have been actively reporting and sharing information with them,<br \/>\n      including unauthorized communication destinations and malwares.<br \/>\n    <\/span>\n  <\/p>\n<\/div>\n<div class=\"elem_paragraph\">\n<p>\n    2. Scope of Compromise<br \/><span style=\"display: block; margin-left: 1rem;\"><br \/>\n      \u2003JAXA identified the scope of compromise based on the initial investigation, the investigation by the<br \/>\n      security vendor and Microsoft, and the analysis by JAXA. In addition, we confirmed that the attacker used multiple<br \/>\n      unknown malwares, making it difficult to detect the unauthorized access.<br \/>\n    <\/span>\n  <\/p>\n<ol style=\"display: block; margin-left: 1rem;\">\n<li style=\"display: grid; grid-template-columns: 1.3rem 1.5fr; font-size: 116.6%;\">\n      <span>(i)<\/span><br \/>\n      <span>the attacker likely exploited a vulnerability in a VPN device to gain the initial access to JAXA&#8217;s internal<br \/>\n        servers and computers. It is highly likely that the previously announced vulnerability was exploited.<\/span>\n    <\/li>\n<li style=\"display: grid; grid-template-columns: 1.3rem 1.5fr; font-size: 116.6%;\">\n      <span>(ii)<\/span><br \/>\n      <span>the attacker further expanded the scope of unauthorized access and compromised JAXA&#8217;s user account<br \/>\n        information.<\/span>\n    <\/li>\n<li style=\"display: grid; grid-template-columns: 1.3rem 1.5fr; font-size: 116.6%;\">\n      <span>(iii)<\/span><br \/>\n      <span>the attacker illegally accessed JAXA&#8217;s MS365 services with the account information it obtained.<\/span>\n    <\/li>\n<\/ol>\n<\/div>\n<div class=\"elem_paragraph\">\n<p>\n    3. Compromised Information<br \/><span style=\"display: block; margin-left: 1rem;\"><br \/>\n      \u2003As a result of the incident, some information (including personal information of JAXA employees, etc.)<br \/>\n      stored on the compromised JAXA servers and computers may have been breached. In addition, we confirmed that some<br \/>\n      of the information managed on JAXA&#8217;s MS365 service (related to activities with external organizations and personal<br \/>\n      information) were compromised. We have already explained and apologized to those affected. The information systems<br \/>\n      and networks compromised in this incident do not handle sensitive information related to launch vehicles and<br \/>\n      satellite operations.<br \/>\n    <\/span>\n  <\/p>\n<\/div>\n<div class=\"elem_paragraph\">\n<p>\n    4. Countermeasures<br \/><span style=\"display: block; margin-left: 1rem;\"><br \/>\n      \u2003In response to this incident, we implemented short-term measures, such as establishing an operation to<br \/>\n      respond to vulnerabilities promptly and strengthening the monitoring of internal communication. In addition, JAXA<br \/>\n      developed permanent measures to further enhance security, such as enhancing monitoring of the entire network and<br \/>\n      endpoints, improving remote access methods, increasing the efficiency and visibility of operational management,<br \/>\n      and enhancing anti-spoofing measures. We are currently in the process of materializing these permanent<br \/>\n      measures.<br \/>\u2003In the course of taking the above measures and strengthening monitoring, we have detected and responded to<br \/>\n      multiple unauthorized accesses to JAXA&#8217;s network since January of this year (including zero-day attacks), though<br \/>\n      no information was compromised.<br \/>\n    <\/span>\n  <\/p>\n<\/div>\n<div class=\"elem_paragraph\">\n<p>\n    5. Future Efforts<br \/><span style=\"display: block; margin-left: 1rem;\"><br \/>\n      \u2003As cyber-attacks become increasingly sophisticated and countermeasures constantly evolve, JAXA is firmly<br \/>\n      aware of the need for prompt and appropriate security responses and plans to steadily implement short-term and<br \/>\n      permanent measures in response to this incident. JAXA will further strengthen information security in cooperation<br \/>\n      with related organizations, including expert organizations.<br \/>\n    <\/span>\n  <\/p>\n<\/div>\n<div class=\"elem_paragraph\">\n<p>\n    For inquiries regarding personal information, please contact the following:\n  <\/p>\n<div style=\"border: 1px solid; padding: 10px; margin-top: 1rem;\">\n<p>\n      Security and Information Systems Department<br \/>Japan Aerospace Exploration Agency (JAXA)<br \/>Address: 2-1-1 Sengen, Tsukuba-shi, Ibaraki 305-8505<br \/>Email: sec-personal-info[a]ml.jaxa.jp \uff08please replace [a] with @\uff09\n    <\/p>\n<\/p><\/div>\n<\/div>\n<p>\t\t<!-- \/area_content_main --><\/div>\n<p><br \/>\n<br \/><a href=\"https:\/\/global.jaxa.jp\/press\/2024\/07\/20240705-2_e.html?rand=771667\">Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Report on Unauthorized Access at JAXA Japan Aerospace Exploration Agency \u2003The Japan Aerospace Exploration Agency (JAXA) reports the status of its response to the compromised information caused by unauthorized access&hellip; <\/p>\n","protected":false},"author":1,"featured_media":771669,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-785507","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-japan"],"_links":{"self":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/785507","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=785507"}],"version-history":[{"count":0,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/785507\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/media\/771669"}],"wp:attachment":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=785507"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=785507"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=785507"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}