submit bug report: https://kfc.responsibledisclosure.com/hc/en-us

Responsible Disclosure Policy:
This page is for security researchers interested in reporting application security vulnerabilities.

If you have reported an issue determined to be within program scope, is determined to be a valid security issue, and you have followed program guidelines, ResponsibleDisclosure.com will recognize your finding and you will be allowed to disclose the vulnerability after a fix has been issued. Please refer all questions to ResponsibleDisclosure.com portal.


Typical Vulnerabilities Accepted:
OWASP Top 10 vulnerability categories
Infrastructure vulnerabilities
Other vulnerabilities with demonstrated impact


Typical Out of Scope:
Theoretical vulnerabilities
Informational disclosure of non-sensitive data
Low impact session management issues
Self XSS (user defined payload)
For a full list of program scope please visit the Responsible Disclosure details page.


Responsible Disclosure Guidelines:
Adhere to all legal terms and conditions outlined at responsibledisclosure.com
Work directly with ResponsibleDisclosure.com on vulnerability submissions
Provide detailed description of a proof of concept to detail reproduction of vulnerabilities
Do not engage in disruptive testing like DoS or any action that could impact the confidentiality, integrity or availability of information and systems
Do not engage in social engineering or phishing of customers or employees
Do not request compensation for time and materials or vulnerabilities discovered

submit bug report: https://www.royalihc.com/responsible-disclosure-policy

Responsible disclosure policy
Royal IHC considers the security of its systems to be critical. However, weak spots may arise.

If you find a weak spot in one of our systems, let us know, so that we can take steps to remedy it as soon as possible. We are keen to cooperate with you in order to better protect our users and systems.

The Coordinated Vulnerability Disclosure policy is not an open invitation to actively and intensively scan our company network in order to discover its weaknesses.

What to do:

Email your findings to ITSecurity@royalihc.com as soon as possible.
Do not abuse any vulnerability, for example, by downloading more data than is necessary to demonstrate the leak, installing a ‘backdoor’ or by changing or deleting data.
Exercise further caution with regard to personal data.
Do not share information about any vulnerability with others until it has been resolved. Delete all confidential information after a vulnerability has been acknowledged.
Do not launch attacks on the physical security or applications of third parties, social engineering, distribute denial-of-service or spam.
Provide sufficient information to enable reproduction of the vulnerability, so that we can remedy it as soon as possible. Generally the IP address or URL of the affected system and a description of the vulnerability and operations carried out are sufficient, but more information may be required in the case of complex vulnerabilities.
Our promise:

We will respond within one working day to confirm the receipt of your report.
We will respond within three working days with our appraisal of your report, and an expected resolution date.
If you have complied with the aforementioned conditions, we will not take legal action against you with regard to the report.
We will strive to resolve the vulnerability as quickly as possible and will keep you informed of the progress made in remedying it.
We will treat your report confidentially and will not share your personal details with third parties without your authorisation, unless required to do so in order to comply with a legal obligation.
Anonymous or pseudonymous reporting is possible. You should be aware that in such cases we cannot contact you concerning the steps taken, progress in stopping the leak, publication or the possible reward for the report.
We would like to be involved in any publication of the vulnerability after it has been resolved. If you wish, we will credit you as having discovered the vulnerability when issuing our report.
Royal IHC currently does not have an active bounty program. However, exceptions will be made at our own discretion for particularly valuable reports.

submit bug report: https://www.heroku.com/policy/security

Heroku Security
Heroku Overview
Heroku is a cloud application platform used by organizations of all sizes to deploy and operate applications throughout the world. Our platform allows organizations to focus on application development and business strategy while Heroku focuses on infrastructure management, scaling, and security. Heroku applies security best practices and manages platform security so customers can focus on their business. Our platform is designed to protect customers from threats by applying security controls at every layer from physical to application, isolating customer applications and data, and with its ability to rapidly deploy security updates without customer interaction or service interruption.

Heroku’s Commitment to Trust
“Nothing is more important to our company than the privacy of our customer’s data." — Parker Harris, Salesforce EVP, Technology

Trust is a core principle of Salesforce and Heroku. It’s this commitment to customer privacy and inspiring trust that directs the decisions we make on a daily basis. Trust is the responsibility of each and every employee and one we take seriously.

To learn more about Salesforce efforts to protect customer privacy and actions customers can take to protect their data visit the Salesforce Trust And Compliance Policies.

