Introduction

First Federal Bank of Kansas City is committed to ensuring the security of our customers by protecting their information. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to describe our preferences on how to submit discovered vulnerabilities to us.

This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.

We welcome security researchers who act in good faith to contact us and report any potential vulnerabilities in our systems. This policy reflects our commitment to collaborating with researchers who share their knowledge and expertise with us in an ethical, constructive and responsible manner.

Authorization

If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and First Federal Bank of Kansas City will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.

Guidelines

Under this policy, “research” means activities in which you:

• Notify us as soon as possible after you discover a real or potential security issue.
• Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
• Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
• Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
• Do not submit a high volume of low-quality reports, or use automated tools to contact us or submit reports.
• Do not retain or intentionally compromise the data, intellectual property, or other commercial or financial interests of First Federal Bank of Kansas City.
• Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.

Test methods

The following test methods are not authorized:

• Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
• Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing

Scope

Only systems and services associated with the base domain of www.ffbkc.com are in scope. Vulnerabilities found in systems from our vendors or subdomains fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any). If you aren’t sure whether a system or endpoint is in scope or not, contact webdevelopment@ffbkc.com before starting your research.

We ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us at webdevelopment@ffbkc.com to discuss it first. We will monitor the scope of this policy over time.

Rules of Engagement

Security researchers are prohibited from:

• Testing any systems other than those listed in the 'Scope' section above.
• Disclosing vulnerability information, except as specified in the 'Reporting a Vulnerability' and 'Disclosure' sections below.
• Performing physical testing on facilities or resources.
• Engaging in social engineering activities.
• Sending unsolicited emails to FFBKC users, including phishing attempts.
• Launching or attempting to launch "Denial of Service" or "Resource Exhaustion" attacks.
• Introducing malicious software into FFBKC systems.
• Conducting tests that could degrade the performance of FFBKC systems, or intentionally disrupt, damage, or disable FFBKC systems.
• Deleting, modifying, sharing, retaining, or destroying FFBKC data, or making it inaccessible.
• Using exploits to exfiltrate data, gain command-line access, establish a persistent presence, or "pivot" to other FFBKC systems.
• Security researchers are required to:
• Immediately stop testing and notify us upon discovering a vulnerability.
• Immediately stop testing and notify us upon discovering an exposure of nonpublic data.
• Purge any stored FFBKC nonpublic data after reporting a vulnerability.

Reporting a vulnerability

Information submitted under this policy will be used for defensive purposes only – to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely First Federal Bank of Kansas City, we may share your report with the Cybersecurity and Infrastructure Security Agency, where it will be handled under their coordinated vulnerability disclosure process. We will not share your name or contact information without express permission.

We accept vulnerability reports at this form or via webdevelopment@ffbkc.com. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days. We do not support PGP-encrypted emails at this time. By submitting a report, you confirm that you have read, understood, and agreed to the guidelines outlined in this policy regarding the conduct of security research and the disclosure of vulnerabilities or potential vulnerabilities related to FFBKC information systems.

What we would ask from you

• In order to help us triage and prioritize submissions, we recommend that your reports:
• Describe the location the vulnerability was discovered and the potential impact of exploitation.
• Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
• Be in English, if possible.

What you can expect from us

When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.

Within 3 business days, we will acknowledge that your report has been received.

To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.

We will maintain an open dialogue to discuss issues.

Disclosure

First Federal Bank of Kansas City is dedicated to promptly addressing vulnerabilities. Since publicly disclosing a vulnerability before a corrective action is available tends to increase risk, we ask that you refrain from disclosing information about identified vulnerabilities for 90 calendar days after we confirm receipt of your report. If you believe it is necessary to inform others about the vulnerability before we implement corrective measures, we request that you coordinate with us in advance.

We may share vulnerability reports with the Cybersecurity and Infrastructure Security Agency (CISA) and any impacted vendors. We will not disclose the names or contact information of security researchers without explicit consent.

Acknowledgments

We do not offer financial compensation, but we do allow for public recognition of anyone who helps us to ensure our systems and data are secure. We will not name you without your consent. If a public endorsement is appropriate, we will discuss the details with you in advance.

Questions

Questions regarding this policy may be sent to webdevelopment@ffbkc.com.

By submitting a vulnerability, you acknowledge that you have read and understand the above Vulnerability Disclosure Policy and that you have no expectation of payment and waive any future pay claims against FFBKC related to your submission.