Product Security



    We take security concerns seriously and work to quickly evaluate and address them. Once reported, we commit the appropriate resources to analyze, validate and provide corrective actions to address the issue.

    The goal of our Product Security Incident Response Team (PSIRT) is to minimize customers’ risk associated with security vulnerabilities by providing timely information, guidance and remediation of vulnerabilities in our products, including software and applications, hardware and devices, services and solutions. This team manages the receipt, investigation, internal coordination, remediation and disclosure of security vulnerability information related to Honeywell products.

    PSIRT coordinates the response and disclosure of all externally identified product vulnerabilities.

    Reporting a Potential Security Vulnerability

    We welcome reports from independent researchers, industry organizations, vendors and customers concerned with product security. To find out more information on how to report a potential vulnerability, please visit the Vulnerability Reporting web page.

    Coordinated Vulnerability Disclosure

    We strive to follow Coordinated Vulnerability Disclosure (CVD). This process allows independent reporters who discover a vulnerability contact Honeywell directly and allow us the opportunity to investigate and remediate the vulnerability before the reporter discloses the information to the public.

    The PSIRT will coordinate with the reporter throughout the vulnerability investigation and will provide them with updates on progress as appropriate. With their agreement, the PSIRT may recognize the reporter on our acknowledgments for finding a valid product vulnerability and privately reporting the issue. After an update or mitigation information is publicly released by Honeywell, the reporter is welcome to discuss the vulnerability publicly.

    Following the CVD allows us to protect our customers and at the same time, coordinate public disclosures and appropriately acknowledge the reporter for their finding. If a reported vulnerability involves a vendor product, the PSIRT will notify the vendor directly, coordinate with the reporter, or engage a third-party coordination center.

    Vulnerability Management Process

    Assessing Security Risk Using Common Vulnerability Scoring System (CVSS)

    We use the Common Vulnerability Scoring System version 3.0 (CVSS v3.0) to evaluate the severity level of identified vulnerabilities. This enables a common scoring method and a common language to communicate the characteristics and impacts of vulnerabilities and attempts to establish a measurement of how much concern a vulnerability warrants. The model uses three distinct measurements or scores that include base, temporal and environmental calculations, each consisting of a set of metrics. The full standard, which is maintained by the Forum of Incident Response and Security Teams (FIRST).

    We follow CVSS v3.0 Specification Document Qualitative Severity Rating Scale to define Severity Ratings as shown in the table below:

    Security Impact Rating CVSS Score
    Critical 9.0 – 10.0
    High 7.0 – 8.9
    Medium 4.0 – 6.9
    1.0 – 3.9

    We reserve the right to deviate from these guidelines in specific cases if additional factors are not properly captured in the CVSS score.

    When and where applicable, Honeywell Security Bulletins will provide the CVSS v3.0 Base Score. We focus on the base metric group only because it brings the most value to our customers and represents the intrinsic characteristics of a vulnerability. Risk assessment is based on an average of risk across a diverse set of installed systems and may not represent the true risk of your local installation.

    We recommend consulting a security or IT professional to evaluate the risk of your specific configuration and encourages you to compute the environmental score based on your network parameters and that all customers take into account the base score and any temporal and environmental scores that may be relevant to their environment to assess their overall risk. This overall score represents a moment in time and is tailored to your specific environment. You should use a security or IT professional’s assessment of the issue and this final score to prioritize responses in your own environment.

    Vulnerability Communication Policy

    Honeywell uses the following guidelines for non-third-party software vulnerabilities to determine the appropriate communication plan:

    Security Impact Rating CVSS Score Communication Plan
    Critical 9.0–10.0 Security Bulletin
    High 7.0–8.9
    Medium 4.0–6.9 Product Release Note
    Low 3.9 or below

    If there is a security issue with a third-party software component that is used in a Honeywell product, we may publish a Security Bulletin. If a Security Bulletin is published for a third-party software component vulnerability, then we typically use the CVSS score provided by the component creator. In some cases, the CVSS score may be adjusted to reflect the impact to the product.

    We reserve the right to deviate from these guidelines in specific cases if additional factors are not properly captured in the CVSS score.

    Notifying Customers of Vulnerability

    In most cases, we intend to notify customers when there is an identified practical workaround or fix for a security vulnerability. The notification is through either targeted communications or by posting a security bulletin on the specific product web page. This will be posted after the PSIRT has completed the vulnerability response process and determined that sufficient software patches or workarounds exist to address the vulnerability or subsequent public disclosure of code fixes is planned to address the vulnerabilities.

    Security bulletins attempt to balance the right amount of information by providing sufficient details to enable customers to make informed decisions to protect themselves, but not verbose details that would allow malicious users to take advantage of the information. They will typically include the following information:

    1. Products and versions affected.
    2. Common Vulnerability Enumeration (CVE) identifier for the vulnerability.
    3. Brief description of the vulnerability and potential impact if exploited.
    4. The Common Vulnerability Scoring System (CVSS) severity rating for the vulnerability.
    5. Mitigation details such as an upgrade, fix, mitigation or other customer action.
    6. Credit to the reporter of the identified vulnerability and acknowledgment for coordinating with Honeywell.

    We will not provide additional information about the specifics of vulnerabilities beyond what is provided in the security bulletin or other documentation such as release notes, knowledge base articles, FAQs, etc. We do not distribute exploit or proof of concept code for identified vulnerabilities.

    In accordance with industry practices, we do not share the findings from internal security testing or other types of security activities with external entities. It is important to note that any scan of our services and production systems will be considered an attack. If you are an OEM partner, please coordinate your needs with your Honeywell program manager.

    Security Notice

    We may release a special communication to respond quickly and appropriately to public disclosures where the vulnerability may have received significant public attention, or is expected to be actively exploited. In such an event, we may expedite the communication and may or may not include a complete set of patches or workarounds.

    Vulnerability Remediation

    We take security concerns seriously and works to evaluate and address them in a timely manner. Response timelines will depend on many factors, including: the severity, the product affected, the current development cycle, QA cycles, and whether the issue can only be updated in a major release.

    Remediation may take one or more of the following forms:

    1. A new release
    2. A Honeywell-provided patch
    3. Instructions to download and install an update or patch from a third-party
    4. A workaround to mitigate the vulnerability

    Notwithstanding the foregoing, we do not guarantee a specific resolution for issues and not all issues identified may be fixed.

    Report a Vulnerability Issue

    We encourage coordinated disclosure of security vulnerabilities. Security researchers, industry groups, government organizations and vendors can report potential security vulnerabilities to Honeywell by choosing one of the two vulnerability types in the form below or by emailing us with below details mentioned.

    If the vulnerability affects a product, service or solution, email us at PSIRT@Honeywell.com, with the following instructions/details:

    • Please encrypt using Honeywell’s public PGP key (see PGP Key page) and include the following:
      • Product and version
      • Description of the potential vulnerability
      • Any special configuration required to reproduce the issue
      • Step by step instructions to reproduce the issue
      • Proof of concept or exploit code, if available
      • Potential Impact

    For all other security issues, email us at Security@honeywell.com with the following instructions. 

    • Please encrypt using Honeywell’s public PGP key (see PGP Key page) and include the following:
      • Website URL or location
      • Type of vulnerability (XSS, Injection, etc.)
      • Instructions to reproduce the vulnerability
      • Proof of concept or exploit code, including how an attacker could exploit the vulnerability
      • Potential impact

    Download PGP Key here

    PGP Key

    Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
    Comment: GPGTools - https://gpgtools.org



    We would like to acknowledge all individuals who have reported a vulnerability in our environment. We are grateful for these security researchers who help keep us secure.

    Vinayak Sakhare https://www.linkedin.com/in/vinayak-sakhare-63b343119  
    Uri Katz of Claroty Research - Team82 https://claroty.com/team82  
    Mark Rosenbaum https://linktr.ee/markrosenbaum  
    Aniket Anil Deshmane* https://twitter.com/AniketDeshmane9?s=08  
    Armanul Miraz @mirazdevox  
    Ben Leonard-Lagarde    
    Carl Dworzack    
    Danish Tariq https://www.linkedin.com/in/danishtariqq/  
    Harinder Singh https://www.linkedin.com/in/lambardar  
    Husain Murabbi (cyber_humans) https://www.linkedin.com/in/husain-murabbi-cyberhumans/  
    Joel Sanchez https://www.linkedin.com/in/joel-sanchez-199b79123/  
    Joost Bakker BovenIJ ziekenhuis  
    Martino Tommasini     
    Mansoor Rangwala (cyber_humans) https://www.linkedin.com/in/mansoor-rangwala-cyberhumans/  
    Netan Mangal* https://www.linkedin.com/in/netanmangal  
    Pratik Sunil Tryambake    
    Rajnish Kumar Gupta https://www.linkedin.com/in/geekyrajnish  
    Rick de Jager https://github.com/RickdeJager  
    Swapnil Maurya @swapmaurya20  
    Thilo Mohri https://www.linkedin.com/in/tmohri/  
    Todd Heflin www.linkedin.com/in/taterbrown  
    Tracy Williams https://www.linkedin.com/in/battletroll/  
    Vinayak Chaturvedi https://www.linkedin.com/in/vinayak-chaturvedi-348b071a1  
    Alberto Perez Agudo    
    Athul Jayaram https://www.linkedin.com/in/athuljayaram  
    Dominique van Dorsselaer    
    GwanYeong Kim @sec_karas  
    Jan Kopriva https://www.linkedin.com/in/jan-kopriva/  
    Mohammed Adam https://www.linkedin.com/in/mohammedadam24/  
    Rahul Gamit https://www.linkedin.com/in/rahul-gamit-54a93a188/  
    Ramkumar Ganesan https://www.linkedin.com/in/ram-kumar94  
    Ronak Nahar https://www.linkedin.com/in/naharronak/  
    Sreekanth Reddy https://twitter.com/sree_appsec  
    Sumit Grover @sumgr0   
    Abhishek Misal http://www.linkedin.com/in/abhishek-misal  
    B. Dhiyaneshwaran    
    Bill Ben Haim
    Kapil Kulkarni*
    Mohamed Hamed https://www.linkedin.com/in/mohamed-hamed-239378163/  
    Nitish Shah https://twitter.com/iamNitishShah  
    Pethuraj M https://www.pethuraj.in/  
    Udhaya Prakash C*  @Udhaya_ISRO  
    Utkarsh Agrawal  https://twitter.com/agrawalsmart7  
    Vijiln @vijiln  
    2017 and earlier:
    Abdul Haq Khokhar @abdulhaqkhokhar  
    Abdul Rehman Qureshi    
    Abhineeti Singh https://my.linkedin.com/in/abhineeti-singh-739628a4  
    Alexander Sidukov (Positive Technologies) @cyberopus  
    Alisha Sheikh https://in.linkedin.com/in/alisha-sheikh-96059615a  
    Amit Kumar https://www.linkedin.com/in/amit-kumar-9853731a4  
    Angkan Chanda    
    Ari Apridana https://www.linkedin.com/in/ariapridana/  
    Ashish Kunwar @D0rkerDevil  
    Ayush Pandey https://www.linkedin.com/in/ayush-pandey-148797175  
    Gayatri Rachakonda https://www.linkedin.com/in/gayatri-r-8368a3110  
    Gjoko Krstic https://www.linkedin.com/in/gjokokrstic  
    Harish P https://www.linkedin.com/in/harish-p-62b38a158  
    Harshal S. Sharma https://www.linkedin.com/in/harshalss-war10ck/  
    Jayesh Patel https://www.breachlock.com  
    Joachim Kerschbaumer  https://twitter.com/joachimk  
    Jose Carlos Exposito Bueno    
    Khaled Sakr https://www.linkedin.com/in/khaled-sakr-61821698  
    Lutfu Mert Ceylan https://linkedin.com/in/lutfumertceylan/  
    Mahad Ahmed https://octadev.com.pk  
    Maxim Rupp http://rupp.it/  
    Mikael Vingaard Vingaard.dk  
    Mindset Technologies https://mindsetechnologies.com/certificates  
    Mohammed Faiz Quadri https://my.linkedin.com/in/mfaquadri  
    Nadav Erez (Claroty) https://www.linkedin.com/in/nadav-erez/  
    Nick Jensen https://www.linkedin.com/in/nickmarcjensen/  
    Pratik Khalane https://www.linkedin.com/in/pratik-khalane/  
    Rei Henigman (Claroty)    
    Saurabh Shinde https://www.linkedin.com/in/saurabhshinde96/  
    Serge Lacroute https://www.linkedin.com/in/serge-lacroute-677a3b134/  
    Srikar V https://linkedin.com/in/exp1o1t9r  
    Steven Hampton @keritzy  
    Tansel ÇETİN @tansbey  
    Umesh Jore* https://www.linkedin.com/in/umesh-jore-55015194  
    Varun Thorat https://www.linkedin.com/in/3xtrinsic/  
    Vasim Shaikh https://www.linkedin.com/in/vasim-shaikh-094507110  
    Venkatesh Sivakumar @PranavVenkats   
    Victor Curalea https://twitter.com/VictorCuralea  
    Victor Hylejam https://twitter.com/ov3rflow1  
    Wai Yan Aung @waiyanaun9   
    Yunus Aydin https://www.linkedin.com/in/aydinnyunus/  

    * Indicates multiple submissions