Vulnerability Reporting
If you are a Heroku customer and you would like to report a vulnerability or have a security concern regarding Heroku, please email security@salesforce.com.

For other security inquiries, please open a support ticket.

Researchers
As part of our commitment to working with security researchers to make our platform safer, Heroku operates a bug bounty program to reward those who find and report bugs in our platform.

To report vulnerabilities related to Heroku:

Privately share details of the suspected vulnerability with Heroku by submitting them with Heroku by submitting them to security@salesforce.com.
Provide full details of the suspected vulnerability so the Heroku security team may validate and reproduce the issue.
Valid findings will be considered for compensation in accordance with the Salesforce Bug Bounty Program Policy.

Security Assessments and Compliance
Data Centers
Heroku’s physical infrastructure is hosted and managed within Amazon’s secure data centers and utilize the Amazon Web Service (AWS) technology. Amazon continually manages risk and undergoes recurring assessments to ensure compliance with industry standards. Amazon’s data center operations have been accredited under:

ISO 27001
SOC 1 and SOC 2/SSAE 16/ISAE 3402 (Previously SAS 70 Type II)
PCI Level 1
FISMA Moderate
Sarbanes-Oxley (SOX)
PCI
We use PCI compliant payment processor Braintree for encrypting and processing credit card payments. Heroku’s infrastructure provider is PCI Level 1 compliant.

Sarbanes-Oxley
As a publicly traded company in the United States, Salesforce is audited annually and remains in compliance with the Sarbanes-Oxley (SOX) Act of 2002.

Penetration Testing and Vulnerability Assessments
Third party security testing of the Heroku application is performed by independent and reputable security consulting firms. Findings from each assessment are reviewed with the assessors, risk ranked, and assigned to the responsible team.

Physical Security
Heroku utilizes ISO 27001 and FISMA certified data centers managed by Amazon. Amazon has many years of experience in designing, constructing, and operating large-scale data centers. This experience has been applied to the AWS platform and infrastructure. AWS data centers are housed in nondescript facilities, and critical facilities have extensive setback and military grade perimeter control berms as well as other natural boundary protection. Physical access is strictly controlled both at the perimeter and at building ingress points by professional security staff utilizing video surveillance, state-of-the-art intrusion detection systems, and other electronic means. Authorized staff must pass two-factor authentication no fewer than three times to access data center floors. All visitors and contractors are required to present identification and are signed in and continually escorted by authorized staff.

Amazon only provides data center access and information to employees who have a legitimate business need for such privileges. When an employee no longer has a business need for these privileges, his or her access is immediately revoked, even if they continue to be an employee of Amazon or Amazon Web Services. All physical and electronic access to data centers by Amazon employees is logged and audited routinely.

For additional information see: https://aws.amazon.com/security

Environmental Safeguards
Fire Detection and Suppression
Automatic fire detection and suppression equipment has been installed to reduce risk. The fire detection system utilizes smoke detection sensors in all data center environments, mechanical and electrical infrastructure spaces, chiller rooms and generator equipment rooms. These areas are protected by either wet-pipe, double-interlocked pre-action, or gaseous sprinkler systems.

Power
The data center electrical power systems are designed to be fully redundant and maintainable without impact to operations, 24 hours a day, and seven days a week. Uninterruptible Power Supply (UPS) units provide back-up power in the event of an electrical failure for critical and essential loads in the facility. Data centers use generators to provide backup power for the entire facility.

Climate and Temperature Control
Climate control is required to maintain a constant operating temperature for servers and other hardware, which prevents overheating and reduces the possibility of service outages. Data centers are conditioned to maintain atmospheric conditions at optimal levels. Monitoring systems and data center personnel ensure temperature and humidity are at the appropriate levels.

Management
Data center staff monitor electrical, mechanical and life support systems and equipment so issues are immediately identified. Preventative maintenance is performed to maintain the continued operability of equipment.

For additional information see: https://aws.amazon.com/security

Network Security
Firewalls
Firewalls are utilized to restrict access to systems from external networks and between systems internally. By default, all access is denied and only explicitly allowed ports and protocols are allowed based on business need.  Each system is assigned to a firewall security group based on the system’s function. Security groups restrict access to only the ports and protocols required for a system’s specific function to mitigate risk.

Host-based firewalls restrict customer applications from establishing localhost connections over the loopback network interface to further isolate customer applications. Host-based firewalls also provide the ability to further limit inbound and outbound connections as needed.

