|
|
| (38 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| = Cloud Services Security = | | = Firefox Operations Security = |
| The CloudSec team is tasked with securing core Firefox services operated by the Cloud Services organization at Mozilla.
| | Firefox Operations Security is responsible for application & operations security for internal & external services and websites in the Firefox organization that host sensitive data or provide a mission critical service. |
| | |
| | [[File:Secops1024.png|400px|right]] |
|
| |
|
| == Contact == | | == Contact == |
| Email us at cloudsec@mozilla.com with the PGP key [http://gpg.mozilla.org/pks/lookup?op=get&search=0xF7A9B793541A953D Mozilla Cloud Services Security (CloudSec) 6F73539153B31C193A2154EAF7A9B793541A953D] | | Email us at secops@mozilla.com. |
|
| |
|
| To report a security issue on a given site, use the bug bounty form [https://www.mozilla.org/en-US/security/bug-bounty/faq-webapp/ as explained here]. | | To report a security issue on a given site, use the bug bounty form [https://www.mozilla.org/en-US/security/bug-bounty/faq-webapp/ as explained here]. |
| | |
| | To tell us about a new service create a [https://github.com/mozilla-services/foxsec/issues/new?template=NewService.md&labels=New%20Service&assignee=psiinon&title=New%20Service:%20 New Service issue]. |
|
| |
|
| __TOC__ | | __TOC__ |
|
| |
|
| == Backlog == | | == Product Lines == |
| | |
| The table below summarizes the open issues assigned to the CloudSec team, sorted by area of focus.
| |
| | |
| === Operational Security ===
| |
| {| class="wikitable"
| |
| |- style="vertical-align:bottom;"
| |
| ! style="height:100px; width:200px; text-align:center;" |
| |
| Continuous Testing (TDS)
| |
| ! style="height:100px; width:200px; text-align:center;" |
| |
| Fraud Detection
| |
| ! style="height:100px; width:200px; text-align:center;" |
| |
| User management
| |
| ! style="height:100px; width:200px; text-align:center;" |
| |
| Infra Hardening
| |
| ! style="height:100px; width:200px; text-align:center;" |
| |
| Threat monitoring
| |
| |-
| |
| | style="background-color: #d04437;"|
| |
| [https://github.com/mozilla-services/cloudsec/issues?q=is%3Aopen+is%3Aissue+label%3A"1.1+TDS" <span style="color:white;">'''1 HIGH'''<br />'''4 MEDIUM'''<br />'''6 LOW'''<br /></span>]
| |
| | style="background-color: #d04437;"|
| |
| [https://github.com/mozilla-services/cloudsec/issues?q=is%3Aopen+is%3Aissue+label%3A"1.2+fraud+detection" <span style="color:white;">'''2 HIGH'''<br />'''2 MEDIUM'''<br />'''2 LOW'''<br /></span>]
| |
| | style="background-color: #ffd351;"|
| |
| [https://github.com/mozilla-services/cloudsec/issues?q=is%3Aopen+is%3Aissue+label%3A"1.3+identity+management" <span style="color:black;">'''3 MEDIUM'''<br /></span>]
| |
| | style="background-color: #d04437;"|
| |
| [https://github.com/mozilla-services/cloudsec/issues?q=is%3Aopen+is%3Aissue+label%3A"1.4+infra+hardening" <span style="color:white;">'''1 HIGH'''<br />'''4 MEDIUM'''<br />'''3 LOW'''<br /></span>]
| |
| | style="background-color: #4a6785;"|
| |
| [https://github.com/mozilla-services/cloudsec/issues?q=is%3Aopen+is%3Aissue+label%3A"3.2+monitor+external+threats" <span style="color:white;">'''2 LOW'''<br /></span>]
| |
| |}
| |
|
| |
|
| === Application Security ===
| | * Firefox Accounts |
| {| class="wikitable"
| | * Addons.mozilla.org |
| |- style="vertical-align:bottom;"
| | * Browser services (sync, push, normandy, remote settings, balrog, product delivery, etc.) |
| ! style="height:100px; width:200px; text-align:center;" |
| | * Data services (telemetry, pioneer, taar, prio, etc.) |
| Risk & Security reviews
| | * Web presence of Premium services (FxSend, FxMonitor, FPN website, etc.) |
| ! style="height:100px; width:200px; text-align:center;" |
| | * Release Engineering (taskcluster, shipit, *.build.m.o, build infra, etc.) |
| Test & Implement Baseline Security
| | * Developer Services (phabricator, lando, bugzilla, sentry, crash reports, etc.) |
| ! style="height:100px; width:200px; text-align:center;" |
| |
| Data & Code Signing
| |
| ! style="height:100px; width:200px; text-align:center;" |
| |
| Training & Communication
| |
| ! style="height:100px; width:200px; text-align:center;" |
| |
| Bug Bounty
| |
| ! style="height:100px; width:200px; text-align:center;" |
| |
| External audits
| |
| |-
| |
| | style="background-color: #4a6785;"|
| |
| [https://github.com/mozilla-services/cloudsec/issues?q=is%3Aopen+is%3Aissue+label%3A"2.1+risk+assessment" <span style="color:white;">'''1 MEDIUM'''<br />'''3 LOW'''<br /></span>]
| |
| | style="background-color: #ffd351;"|
| |
| [https://github.com/mozilla-services/cloudsec/issues?q=is%3Aopen+is%3Aissue+label%3A"2.2+appsec+baseline" <span style="color:black;">'''2 MEDIUM'''<br />'''3 LOW'''<br /></span>]
| |
| | style="background-color: #4a6785;"|
| |
| [https://github.com/mozilla-services/cloudsec/issues?q=is%3Aopen+is%3Aissue+label%3A"3.1+signature" <span style="color:white;">'''1 MEDIUM'''<br />'''2 LOW'''<br /></span>]
| |
| | style="background-color: #4a6785;"|
| |
| [https://github.com/mozilla-services/cloudsec/issues?q=is%3Aopen+is%3Aissue+label%3A"2.3+security+communication" <span style="color:white;">'''1 MEDIUM'''<br />'''4 LOW'''<br /></span>]
| |
| | style="background-color: #4a6785;"|
| |
| [https://github.com/mozilla-services/cloudsec/issues?q=is%3Aopen+is%3Aissue+label%3A"2.4+bug+bounty" <span style="color:white;">'''1 LOW'''<br /></span>]
| |
| | style="background-color: #4a6785;"|
| |
| [https://github.com/mozilla-services/cloudsec/issues?q=is%3Aopen+is%3Aissue+label%3A"3.3+external+audits" <span style="color:white;">'''1 MEDIUM'''<br />'''1 LOW'''<br /></span>]
| |
| |}
| |
|
| |
|
| == Strategy == | | == Scope == |
|
| |
|
| === 1. Improve operational security of the core infrastructure === | | === Application security === |
| | Responsibility for internal & external services and websites in the Firefox organization that host sensitive data or provide a mission critical service. |
| | * Risk assessments |
| | * Security Reviews |
| | * Manual and automated testing |
| | * Review risks w/ product owners |
| | * Security incident management |
|
| |
|
| ==== 1.1 Implement Test Driven Security (TDS) in CI/CD ====
| | The application security group also owns cryptographic services (autograph, tls canary, tls observatory, etc) and appsec tooling (zap, dependency observatory, etc.). |
| Security tests should be part of the continuous integration (CI) and continuous delivery (CD) pipelines.
| |
| * CI integration should be part of the code commit/review process, either in an existing CI (travis-ci, circleci, taskcluster) or in a security dedicated one. CI tests should include static code analysis and recommendations, docker containers testing and dependency checks (vulnerability management).
| |
| * CD integration should be done at Jenkins' level, when stage environments are built and promoted.All services are regularly rebuilt by Jenkins. CD tests should include application vulnerability scanning (ZAProxy) and infrastructure access control tests (security groups, IAM permissions, ...).
| |
| TDS should output directly in the build pipeline at first, and allow dev & ops to control levels that block integration & delivery. In a second phase, TDS outputs should be aggregated into a central security tracking platform.
| |
|
| |
|
| ==== 1.2 Make use of the logging pipeline to detect fraud and anomalies ==== | | === Operations security === |
| Heka, ElasticSearch and Kafka are powerful tools on top of which we can plug various pattern detection mechanisms to identify known bad actors, or unusual behavior. Fraud detection is a highly requested feature that devs don’t want to rebuild every time. Fraud detection should operate autonomously for each service, taking into account business rules set by the developers and the security team.
| | Responsibility for infrastructure and hosting of Firefox services. |
| | * Covers the security of AWS and GCP infrastructure, and datacenters for the build infra |
| | * Security operations consulting for the Firefox organization at large |
|
| |
|
| ==== 1.3 Improve user management and authentication ====
| | The operations security group also owns the fraud pipeline (foxsec-pipeline) and secops tooling (frost, sops, etc.). |
| We should make better use of LDAP to add and remove employees from various third party services and admin panels.
| |
| * Admin panels should rely on Mozilla's Identity Management platform provided by IT
| |
| * Third-party services (datadog, pagerduty, aws) should have automated user management (userplex).
| |
| Cloudsec need to facilitate integration with Mozilla's IAM with standard libraries and tools.
| |
|
| |
|
| ==== 1.4 Harden the infrastructure ==== | | === Risk Management === |
| All services and tools that are part of the standard infrastructure should undergo security hardening. Hardening rules should be testable in the CD pipeline (see TDS above) to prevent security regressions. Some examples:
| | Responsibility for maintaining visibility into the security posture of the Firefox infrastructure. |
| * SSH should enforce MFA authentication | | * Rapid Risk Assessments framework & associated tooling |
| * Disabled users should be removed from all systems, particularly bastion hosts | | * Security posture reports & leadership reporting |
| * AWS permissions must prevent services from compromising each other
| |
| * Secrets must be provisioned encrypted
| |
| * ...
| |
| | |
| === 2. Increase security maturity ===
| |
| | |
| ==== 2.1 Help new projects identify threats and controls (RRA, threat models,...) ====
| |
| Risk assessment and threat modeling help people think through failure scenarios they wouldn’t evaluate otherwise. RRAs often leads to architectural changes that are best identified early. Each new project must undergo a 30/60min RRA with one of the member of cloudsec to assess the security posture of the project.
| |
| | |
| ==== 2.2 Implement baseline services security standards ====
| |
| Content Security Policy (CSP), HSTS, HPKP, data signature and encryption, input validation, XSS and SQLi protection are part of techniques developers should care about when building new services. Cloudsec defines services security standards that devs can implement and cloudsec tests in TDS.
| |
| | |
| ==== 2.3 Communicate security effectively throughout the organization ====
| |
| Teams need a channel to ask security questions, discuss concerns and share techniques. CloudSec must organize information flow and broadcast to developers, ops and managers. This includes general security best practices, analyzis and actions to take on CVE vulnerabilities, response and communication on incidents.
| |
| | |
| ==== 2.4 Use Mozilla’s bug bounty program ====
| |
| The bug bounty program is a fantastic tool: for a small amount of money, we reward people worldwide for helping us improve our security posture. Most security issues identified in our services come from the bug bounty program. We must ensure that all services are part of the bug bounty program and that triaging is performed regularly. As much as possible, we must assist developers in fixing security issues that are reported through bug bounties.
| |
| | |
| === 3. Build core security services ===
| |
| | |
| ==== 3.1 Sign data that changes the configuration of user agents ====
| |
| We iterate fast, and eventually someone, either us or a partner, is bound to make a mistake and open a door that could put our users at risk. Signing the data we send to our users helps cover that risk. Digital signature for Firefox is a complex topic - not every project can implement it independently - so cloudsec must provide the tooling and services to facilitate signing ([autograph](https://github.com/mozilla-services/autograph))
| |
| | |
| ==== 3.2 Monitor our ecosystem for external threats ====
| |
| There are many scenarios in which our users can be at risk because of the fraudulent or careless behavior of a third party. A bad certificate authority could issue a certificate that impersonates us. A careless partner could leak addon signing keys. A web startup could get hacked and leak web push endpoints. We should implement the tools needed to identify fraudulent behavior outside of our organization that impact us, so we can react in a timely manner and protect Firefox users.
| |
| | |
| ==== 3.3 Partner with external firms to monitor our security ====
| |
| We can’t do everything ourselves. External security firms can help us keep an eye on and audit our services. Some of their work may be redundant with current efforts, such as automated security testing, but would help cover the interim. We should evaluate various vendors and partner with the ones that have the best support of our technologies.
| |
|
| |
|
| == Security Checklist == | | == Security Checklist == |
|
| |
|
| See https://github.com/mozilla-services/cloudsec/blob/master/security_checklist.md
| | This has moved to https://github.com/mozilla-services/websec-check |
| | |
| The checklist below is in MARKDOWN format to be copy/pasted into Github issues.
| |
| | |
| <source lang:markdown>
| |
| Infrastructure rules
| |
| --------------------
| |
| | |
| * [ ] Use [Modern TLS](https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility) (**INFRA-TLS**)
| |
| * [ ] Set HSTS to 31536000 (1 year) (**INFRA-HSTS**)
| |
| * [ ] Set HPKP to 5184000 (60 days) (**INFRA-HPKP**)
| |
| * `Public-Key-Pins: max-age=300; pin-sha256="WoiWRyIOVNa9ihaBciRSC7XHjliYS9VwUGOIud4PB18="; pin-sha256="r/mIkG3eEpVdm+u/ko/cwxzOMo1bk4TyHIlByibiA5E="; report-uri="/__hpkpreport__";`
| |
| * Start with max-age set to 5 minutes and increase gradually
| |
| * Pin to the EV and DV roots of Digicert
| |
| * Set a reporting endpoint `/__hpkpreport__` to catch violations in nginx ([example conf](https://github.com/mozilla-services/puppet-config/blob/HEAD/amo/modules/amo_proxy/templates/nginx.hpkpreport.conf.erb))
| |
| * If service has an admin panels, it must:
| |
| * [ ] only be available behind Mozilla VPN (which provides MFA) (**INFRA-ADMINVPN**)
| |
| * [ ] require LDAP authentication (**INFRA-ADMINLDAP**)
| |
| * [ ] enforce a two-man rule on sensitive changes (**INFRA-2MANRULE**)
| |
| | |
| Coding rules
| |
| ------------
| |
| | |
| The following rules apply to all web applications: api and websites.
| |
| | |
| * [ ] Sign all commits (**APP-COMMITSIG**)
| |
| * Developers should [configure git to sign all commits](http://micropipes.com/blog//2016/08/31/signing-your-commits-on-github-with-a-gpg-key/) and upload their PGP fingerprint to https://login.mozilla.com
| |
| | |
| * [ ] Detailed logging in mozlog format (**APP-MOZLOG**)
| |
| * Business logic must be logged with app specific codes (errno)
| |
| * Access control failures must be logged at WARN level
| |
| | |
| * [ ] All SQL queries must be parameterized, not concatenated (**APP-SQL**)
| |
| * [ ] User data must be escaped for the right context prior to reflecting it (**APP-ESCAPE**)
| |
| * [ ] Apply sensible limits to user inputs, see [input validation](https://wiki.mozilla.org/WebAppSec/Secure_Coding_Guidelines#Input_Validation) (**APP-INPUTVAL**)
| |
| * [ ] Enforce Access Controls server-side (**APP-ACL**)
| |
| * [ ] Set the Secure flag on [Cookies](https://wiki.mozilla.org/Security/Guidelines/Web_Security#Cookies), and use sensible Expiration and HTTPOnly (**APP-SECCOOKIE**)
| |
| * Keep 3rd-party libraries up to date (**APP-DEPS**)
| |
| * [ ] Use [NSP](https://nodesecurity.io/) or [GreenKeeper](https://greenkeeper.io/ Greenkeeper) for NodeJS applications
| |
| * [ ] Use pip --outdated or [requires.io](https://requires.io/) for Python applications
| |
| * [ ] If handling cryptographic keys, must have a mechanism to handle monthly key rotations (**APP-KEYROT**)
| |
| * [ ] All keys must be rotated quarterly.
| |
| * Keys used to sign sessions don't need a rotation mechanism if destroying all sessions is acceptable during.
| |
| | |
| ### Additional websites requirements
| |
| | |
| The following coding rules only apply to websites, not web apis.
| |
| | |
| * [ ] Never store passwords, use Firefox Accounts (**APP-IDP**)
| |
| * [ ] Forbid Mixed content, always use HTTPS (**APP-MIXCONTENT**)
| |
| * [ ] Must have a CSP with (**APP-CSP**)
| |
| * [ ] a report-uri pointing to the service /__cspreport__
| |
| * [ ] frame-options set to deny
| |
| * [ ] no use of unsafe-inline or unsafe-eval
| |
| * [ ] Must have CSRF tokens and manually excluded specific forms (**APP-CSRF**)
| |
| * [ ] Should consider having checksums for 3rd-party content via SRI (**APP-SRI**).
| |
| * Trusted 3rd parties, like Google Analytics, don't need SRI. Use your best judgment to decide if a 3rd party script is trustworthy (and assume it is not).
| |
| * Consider Security headers as appropriate (**APP-HEADERS**)
| |
| * [ ] X-Content-Type-Options
| |
| * [ ] X-Frame-Options
| |
| * [ ] X-XSS-Protection
| |
| | |
| Data rules
| |
| ----------
| |
| | |
| * When storing sensitive user data (like browsing history) on Mozilla servers:
| |
| * [ ] Anonymize it (similar to Tiles) (**DATA-ANON**)
| |
| * [ ] Encrypt it client-side (similar to Sync) (**DATA-CRYPT**)
| |
| * [ ] If user data must be stored non-anonymized and in clear text, you must talk to the security and legal teams about it.
| |
| * If the service pushes data to Firefox, like when distributing blacklists or pushing updates, cryptographic signatures must be used. (**DATA-SIGN**)
| |
| * [ ] Addons must use standard AMO signing (**APP-SIGNING**)
| |
| * [ ] Code & Conf must use Content-Signature via
| |
| [Autograph](https://github.com/mozilla-services/autograph) (**DATA-SIGNING**)
| |
| </source>
| |
| | |
| == Sites and Services ==
| |
| | |
| CloudSec is responsible for the security of the following websites and backend services.
| |
| | |
| (note: cloudsec is not responsible for the security of implementations in firefox, only of the backend services).
| |
| | |
| === ABSearch ===
| |
| Code: [https://github.com/mozilla-services/absearch absearch]
| |
| | |
| Public Endpoints:
| |
| * search.services.mozilla.com
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Addons.mozilla.org ===
| |
| Code:
| |
| * [https://github.com/mozilla/addons-frontend addons-frontend]
| |
| * [https://github.com/mozilla/addons-server/ addons-server]
| |
| * [https://github.com/mozilla/addons-linter addons-linter]
| |
| | |
| Public Endpoints:
| |
| * addon.mozilla.org
| |
| * addons.mozilla.org
| |
| * blocklist.addons.mozilla.org
| |
| * builder.addons.mozilla.org
| |
| * controller-review.apk.firefox.com
| |
| * controller.apk.firefox.com
| |
| * services.addons.mozilla.org
| |
| * static.addons.mozilla.net
| |
| * versioncheck-bg.addons.mozilla.org
| |
| * versioncheck.addons.mozilla.org
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Product Delivery ===
| |
| Code: [https://github.com/mozilla-services/go-bouncer go-bouncer]
| |
| | |
| Public Endpoints:
| |
| * download-installer.cdn.mozilla.net
| |
| * download.mozilla.org
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === AUS/Balrog ===
| |
| Code: [https://github.com/mozilla/balrog/ balrog]
| |
| | |
| Public Endpoints:
| |
| * aus3.mozilla.org
| |
| * aus4.mozilla.org
| |
| * aus5.mozilla.org
| |
| * aus.mozilla.org
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Firefox Accounts ===
| |
| Code:
| |
| * [https://github.com/mozilla/fxa fxa]
| |
| * [https://github.com/mozilla/fxa-auth-server fxa-auth-server]
| |
| * [https://github.com/mozilla/fxa-content-server fxa-content-server]
| |
| * [https://github.com/mozilla/fxa-js-client fxa-js-client]
| |
| * [https://github.com/mozilla/fxa-oauth-server fxa-oauth-server]
| |
| * [https://github.com/mozilla/fxa-customs-server/ fxa-customs-server]
| |
| | |
| Public Endpoints:
| |
| * accounts.firefox.com
| |
| * api.accounts.firefox.com
| |
| * oauth.accounts.firefox.com
| |
| * profile.accounts.firefox.com
| |
| * verifier.accounts.firefox.com
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Firefox Sync ===
| |
| Code:
| |
| * [https://github.com/mozilla-services/syncserver syncserver]
| |
| * [https://github.com/mozilla-services/tokenserver tokenserver]
| |
| | |
| Public Endpoints:
| |
| * *.$region.sync.services.mozilla.com
| |
| * token.services.mozilla.com
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Firefox Hello ===
| |
| Code: [https://github.com/mozilla-services/loop-server loop-server]
| |
| | |
| Public Endpoints:
| |
| * hello.firefox.com
| |
| * loop.services.mozilla.com
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Location (MLS) ===
| |
| Code:
| |
| * [https://github.com/mozilla/ichnaea ichnaea]
| |
| * [https://github.com/mozilla-services/location-leaderboard location-leaderboard]
| |
| | |
| Public Endpoints:
| |
| * location.services.mozilla.com
| |
| * location-leaderboard.services.mozilla.com
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Marketplace.firefox.com ===
| |
| Code: [https://github.com/mozilla/zamboni zamboni]
| |
| | |
| Public Endpoints:
| |
| * marketplace.firefox.com
| |
| * receiptcheck.marketplace.firefox.com
| |
| * static.marketplace.firefox.com
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Persona ===
| |
| Code: [https://github.com/mozilla/persona persona]
| |
| | |
| Public Endpoints:
| |
| * browserid.org
| |
| * firefoxos.persona.org
| |
| * persona.org
| |
| * static.login.persona.org
| |
| * verifier.login.persona.org
| |
| * www.browserid.org
| |
| * www.persona.org
| |
| * yahoo.login.persona.org
| |
| * gmail.login.persona.org
| |
| * login.anosrep.org
| |
| * login.mozilla.org
| |
| * login.persona.org
| |
| * diresworb.org
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Push ===
| |
| Code:
| |
| * [https://github.com/mozilla-services/autopush autopush]
| |
| * [https://github.com/mozilla-services/push-dev-dashboard push-dev-dashboard]
| |
| | |
| Public Endpoints:
| |
| * push.services.mozilla.com
| |
| * updates.push.services.mozilla.com
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Security Settings (Kinto) ===
| |
| Code: TBD
| |
| | |
| Public Endpoints:
| |
| * settings.services.mozilla.com
| |
| | |
| In Bounty Scope? No
| |
| | |
| === Shield / Normandy ===
| |
| Code:
| |
| * [https://github.com/mozilla/normandy normandy]
| |
| | |
| Public Endpoints: TBD
| |
| | |
| In Bounty Scope? No
| |
| | |
| === Telemetry ===
| |
| Code:
| |
| * [https://github.com/mozilla/telemetry-server telemetry-server]
| |
| * [https://github.com/mozilla/telemetry-dashboard/ telemetry-dashboard]
| |
| | |
| Public Endpoints:
| |
| * incoming.telemetry.mozilla.org
| |
| * telemetry-experiment.cdn.mozilla.net
| |
| * analysis.telemetry.mozilla.org
| |
| * sql.telemetry.mozilla.org
| |
| * metrics.services.mozilla.com
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Test Pilot ===
| |
| Code: [https://github.com/mozilla/testpilot testpilot]
| |
| | |
| Public Endpoints:
| |
| * http://testpilot.firefox.com/
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Tiles ===
| |
| Code: [https://github.com/mozilla/splice splice]
| |
| | |
| Public Endpoints:
| |
| * tiles.cdn.mozilla.net
| |
| * tiles.services.mozilla.com
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === TLS Observatory ===
| |
| Code: [https://github.com/mozilla/tls-observatory tls-observatory]
| |
| | |
| Public Endpoints:
| |
| * tls-observatory.services.mozilla.com
| |
| | |
| In Bounty Scope? No
| |
| | |
| === Tracking Protection ===
| |
| Code: [https://github.com/mozilla-services/shavar shavar]
| |
| | |
| Public Endpoints:
| |
| * shavar.services.mozilla.com
| |
| * tracking.services.mozilla.com
| |
| | |
| In Bounty Scope? Yes
| |
| | |
| === Everything.me ===
| |
| In Bounty Scope? No
| |
|
| |
|
| === Find My Device === | | == About the logo == |
| Code: [https://github.com/mozilla-services/FindMyDevice find my device]
| |
|
| |
|
| In Bounty Scope? No
| | The Firefox Operations Security logo is derived [https://github.com/synthagency/icons-flat-osx/blob/master/SVG/Apps-Firefox.svg from this work by Synth Agency], and published under Creative Commons Attribution-NonCommercial 4.0 International Public License. |