StrikeForce Technologies, Inc. Patent litigation record

Company 14 cases

14 cases on record naming StrikeForce Technologies, Inc.: 12 as claimant, 2 as respondent. Each row links to that case’s full docket record.

Profile this company in Eureka
Litigation indexPatsnap Litigation Data··Docket source: PACER

14 cases on record

Cases on record
14
As claimant
12
As respondent
2
Patents held
Not recorded
Core tech
G06F7/04 · G06F21/00 · H04L29/06 · G06F21/42
Case no.PartiesRoleCourtFiledDurationOutcome
19-103 StrikeForce Technologies, Inc. v. Secureauth Corporation Plaintiff U.S. Supreme Court 22 Jul 2019 77 d Appeal Denied
2018-1470 StrikeForce Technologies, Inc. v. Secureauth, Corp. Plaintiff Fed. Cir. 24 Jan 2018 391 d Closed
2:17-cv-04294 Entrust, Inc. v. StrikeForce Technologies, Inc. Defendant D.N.J. 13 Jun 2017 128 d Out-of-court Settlement
2:17-cv-04314 StrikeForce Technologies, Inc. v. Secureauth, Corp. Plaintiff C.D. Cal. 9 Jun 2017 202 d Judgment on the Merits
1:17-cv-00309 StrikeForce Technologies, Inc. v. Entrust, Inc. Plaintiff E.D. Va. 17 Mar 2017 245 d Likely Settlement
1:17-cv-00307 StrikeForce Technologies, Inc. v. Secureauth Corporation Plaintiff E.D. Va. 16 Mar 2017 85 d MDL Transfer
1:17-cv-10422 StrikeForce Technologies, Inc. v. Gemalto, Inc. Plaintiff D. Mass. 14 Mar 2017 778 d Voluntary dismissal
1:17-cv-10423 StrikeForce Technologies, Inc. v. Vasco Data Security International, Inc. Plaintiff D. Mass. 14 Mar 2017 763 d Likely Settlement
2:16-cv-03571 StrikeForce Technologies, Inc. v. Duo Security Incorporated Plaintiff D.N.J. 20 Jun 2016 1232 d Voluntary dismissal
2:16-cv-03573 StrikeForce Technologies, Inc. v. Trustwave Holdings, Inc. Plaintiff D.N.J. 20 Jun 2016 534 d Likely Settlement
2:16-cv-03574 StrikeForce Technologies, Inc. v. Centrify Corporation Plaintiff D.N.J. 20 Jun 2016 1233 d Voluntary dismissal
2:14-cv-01809 StrikeForce Technologies, Inc. v. Authentify Patent Co., LLC Plaintiff W.D. Wash. 21 Nov 2014 132 d Likely Settlement
2:13-cv-00741 Authentify Patent Co., LLC v. StrikeForce Technologies, Inc. Defendant W.D. Wash. 26 Apr 2013 705 d Likely Settlement
1:13-cv-00490 StrikeForce Technologies, Inc. v. PhoneFactor, Inc. Plaintiff D. Del. 28 Mar 2013 1028 d Out-of-court Settlement
Source: Patsnap Litigation Data. Cases naming StrikeForce Technologies, Inc. in the current snapshot. Run this in Eureka
Patsnap Eureka

See what StrikeForce Technologies is protecting

Portfolio, claim scope and where its coverage is thin. Every answer cites the records behind it.

Analyse this portfolio
10,000 free credits to start

About this summary. This page summarises the litigation records within the coverage and snapshot dates stated here. Counts describe records in that dataset and do not, by themselves, establish the conduct, litigation success or legal position of any person or organisation.

Docket data has limits. Records are drawn from a snapshot and may lag the live docket. Sealed filings, amended complaints, counterclaims and post-closure motions may not be reflected. Party names, attorney names and firm affiliations are reproduced as recorded and may contain omissions. Where a field is absent from the record, this page marks it as not recorded rather than inferring a value.

No characterisation of the parties or the outcome. This page reports what the record contains. Nothing here should be read as an assertion that any party infringed, that any patent is valid or invalid, that any settlement occurred, or that any party prevailed. The filing of a claim is not a court finding, and a docket marked “closed” does not by itself establish infringement, validity, settlement or a decision on the merits.

No FTO or validity opinion. Nothing on this page constitutes a freedom-to-operate, novelty, validity or infringement opinion. Any decision touching a live patent dispute should be verified independently and reviewed with qualified patent counsel.

Third-party names and marks. Party, attorney, judge and company names appear for identification only. Company names may be trademarks of their owners; their appearance does not, by itself, imply affiliation with or endorsement by Patsnap.

Corrections and privacy requests. To report an inaccurate record or attribution, use the “Report an incorrect record” link on this page. For requests concerning your personal information, including, where applicable, the rights to access, rectify, erase, restrict or object to processing, use the “Privacy request” link. We assess requests under applicable law. See our Privacy Policy for details of this processing.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.