DDoS Mitigation
Our infrastructure provides DDoS mitigation techniques including TCP Syn cookies and connection rate limiting in addition to maintaining multiple backbone connections and internal bandwidth capacity that exceeds the Internet carrier supplied bandwidth.  We work closely with our providers to quickly respond to events and enable advanced DDoS mitigation controls when needed.

Spoofing and Sniffing Protections
Managed firewalls prevent IP, MAC, and ARP spoofing on the network and between virtual hosts to ensure spoofing is not possible. Packet sniffing is prevented by infrastructure including the hypervisor which will not deliver traffic to an interface which it is not addressed to.  Heroku utilizes application isolation, operating system restrictions, and encrypted connections to further ensure risk is mitigated at all levels.

Port Scanning
Port scanning is prohibited and every reported instance is investigated by our infrastructure provider.  When port scans are detected, they are stopped and access is blocked.

Data Security
Customer Applications
Each application on the Heroku platform runs within its own isolated environment and cannot interact with other applications or areas of the system. This restrictive operating environment is designed to prevent security and stability issues.  These self-contained environments isolate processes, memory, and the file system using LXC while host-based firewalls restrict applications from establishing local network connections.

For additional technical information see: https://devcenter.heroku.com/articles/dyno-isolation

Heroku Postgres
Customer data is stored in separate access-controlled databases per application. Each database requires a unique username and password that is only valid for that specific database and is unique to a single application. Customers with multiple applications and databases are assigned separate databases and accounts per application to mitigate the risk of unauthorized access between applications.

Customer connections to postgres databases require SSL encryption to ensure a high level of security and privacy.  When deploying applications, we encourage customers to take advantage of encrypted database connections.

Stored data can be encrypted by customer applications in order to meet data security requirements. Customers can implement data storage, key management, and data retention requirements when developing their application.

Add-ons
Customers can extend the functionality of applications by using Heroku Add-ons. Add-ons are offered and managed by 3rd party companies and implement their own security controls and processes.

For additional information see: https://addons.heroku.com

System Security
System Configuration
System configuration and consistency is maintained through standard, up-to-date images, configuration management software, and by replacing systems with updated deployments. Systems are deployed using up-to-date images that are updated with configuration changes and security updates before deployment. Once deployed, existing systems are decommissioned and replaced with up-to-date systems.

Customer Application Isolation
Applications on the Heroku platform run within their own isolated environment and cannot interact with other applications or areas of the system to prevent security and stability issues.  These self-contained environments isolate processes, memory, and the file system while host-based firewalls restrict applications from establishing local network connections.

For additional technical information see: https://devcenter.heroku.com/articles/dyno-isolation

System Authentication
Operating system access is limited to Heroku staff and requires username and key authentication. Operating systems do not allow password authentication to prevent password brute force attacks, theft, and sharing.

Vulnerability Management
Our vulnerability management process is designed to remediate risks without customer interaction or impact.  Heroku is notified of vulnerabilities through internal and external assessments, system patch monitoring, and third party mailing lists and services.  Each vulnerability is reviewed to determine if it is applicable to Heroku’s environment, ranked based on risk, and assigned to the appropriate team for resolution.

New systems are deployed with the latest updates, security fixes, and Heroku configurations and existing systems are decommissioned as customers are migrated to the new instances. This process allows Heroku to keep the environment up-to-date. Since customer applications run in isolated environments, they are unaffected by these core system updates.

To further mitigate risk, each component type is assigned to a unique network security group. These security groups are designed to only allow access to the ports and protocols required for the specific component type. For example, user applications running within an isolated dyno are denied access to the Heroku management infrastructure as each is within its own network security group and access is not allowed between the two.

Heroku Application Security
We undergo penetration tests, vulnerability assessments, and source code reviews to assess the security of our application, architecture, and implementation. Our third party security assessments cover all areas of our platform including testing for OWASP Top 10 web application vulnerabilities and customer application isolation.  Heroku works closely with external security assessors to review the security of the Heroku platform and applications and apply best practices.

Issues found in Heroku applications are risk ranked, prioritized, assigned to the responsible team for remediation, and Heroku’s security team reviews each remediation plan to ensure proper resolution.

Backups
Customer Applications
Applications deployed to the Heroku platform are automatically backed up as part of the deployment process on secure, access controlled, and redundant storage.  We use these backups to deploy your application across our platform and to automatically bring your application back online in the event of an outage.

