Method, apparatus, and computer program product for encryption key management within a group-based communication system

US10778419B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10778419-B2
Application numberUS-201916434097-A
CountryUS
Kind codeB2
Filing dateJun 6, 2019
Priority dateJun 6, 2018
Publication dateSep 15, 2020
Grant dateSep 15, 2020

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Various embodiments are directed to systems and methods for encryption key management within a group-based communication platform.

First claim

Opening claim text (preview).

What is claimed is: 1. An apparatus for providing encryption key management, the apparatus capable of communicating with one or more servers of a communication system, the apparatus comprising at least one processor and at least one non-transitory memory storing instructions that, when executed by the processor, configure the apparatus to: provide, to the one or more servers, access to one or more encryption keys provided by a key material source, the encryption keys for accessing data managed by the communication system; wherein access to encryption keys is revocable on a per keyscope component basis wherein any encryption key associated with a revoked keyscope component is rendered invalid by the key material source, wherein a keyscope component is associated with an encryption key and is one or more of a timestamp, a user identifier, a message identifier, a file identifier, group-based communication channel identifier, a group-based communication team identifier, or a group-based communication workspace identifier; and provide encrypted plaintext or decrypted ciphertext to the one or more servers, using the one or more encryption keys provided by the key material source, wherein the plaintext comprises one or more of group-based communication message plaintext, group-based communication file plaintext, or a group-based communication search index encryption key. 2. The apparatus of claim 1 , wherein the at least one processor and at least one non-transitory memory stores instructions that, when executed by the processor, further configure the apparatus to: provide, to the one or more servers, access to one or more encryption keys stored in at least one local memory, the encryption keys for accessing data managed by the communication system. 3. The apparatus of claim 1 , wherein the decrypted ciphertext comprises one or more of decrypted group-based communication message ciphertext, decrypted group-based communication file ciphertext, or a decrypted group-based communication search index encryption key. 4. A computer implemented method for providing encryption key management, comprising: providing, to one or more servers of a communication system, access to one or more encryption keys provided by a key material source, the encryption keys for accessing data managed by the communication system; wherein access to encryption keys is revocable on a per keyscope component basis wherein any encryption key associated with a revoked keyscope component is rendered invalid by the key material source, wherein a keyscope component is associated with an encryption key and is one or more of a timestamp, a user identifier, a message identifier, a file identifier, group-based communication channel identifier, a group-based communication team identifier, or a group-based communication workspace identifier; and providing encrypted plaintext or decrypted ciphertext to the one or more servers, using the one or more encryption keys provided by the key material source, wherein the plaintext comprises one or more of group-based communication message plaintext, group-based communication file plaintext, or a group-based communication search index encryption key. 5. The computer implemented method of claim 4 , further comprising: providing, to the one or more servers, access to one or more encryption keys stored in at least one local memory, the encryption keys for accessing data managed by the communication system. 6. The computer implemented method of claim 4 , wherein the decrypted ciphertext comprises one or more of decrypted group-based communication message ciphertext, decrypted group-based communication file ciphertext, or a decrypted group-based communication search index encryption key.

Assignees

Inventors

Classifications

  • involving a third party or a trusted authority · CPC title

  • using a plurality of keys or algorithms · CPC title

  • Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage · CPC title

  • Revocation or update of secret information, e.g. encryption key update or rekeying · CPC title

  • H04L9/0861Primary

    Generation of secret information including derivation or calculation of cryptographic keys or passwords · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10778419B2 cover?
Various embodiments are directed to systems and methods for encryption key management within a group-based communication platform.
Who is the assignee on this patent?
Slack Tech Inc
What technology area does this patent fall under?
Primary CPC classification H04L9/0861. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Sep 15 2020 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 4 related publications on this page (citations in our corpus or others sharing the same primary CPC).