<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0" xml:base="https://www.hackerone.com/">
  <channel>
    <title>Asia/Pacific</title>
    <link>https://www.hackerone.com/</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>Protective Security Policy Framework - Policy 11 - Robust ICT Systems</title>
  <link>https://www.hackerone.com/node/2398</link>
  <description><![CDATA[<span class="field field--name-title field--type-string field--label-hidden">Protective Security Policy Framework - Policy 11 - Robust ICT Systems</span>
<span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>h1_admin</span></span>
<span class="field field--name-created field--type-created field--label-hidden">Wed, 10/09/2024 - 12:52
</span>

  
    Jurisdiction
              Australia
          

  
    Region
              Asia/Pacific
          

  
    Requirement
              Required
          

  
    Organization
              Australian Department of Home Affairs
          

  
    Provision
              C.6
          

  
    Applies to
              Australian Government entities
          

  
    Date
              July 29, 2022
          

  
    Description
              <p>C.6 Vulnerability Disclosure Program&nbsp;</p><p>60. Requirement 4 mandates that all entities must have in place a vulnerability disclosure program. This includes having a publicly available vulnerability disclosure policy supported by processes and procedures for receiving, verifying, resolving and reporting on security vulnerabilities disclosed by both internal and external sources.&nbsp;</p><p>61. Implementing a vulnerability disclosure program, based on responsible disclosure, can assist entities, vendors and service providers to improve the security of their products and services as it provides a way for security researchers, customers and members of the public to responsibly notify them of potential security vulnerabilities in a coordinated manner. Furthermore, following the verification and resolution of a reported security vulnerability, it can assist entities, vendors and service providers in notifying their customers of any security vulnerabilities that have been discovered in their products and services and any recommended security patches, updates or mitigations.&nbsp;</p><p>62. For guidance on the creation and maintenance of vulnerability disclosure programs, see the Information Security Manual and Guidelines for Software Development.</p>
          

            <a href="https://www.protectivesecurity.gov.au/system/files/2024-02/policy-11-robust-ict-systems.pdf">https://www.protectivesecurity.gov.au/system/files/2024-02/policy-11-robust-ict…</a>
      ]]></description>
  <pubDate>Wed, 09 Oct 2024 17:52:21 +0000</pubDate>
    <dc:creator>h1_admin</dc:creator>
    <guid isPermaLink="false">2398 at https://www.hackerone.com</guid>
    </item>
<item>
  <title>Code of Practice: Securing the Internet of Things for Consumers</title>
  <link>https://www.hackerone.com/node/2397</link>
  <description><![CDATA[<span class="field field--name-title field--type-string field--label-hidden">Code of Practice: Securing the Internet of Things for Consumers</span>
<span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>h1_admin</span></span>
<span class="field field--name-created field--type-created field--label-hidden">Wed, 10/09/2024 - 08:52
</span>

  
    Jurisdiction
              Australia
          

  
    Region
              Asia/Pacific
          

  
    Requirement
              Recommended
          

  
    Organization
              Australian Government
          

  
    Provision
              Principle 2
          

  
    Applies to
              Device Manufacturers, IoT Service Providers and Mobile Application Developers
          

  
    Date
              2020
          

  
    Description
              <p>Principle 2: Implement a vulnerability disclosure policy&nbsp;</p><p>IoT device manufacturers, IoT service providers and mobile application developers should provide a public point of contact as part of a vulnerability disclosure policy in order for security researchers and others to report issues. Disclosed vulnerabilities should be acted on in a timely manner. Implementing a bug bounty program encourages and rewards the cyber security community for identifying and reporting vulnerabilities, thereby facilitating the responsible and coordinated disclosure and remediation of vulnerabilities.&nbsp;</p><p>Primarily applies to Device Manufacturers, IoT Service Providers and Mobile Application Developers.</p>
          

            <a href="https://www.homeaffairs.gov.au/reports-and-pubs/files/code-of-practice.pdf">https://www.homeaffairs.gov.au/reports-and-pubs/files/code-of-practice.pdf</a>
      ]]></description>
  <pubDate>Wed, 09 Oct 2024 13:52:19 +0000</pubDate>
    <dc:creator>h1_admin</dc:creator>
    <guid isPermaLink="false">2397 at https://www.hackerone.com</guid>
    </item>
