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.

Policies


Vulnerability Management

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

Low

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 work 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 using either the Security Vulnerability Submission Form (below) or by emailing us at security@honeywell.com. NOTE: to ensure privacy of the vulnerability report it is recommended to encrypt your email/message with our PGP key).

When emailing, please provided the following information:
  • 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 exploit code, if available

Security Vulnerability Submission Form


PERSONAL DETAILS
If applicable
PRODUCT VULNERABILITY REPORT
Please include as much of the following information as is available such as description of the vulnerability, any special configuration required to reproduce the issue, step-by-step instructions to reproduce the issue, proof-of-concept or exploit code.
Link to Privacy Notice.




PGP Key


-----BEGIN PGP PUBLIC KEY BLOCK-----
mQENBE/Z+NYBCAC/++sRC1JFlk1oMMDgl5jxhhh3U+MzTDLiBjHcCeJ4OmBiGRck
LljhZc0oW8SMd2JW0KjtEa0lKW8JIQHWBRjnGPudT8A/Y/3RW/Rx60dTvvUvt6ux
IqWmYDoe3B2aTNJmiQZobKwG5uxq0hKhQmTGsmqBWd9jWJT3lopjR7YPzuI3rWjq
m8DKaz+0JEs0hbPiO5mnID48NaTQvFb5tCySrnOaJIPHAwPtcfz8WWR3wDh3HX6N
sQOohiYs0lcxxF/klycMfgSaOd4KCvMuvvyYzsAgqAc2cyI41SAWhM0t4/7sGVsM
6QkOEQL7oM37fKpynKZoNqVQS43i5vEQXKhTABEBAAG0I0hvbmV5d2VsbCBDSVJU
IDxjaXJ0QGhvbmV5d2VsbC5jb20+iQFyBBABAgBcBQJP2fjWMBSAAAAAACAAB3By
ZWZlcnJlZC1lbWFpbC1lbmNvZGluZ0BwZ3AuY29tcGdwbWltZQgLCQgHAwIKAQIZ
AQUbAwAAAAUWAAMCAQUeAQAAAAYVCAkKAgMACgkQNyARPx/t4AdyoQf+LlUiTv20
VT5Hwbwm4CYxELzjlDaIsDS5DBFAY//gVcaC3J2CW/JeDSvDcBahePADVYI8N3Mk
fo2IPW4G7riB1OvBm8INELEVnDpFgTMffcLtHyyJHdolO7MKNGp/1zZxHriEci6K
22v6GT8TluEA9R6pKA7SI/lbVCxDe53CPzm7rQhxLFr2GJ3YKqvJ8C1OW06+fPDZ
U+nx80X+MIXMJ0+i+i1RS4TVK1chx6MWtkWRPBh022a7q5Ub19ox2osNavwE/gIs
sMcK2UCZKrphavAbh2YGvPl6UA16lIDwSwMZZ32Di/QcXPfZmBqmJxSs88lQmk5X
4AKpkknAGb7IY7Qvc2VjdXJpdHlAaG9uZXl3ZWxsLmNvbSA8c2VjdXJpdHlAaG9u
ZXl3ZWxsLmNvbT6JAW8EEAECAFkFAk/7Qg4wFIAAAAAAIAAHcHJlZmVycmVkLWVt
YWlsLWVuY29kaW5nQHBncC5jb21wZ3BtaW1lCAsJCAcDAgoBBRsDAAAABRYAAwIB
BR4BAAAABhUICQoCAwAKCRA3IBE/H+3gBzppB/9fadXJONWysBKStMVFzH4i2WZC
L+s90NhM+lrGZGan8SUKd9Zxqn5mqoU/WPcqAjm3Q8+R9PG90PDfl3zO5NNys3+M
r6gEolry7eYoZfcdEl5ZJxv92cFRSbO9CALohfmK83sERtEmC+vYOuESrYliRdIT
lnuKUGQ+eyisyLVF6aXLrdUpGwqnVRrb/F35arDh/Ow2wJKRzTRzq2X+CbZeMwg5
IeF9zGWK2WxWwi3g8mlxuke/O9J4wSLVicrU4YmM1KLlLotUx1ln21En55IjMBeX
90jGeT2NUZKqEcQahxI7wy2MxkamCL94/CcXdTbEs6lHQQDPttQVxYUCgNQguQEN
BE/Z+NYBCADa32cq/xqjIdAV27aYUPPEJoE02BmCChQmOSvzRqFimE/iAw79HU3q
tQQOhF5/MYrAbqXxWfjJCzfBaXdVYtIFGzCZQVr0YhOImeqt8k6bD8lmW+oJuHmi
0ZLb+KtFvQg5gOfz84+03ofjukh+EK4xQRg2hhnhjVWjigAkhuTv9HUhaeVRMYAK
+AghMOdrRfHZQX1OV6fsBC8xeKWidpmHMVqi7ZpthgZs1aAgfwXabpt3jcIrqUzU
F1rTA9kXI6YCVumQODfFxMmP+KSoLjDdCstXVHMgv7BAlDdCwkiswwVEtXFJaNVH
zg59emUIU0UbnOd427JYFUfj7KjztmsDABEBAAGJAkEEGAECASsFAk/Z+NcFGwwA
AADAXSAEGQEIAAYFAk/Z+NYACgkQ7789aq8z/0hNgQf/esKby1VRwzmvAqW4YZEq
bY4WWkvlQA30YMHTIBhuAI9hfgdk8kUNvl4Ss6s8CwBfckWB9hE/VzQL7CQfoVGc
g1FGXkZMDeuVqi6k9vp9WmWA05I+hFig/votoITREAGuzRfiPWvxx8KdYXnTFLWw
shjZLw0KtdkoOc8YikAAy+c7sVljsMPMUeW1Kn5wzkR+F4vDPp0AKttmajdXoxZo
UfEQlozDOvL8gfHxjRp1DQi4/MRImE5vYoDjajER6RiA1xONlpdU6Dn3asWZ5UyI
f6RnoCqk5Y9tKAtj1IDhRnvBLe7M5uTZZYe0Ta1eh0EqdXzH5d+E/Ag8v9yV7PGX
pAAKCRA3IBE/H+3gB+IeB/9xqFBIhDdny9XigY92BBlPvMeHWdCvmY//10yR4Zip
TDORF8ou19Ks0gjKrew5fRMjRvXewcn9uzKzVs+6tEyj1BkT9cFG6efSSKQqWojA
aui58mihXutZNCzTWemyCMS0FWwuz/GsZno4gHlRkNUbrnRp4sEiK9FgHL1u4g/+
i7EqTkLnNMEhDTRGTt43+C6jFqeWsPjA2HOzD9T1IMjyAgeCGIgbwqHJ5J59BWhP
v53U0XmoRyCEci63OlK/fcZo+56C86Speuw8LarXD3j34iaNypLq1ThIpiwB5lSu
j3lCEBNAZW4A3KK31ESTryzK/wp7Qlyu+uEiPlC73cud
=PyGa
-----END PGP PUBLIC KEY BLOCK-----


