Opposition · USPTO

Opposition 91304417

OtherUSPTO

Opposition 91304417 at USPTO between CRA International, Inc. and Cyberrisk Alliance, LLC, over the mark INFOSEC WORLD A CRA RESOURCE, filed Jan 13, 2026. Status in the office record: other.

Status
Other
Result
Other
Filed
Jan 13, 2026
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

CRA International, Inc.

Company trademarks
Respondent

Cyberrisk Alliance, LLC

Timeline

How the case has moved

Dates from the USPTO record and the INFOSEC WORLD A CRA RESOURCE filing.

  1. INFOSEC WORLD A CRA RESOURCE filed

    Application 98794784 filed at the USPTO.
  2. Opposition filed

    CRA International, Inc. started opposition 91304417 at USPTO against INFOSEC WORLD A CRA RESOURCE.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
INFOSEC WORLD A CRA RESOURCEContested98794784USPTO
CRARelied on72261919USPTO
CRARelied on74019567USPTO
CRARelied on74019568USPTO
CRARelied on74019569USPTO
CRARelied on74019570USPTO
CRA INSIGHTSRelied on77428473USPTO
CRA INSIGHTSRelied on77441714USPTO
CRARelied on87776734USPTO
CRARelied on87779406USPTO
API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

GET /v1/proceedings/{id}
ID=prc_9431036b-80f5-44af-849b-594d859458bd
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_9431036b-80f5-44af-849b-594d859458bd",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91304417",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-01-13",
  "parties": [
    {
      "name": "CRA International, Inc.",
      "role": "opponent"
    },
    {
      "name": "CYBERRISK ALLIANCE, LLC",
      "role": "respondent"
    }
  ]
}