<item>
  <title>Regulations on the Management of Security Vulnerabilities in Network Products</title>
  <link>https://www.hackerone.com/node/2381</link>
  <description><![CDATA[<span class="field field--name-title field--type-string field--label-hidden">Regulations on the Management of Security Vulnerabilities in Network Products</span>
<span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>h1_admin</span></span>
<span class="field field--name-created field--type-created field--label-hidden">Mon, 07/29/2024 - 16:45
</span>

  
    Jurisdiction
              People's Republic of China
          

  
    Region
              Asia/Pacific
          

  
    Requirement
              Required
          

  
    Organization
              Ministry of Industry and Information Technology
          

  
    Provision
              Article 5, Article 6
          

  
    Applies to
              Network product providers, network operators and network product security vulnerability collection platforms
          

  
    Date
              July 2021
          

  
    Description
              <strong>Article 5: </strong>Network product providers, network operators and network product security vulnerability collection platforms shall establish and improve channels for receiving network product security vulnerability information and keep them open, and retain network product security vulnerability information receiving logs for no less than 6 months.&nbsp;&nbsp;<strong>Article 6:</strong> "Encourages relevant organizations and individuals to report security vulnerabilities in their products to network product providers" and "Encourage network product providers to establish a reward mechanism for security vulnerabilities in the network products they provide, and reward organizations or individuals who discover and report security vulnerabilities in the network products they provide."
          

            <a href="http://www.cac.gov.cn/2021-07/13/c_1627761607640342.htm">http://www.cac.gov.cn/2021-07/13/c_1627761607640342.htm</a>
      ]]></description>
  <pubDate>Mon, 29 Jul 2024 21:45:48 +0000</pubDate>
    <dc:creator>h1_admin</dc:creator>
    <guid isPermaLink="false">2381 at https://www.hackerone.com</guid>
    </item>
<item>
  <title>Responsible Vulnerability Disclosure Policy</title>
  <link>https://www.hackerone.com/node/2380</link>
  <description><![CDATA[<span class="field field--name-title field--type-string field--label-hidden">Responsible Vulnerability Disclosure Policy</span>
<span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>h1_admin</span></span>
<span class="field field--name-created field--type-created field--label-hidden">Mon, 07/29/2024 - 16:44
</span>

  
    Jurisdiction
              Singapore
          

  
    Region
              Asia/Pacific
          

  
    Requirement
              Recommended
          

  
    Organization
              Cyber Security Agency of Singapore / SingCERT
          

  
    Provision
              Responsible Disclosure Guidelines
          

  
    Applies to
              System Owners
          

  
    Date
              October 2024
          

  
    Description
              Recommends and outlines best practices for "Informers" and "System Owners". The policy also explains in which cases SingCERT can/cannot act as a conduit between Informers and System Owners. Broadly speaking, "SingCERT supports RVD as a means of fostering cooperation between System Owner(s) and the wider cybersecurity community, so as to improve cybersecurity and build a trusted and resilient cyberspace."&nbsp;<strong>"System Owners</strong> are encouraged to develop their own vulnerability disclosure policies setting out how vulnerability reports will be received and handled, what the reports should contain, approaches for disclosure to affected users and the public, as well as any rewards policies." They are also encouraged to keep open contact with the former to take in more information and to update SingCERT and the Informer of its assessments.&nbsp;&nbsp;If the Informer cannot reach the System Owner for some reason, SingCERT can act as a liaison between the two. For this process, that informer would report the vulnerability to SingCERT via email.&nbsp;<br>&nbsp;Version 2.0 of this manual was released in October 2024.
          

            <a href="https://www.csa.gov.sg/Tips-Resource/Resources/singcert/singcert-vulnerability-disclosure-policy">https://www.csa.gov.sg/Tips-Resource/Resources/singcert/singcert-vulnerability-…</a>
      ]]></description>
  <pubDate>Mon, 29 Jul 2024 21:44:10 +0000</pubDate>
    <dc:creator>h1_admin</dc:creator>
    <guid isPermaLink="false">2380 at https://www.hackerone.com</guid>
    </item>
<item>
  <title>Information Security Early Warning Partnership Guideline</title>
  <link>https://www.hackerone.com/node/2379</link>
  <description><![CDATA[<span class="field field--name-title field--type-string field--label-hidden">Information Security Early Warning Partnership Guideline</span>
<span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>h1_admin</span></span>
<span class="field field--name-created field--type-created field--label-hidden">Mon, 07/29/2024 - 16:38
</span>

  
    Jurisdiction
              Japan
          

  
    Region
              Asia/Pacific
          

  
    Requirement
              Recommended
          

  
    Organization
              IPA / JPCERT
          

  
    Provision
              N/A
          

  
    Applies to
              Software Developers and Website Developers
          

  
    Date
              September 2024
          

  
    Description
              Japan's Information-Technology, Promotion Agency (IPA) has a policy of collecting information from informers and, either by itself, or through JPCERT/CC, passes that information onto the relevant parties. IPA handles website vulnerabilities and JPCERT/CC handles software vulnerabilities. According to IPA, the process is in alignment with ISO/IEC 29147:2014 (which as noted with regards to the US FDA's regulations, was updated in 2018).&nbsp;In 2024, Japan's "Standards for Handling Vulnerability-related Information of Software Products and Others" were partially amended to enhance the coordination and communication processes among stakeholders, including finders, software developers, and website operators, thereby improving the overall management and disclosure of vulnerability-related information.&nbsp;
          

            <a href="https://www.ipa.go.jp/en/security/vulnerabilities/partnership.html">https://www.ipa.go.jp/en/security/vulnerabilities/partnership.html</a>
      ]]></description>
  <pubDate>Mon, 29 Jul 2024 21:38:05 +0000</pubDate>
    <dc:creator>h1_admin</dc:creator>
    <guid isPermaLink="false">2379 at https://www.hackerone.com</guid>
    </item>