Customer Postgres Databases
Continuous Protection keeps data safe on Heroku Postgres. Every change to your data is written to write-ahead logs, which are shipped to multi-datacenter, high-durability storage. In the unlikely event of unrecoverable hardware failure, these logs can be automatically 'replayed' to recover the database to within seconds of its last known state. We also provide you with the ability to back up your database to meet your own backup and data retention requirements.

For additional technical information see: https://devcenter.heroku.com/articles/pgbackups

Customer Configuration and Meta-information
Your configuration and meta-information is backed up every minute to the same high-durability, redundant infrastructure used to store your database information. These frequent backups allow capturing changes made to the running application configuration added after the initial deployment.

Heroku Platform
From our instance images to our databases, each component is backed up to secure, access-controlled, and redundant storage.  Our platform allows for recovering databases to within seconds of the last known state, restoring system instances from standard templates, and deploying customer applications and data.  In addition to standard backup practices, Heroku’s infrastructure is designed to scale and be fault tolerant by automatically replacing failed instances and reducing the likelihood of needing to restore from backup.

Disaster Recovery
Customer Applications and Databases
Our platform automatically restores customer applications and Heroku Postgres databases in the case of an outage. The Heroku platform is designed to dynamically deploy applications within the Heroku cloud, monitor for failures, and recover failed platform components including customer applications and databases.

Heroku Platform
The Heroku platform is designed for stability, scaling, and inherently mitigates common issues that lead to outages while maintaining recovery capabilities.  Our platform maintains redundancy to prevent single points of failure, is able to replace failed components, and utilizes multiple data centers designed for resiliency. In the case of an outage, the platform is deployed across multiple data centers using current system images and data is restored from backups. Heroku reviews platform issues to understand the root cause, impact to customers, and improve the platform and processes.

Customer Data Retention and Destruction
You have the freedom to define what data your applications store and the ability to purge data from your databases to comply with your data retention requirements. If you deprovision an application and the associated database, we maintain the database’s storage volume for one week after which time its automatically destroyed rendering the data unrecoverable.

Decommissioning hardware is managed by our infrastructure provider using a process designed to prevent customer data exposure. AWS uses techniques outlined in DoD 5220.22-M (“National Industrial Security Program Operating Manual “) or NIST 800-88 (“Guidelines for Media Sanitization”) to destroy data.

For additional information see: https://aws.amazon.com/security

Privacy
Heroku has a published privacy policy that clearly defines what data is collected and how it is used. Heroku and Salesforce are committed to customer privacy and transparency.

We take steps to protect the privacy of our customers and protect data stored within the platform. Some of the protections inherent to Heroku’s products include authentication, access controls, data transport encryption, HTTPS support for customer applications, and the ability for customers to encrypt stored data. For additional information see: https://www.heroku.com/policy/privacy

Access to Customer Data
Heroku staff does not access or interact with customer data or applications as part of normal operations. There may be cases where Heroku is requested to interact with customer data or applications at the request of the customer for support purposes or where required by law. Customer data is access controlled and all access by Heroku staff is accompanied by customer approval or government mandate, reason for access, actions taken by staff, and support start and end time.

Employee Screening and Policies
As a condition of employment all Heroku and Salesforce employees undergo pre-employment background checks and agree to company policies including security and acceptable use policies.

Security Staff
Our security team is lead by the Chief Information Security officer (CISO) and includes staff responsible for application and information security. The security team works closely with the entire Heroku organization and customers to address risk and continue Heroku’s commitment to trust.

Customer Security Best Practices
Encrypt Data in Transit
Enable HTTPS for applications and SSL database connections to protect sensitive data transmitted to and from applications.

Encrypt Sensitive Data at Rest
Customers with sensitive data can encrypt stored files and data within databases to meet their data security requirements. Data encryption can be deployed using industry standard encryption and the best practices for your language or framework.

Secure Development Practices
Apply development best practices for your chosen development language and framework to mitigate known vulnerability types such as those on the OWASP Top 10 Web Application Security Risks.

Authentication
To prevent unauthorized account access use a strong passphrase for both your Heroku user account and SSH keys, store SSH keys securely to prevent disclosure, replace keys if lost or disclosed, and use Heroku’s RBAC model to invite contributors rather than sharing user accounts.

