<?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>Singapore</title>
    <link>https://www.hackerone.com/</link>
    <description/>
    <language>en</language>
    
    <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>

  </channel>
</rss>
