Vulnerabilities are an inevitable reality of software development. New CVEs are published daily, dependencies introduce risks, and application code can contain flaws. What matters is having a systematic process to find, prioritize, and fix vulnerabilities before they can be exploited. This article describes BttrForm's vulnerability management program.
Dependency Scanning
BttrForm's codebase depends on hundreds of open-source packages. Each dependency is a potential source of vulnerabilities. We run automated dependency scanning to catch known issues as early as possible.
Automated Daily Scans
- Dependabot monitors all
package.jsonfiles across the monorepo and automatically opens pull requests when vulnerable dependencies are detected. - Snyk provides a second layer of scanning with deeper analysis, including transitive dependency vulnerabilities that Dependabot may miss.
- Scans run daily against the latest vulnerability databases (NVD, GitHub Advisory Database, Snyk Vulnerability DB).
How We Handle Findings
1. Vulnerability detected in dependency
2. Severity assessed (Critical / High / Medium / Low)
3. Automated PR created with patched version (if available)
4. Engineering reviews PR for compatibility
5. PR merged and deployed according to patch SLA
6. If no patch available, mitigation applied (WAF rule, code workaround)
Transitive Dependencies
Penetration Testing
Automated scanning catches known vulnerabilities, but it cannot find business logic flaws, complex attack chains, or novel vulnerabilities. BttrForm engages third-party security firms to conduct penetration tests.
Testing Schedule
| Test Type | Frequency | Scope |
|---|---|---|
| Full application penetration test | Annually | All endpoints, authentication, authorization, data handling |
| API security assessment | Annually | REST API, webhook endpoints, file upload handling |
| Infrastructure assessment | Annually | Network configuration, cloud security, container security |
| Targeted assessment | As needed | New features, major architectural changes |
What Pen Testers Evaluate
- Authentication and session management -- Can an attacker bypass login, hijack sessions, or escalate privileges?
- Authorization and access control -- Can a user access another user's data through API manipulation or parameter tampering?
- Input validation -- Are forms, APIs, and file uploads vulnerable to injection attacks (SQL, XSS, command injection)?
- Business logic -- Can an attacker manipulate workflows, bypass billing, or abuse features in unintended ways?
- Infrastructure -- Are servers, databases, and network configurations hardened against attack?
Remediation
All findings from penetration tests are triaged, prioritized, and fixed according to the CVE patch SLAs described below. Critical and high findings are addressed before the penetration test report is finalized.
Reports Available on Request
CVE Patch SLAs
BttrForm maintains strict Service Level Agreements for patching known vulnerabilities, measured from the time a vulnerability is confirmed to affect our systems.
| Severity | CVSS Score | Patch Deadline | Examples |
|---|---|---|---|
| Critical | 9.0 -- 10.0 | 24 hours | Remote code execution, authentication bypass, SQL injection |
| High | 7.0 -- 8.9 | 72 hours | Privilege escalation, significant data exposure, XSS with high impact |
| Medium | 4.0 -- 6.9 | 7 days | Limited data exposure, denial of service, low-impact XSS |
| Low | 0.1 -- 3.9 | 30 days | Information disclosure with minimal impact, cosmetic security issues |
Patch Process
- Confirm applicability -- Verify the CVE affects BttrForm's specific configuration and usage of the component.
- Assess impact -- Determine the real-world risk in BttrForm's context (a critical CVE in an unused feature may be lower priority).
- Apply patch -- Update the affected dependency or apply a code fix.
- Test -- Run the full test suite, including security-specific tests, to verify the patch does not break functionality.
- Deploy -- Push the fix to production within the SLA window.
- Verify -- Confirm the vulnerability is no longer exploitable in the production environment.
Zero-Day Vulnerabilities
Responsible Disclosure Program
BttrForm welcomes reports from security researchers who discover vulnerabilities in our platform. We operate a responsible disclosure program to ensure vulnerabilities are reported safely and fixed promptly.
How to Report a Vulnerability
Send your report to security@bttrlabs.com with the following information:
- Description of the vulnerability
- Steps to reproduce (including URLs, parameters, and payloads)
- Impact assessment (what an attacker could achieve)
- Screenshots or proof-of-concept code (if applicable)
- Your contact information for follow-up
Scope
The following are in scope for our responsible disclosure program:
- BttrForm web application (app.bttrform.com)
- BttrForm API (api.bttrform.com)
- BttrForm marketing site (bttrform.com)
- BttrForm embed widget
- Authentication and session management
- Data access and authorization
The following are out of scope:
- Social engineering attacks against BttrForm employees
- Physical security of BttrForm offices or data centers
- Denial of service (DoS/DDoS) attacks
- Vulnerabilities in third-party services that BttrForm integrates with
- Issues that require unlikely user interaction (e.g., self-XSS)
Our Commitments
- Acknowledgment within 2 business days of receiving your report.
- Triage and assessment within 5 business days.
- Status updates at least every 10 business days until resolution.
- No legal action against researchers acting in good faith within the scope of this program.
- Credit in our security acknowledgments page (if you wish).
Rewards
BttrForm offers rewards for qualifying vulnerability reports based on severity:
| Severity | Reward Range |
|---|---|
| Critical | $500 -- $2,000 |
| High | $200 -- $500 |
| Medium | $50 -- $200 |
| Low | Recognition |
Reward amounts depend on the quality of the report, the impact of the vulnerability, and whether it is a duplicate of a known issue.
Security Headers
BttrForm configures HTTP security headers on all responses to protect against common web attacks.
| Header | Value | Purpose |
|---|---|---|
| Content-Security-Policy | Strict policy limiting script and resource origins | Prevents XSS and data injection |
| Strict-Transport-Security | max-age=31536000; includeSubDomains | Forces HTTPS for all connections |
| X-Content-Type-Options | nosniff | Prevents MIME type sniffing |
| X-Frame-Options | DENY | Prevents clickjacking via iframes |
| X-XSS-Protection | 0 (disabled, CSP preferred) | Legacy header, CSP provides better protection |
| Referrer-Policy | strict-origin-when-cross-origin | Limits referrer information leakage |
| Permissions-Policy | Restricts camera, microphone, geolocation | Limits browser feature access |
Verifying Headers
curl -I https://app.bttrform.com to see the response headers.Infrastructure Security
BttrForm's infrastructure is designed with defense in depth -- multiple overlapping layers of security so that no single failure compromises the system.
Network Architecture
- Private subnets -- Database servers and internal services run in private subnets with no direct internet access. Only application servers in public subnets can reach them.
- Firewall rules -- Network security groups restrict traffic to only the ports and protocols required for each service.
- VPN access -- Administrative access to infrastructure requires VPN connection with multi-factor authentication.
Web Application Firewall (WAF)
A WAF sits in front of all BttrForm endpoints and filters malicious traffic:
- SQL injection attempt detection and blocking
- Cross-site scripting (XSS) payload filtering
- Path traversal attack prevention
- Rate limiting on authentication endpoints
- Geographic blocking (configurable per customer on Enterprise plans)
DDoS Protection
- Layer 3/4 protection -- Network-level DDoS mitigation provided by our cloud infrastructure, capable of absorbing volumetric attacks.
- Layer 7 protection -- Application-level rate limiting and traffic analysis to detect and mitigate sophisticated application-layer attacks.
- Auto-scaling -- Infrastructure automatically scales to handle traffic spikes, whether legitimate or malicious.
Uptime
Was this helpful?