Logging
Logging is critical for troubleshooting and investigating issues. We provide you with three main options for interacting with their system, application, and API logs. Customers can receive all 3 types of logs via syslog from the Heroku platform, choose to send logs to a Heroku add-on, or interact with logs in real-time through the Heroku client.

For additional technical information see: https://devcenter.heroku.com/articles/logging

Use of Third-Party Solutions
In developing your application on Heroku you may choose to use third party services for added functionality such as Amazon’s S3, an email service provider, or any of our add-on partners. Be mindful of the data shared with these providers and their security practices just as you would be with Heroku.

submit bug report: https://www.eneco.com/responsible-disclosure/

Responsible Disclosure Statement
At Eneco Group we consider the security of our systems a top priority. Unfortunately, regardless of the effort we put in system security, vulnerabilities may still be present. If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like you to help us better protect our systems and the personal data entrusted to us by our customers and employees.

Please do the following
Submit your findings.
Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or by deleting or modifying other people’s data.
Do not reveal the problem to others until it has been resolved.
Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications to third parties.
Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually the IP-address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require additional information.
Submit your findings
What we promise
We will respond to your report in 5 working days with our evaluation of your report and an expected resolution date.
If you have followed the instructions above, we will not take any legal action against you in regard to the report.
We will not pass on your personal details to third parties without your permission, unless we are legally obliged to. Reporting under a pseudonym is possible.
We will keep you informed of the progress towards resolving the problem.
In the public information concerning the problem reported, we will give your name or pseudonym as the discoverer of the problem (unless you desire otherwise).

submit bug report: http://ecobee.com

About
We make wi-fi enabled smart thermostats for residential and commercial applications that are intuitive to use and beautiful to look at. We help you maximize comfort and savings without compromising your lifestyle.
Story
Before founding ecobee in 2007, Stuart Lombard was on a mission to reduce his family’s carbon footprint and save money. He found a lot of ways to conserve energy but most were complex and costly. However, he discovered that heating and cooling made up the majority of his home energy use. So, he tried a programmable thermostat. It turned out to be really complicated, even for someone with an engineering degree. And, unreliable. When Stuart and his family came home one winter day to find their house freezing, they'd had enough. He knew there had to be a better way and decided to build his own thermostat. A truly smart thermostat, that was easy to install, smart enough to deliver comfort, conserving energy and pay for itself in energy savings. That day, ecobee was born.
Reporting Criteria
Failure to meet these criteria will most likely result in an Informative or NA report:
Must include steps to reproduce the vulnerability
Must include a working Proof of Concept
NO: "Leaked keys"
YES: PoC showing how the leaked keys are used to gain access ...
Response Targets
We do not work on weekends - please be patient. If we require additional information from you, please allow for another 2-3 days for our team to review and respond.
Response Target   Time (in business days)
First response (from report submit)   2 days
Triage (from report submit)   2 days
Resolution   Depends on severity and complexity
Test Instructions for Application Testing
You MUST use your HackerOne email alias when registering for an ecobee account
You must ensure that vulnerabilities in mobile apps are submitted for the current version. Vulnerabilities in older versions which have since been remedied will be considered invalid.
If demonstrating a vulnerability regarding unauthorized access to a customer account. Please create a second account of your own, do not access accounts of customers who have not consented to this test.
Test Instructions for Hardware Testing
ecobee will not be providing test devices. If any customer or individual finds a vulnerability in an ecobee product, then he or she can safely report the details through this program.
Program Rules
Automated requests/scanning must be kept to 45 requests per minute. You run the risk of a program block/ban if you do not use your h1 email alias and send more than 45 requests per minute when testing.
Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the report may be closed as Informative.
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
When duplicates occur, we only triage the first report. All reports after the original will be closed as Duplicate. This includes the same bug being duplicated across several web properties, or between mobile apps.
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
Out of scope vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
Self XSS
Clickjacking on pages with no sensitive actions.
Unauthenticated/logout/login CSRF.
Attacks requiring MITM or physical access to a user's device.
Previously known vulnerable libraries without a working Proof of Concept.
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
Missing best practices in SSL/TLS configuration.
Any activity that could lead to the disruption of our service (DoS).
Content spoofing and text injection issues WITHOUT showing an attack vector/without being able to modify HTML/CSS
Brute force attacks
Flaws in third-party software for which there are no applicable patches.
Disclosure Policy
As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
Follow HackerOne's disclosure guidelines.
Safe Harbor
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep ecobee and our users safe!