<item>
  <title>Information Security Manual (ISM)</title>
  <link>https://www.hackerone.com/node/2378</link>
  <description><![CDATA[<span class="field field--name-title field--type-string field--label-hidden">Information Security Manual (ISM)</span>
<span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>h1_admin</span></span>
<span class="field field--name-created field--type-created field--label-hidden">Mon, 07/29/2024 - 16:31
</span>

  
    Jurisdiction
              New Zealand
          

  
    Region
              Asia/Pacific
          

  
    Requirement
              Recommended
          

  
    Organization
              Government Communications Security Bureau
          

  
    Provision
              Objective 5.9
          

  
    Applies to
              New Zealand Government departments, agencies and organizations; Crown entities, local government and private sector organizations
          

  
    Date
              September 2024
          

  
    Description
              <strong>Objective 5.9.1.</strong> Agencies implement a Vulnerability Disclosure Policy (VDP) to enable members of the public to report vulnerabilities in the agency’s public-facing systems and applications and receive feedback on such reports.&nbsp;&nbsp;<strong>Objective 5.9.20. </strong>A VDP will typically include: A scoping statement setting out which systems the policy applies to (e.g. the agency’s website and other public-facing systems); Details of how finders can contact the agency’s security team (including any public keys for encrypting reports); Permitted activities; Acknowledgement of reports and a response time (typically 60 or 90 days) for corrections, adjustments, or other “fixes”; Reporters/finders agreeing to not share information about the vulnerability until the end of the disclosure period, to let the organisation fix the issues before it becomes public; Illegal activities are not permitted (specifying any relevant legislation, such as the Crimes Act, the Privacy Act etc.); and Either a statement that bug bounties will not be paid for any discoveries, or information about the agency’s bug bounty programme.&nbsp;Version 3.8 of this manual was released in September 2024.&nbsp;
          

            <a href="https://nzism.gcsb.govt.nz/ism-document/#Section-12947">https://nzism.gcsb.govt.nz/ism-document/#Section-12947</a>
      ]]></description>
  <pubDate>Mon, 29 Jul 2024 21:31:47 +0000</pubDate>
    <dc:creator>h1_admin</dc:creator>
    <guid isPermaLink="false">2378 at https://www.hackerone.com</guid>
    </item>
<item>
  <title>Information Security Manual (ISM)</title>
  <link>https://www.hackerone.com/node/2377</link>
  <description><![CDATA[<span class="field field--name-title field--type-string field--label-hidden">Information Security Manual (ISM)</span>
<span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>h1_admin</span></span>
<span class="field field--name-created field--type-created field--label-hidden">Mon, 07/29/2024 - 16:25
</span>

  
    Jurisdiction
              Australia
          

  
    Region
              Asia/Pacific
          

  
    Requirement
              Recommended
          

  
    Organization
              Australian Signals Directorate (ASD)
          

  
    Provision
              Pg. 106 (Controls ISM-1616, ISM-1755, ISM-1756, ISM-1717)
          

  
    Applies to
              Large companies, Government agencies
          

  
    Date
              September 2023
          

  
    Description
              <strong>Control: ISM-1616</strong>; Revision: 0; Updated: Aug-20; Applicability: All; Essential Eight: N/A A vulnerability disclosure program is implemented to assist with the secure development and maintenance of products and services.&nbsp;&nbsp;<strong>Control: ISM-1755</strong>; Revision: 1; Updated: Dec-22; Applicability: All; Essential Eight: N/A A vulnerability disclosure policy is developed, implemented and maintained.&nbsp;&nbsp;<strong>Control: ISM-1756</strong>; Revision: 1; Updated: Dec-22; Applicability: All; Essential Eight: N/A Vulnerability disclosure processes, and supporting vulnerability disclosure procedures, are developed, implemented and maintained.&nbsp;<strong>Control: ISM-1717</strong>; Revision: 2; Updated: Sep-23; Applicability: All; Essential Eight: N/A A ‘security.txt’ file is hosted for all internet-facing organisational domains to assist in the responsible disclosure of vulnerabilities in an organisation’s products and services.&nbsp;
          

            <a href="https://www.cyber.gov.au/sites/default/files/2024-03/Information%20Security%20Manual%20%28March%202024%29.pdf">https://www.cyber.gov.au/sites/default/files/2024-03/Information%20Security%20M…</a>
      ]]></description>
  <pubDate>Mon, 29 Jul 2024 21:25:49 +0000</pubDate>
    <dc:creator>h1_admin</dc:creator>
    <guid isPermaLink="false">2377 at https://www.hackerone.com</guid>
    </item>

  </channel>
</rss>