Acknowledgments


Thanks to security researchers who help keep us secure by reporting a vulnerability in our environment.

REPORTERS NAME

ASSOCIATION LINK

Abdul Haq Khokhar

@abdulhaqkhokhar

 

Abdul Rehman Qureshi

http://gbwhatsappapk.net/ 

Abhineeti Singh

https://my.linkedin.com/in/abhineeti-singh-739628a4

Abhishek Misal

http://www.linkedin.com/in/abhishek-misal 

Alexander Sidukov (Positive Technologies)             @cyberopus
Angkan Chanda   
Ari Apridana   https://www.linkedin.com/in/ariapridana/
Ashish Kunwar   @D0rkerDevil 
Bill Ben Haim  https://www.linkedin.com/in/bill-ben-haim-b6775a48/ 
B Dhiyaneshwaran  https://www.linkedin.com/in/dhiyaneshwaran-b-27947a131/ 
Jose Carlos Exposito Bueno   
Gayatri Rachakonda  https://www.linkedin.com/in/gayatri-r-8368a3110 
Kapil Kulkarni*  https://www.linkedin.com/in/kapil-kulkarni-oscp-ceh-chfi-5a333763/  
Khaled Sakr  https://www.linkedin.com/in/khaled-sakr-61821698 
Mahad Ahmed   https://octadev.com.pk
Mohammed Faiz Quadri  https://my.linkedin.com/in/mfaquadri  
Mohamed Hamed  https://www.linkedin.com/in/mohamed-hamed-239378163/
Nitish Shah  https://twitter.com/iamNitishShah
Pethuraj M   https://www.pethuraj.in/
Steven Hampton  @keritzy 
Tansel ÇETİN @tansbey 
Udhaya Prakash C  @Udhaya_ISRO 
Umesh Jore*  https://www.linkedin.com/in/umesh-jore-55015194 
Utkarsh Agrawal   https://twitter.com/agrawalsmart7 
Vasim Shaikh  https://www.linkedin.com/in/vasim-shaikh-094507110 
Venkatesh Sivakumar   @PranavVenkats  
Vijiln  @vijiln 
Wai Yan Aung  @waiyanaun9