US2018337975A1PendingUtilityA1

System and method for providing a secure network

43
Assignee: SURFDASHPriority: Sep 30, 2015Filed: Dec 18, 2017Published: Nov 22, 2018
Est. expirySep 30, 2035(~9.2 yrs left)· nominal 20-yr term from priority
H04L 67/06H04L 63/0807G06F 21/6227H04L 67/1097H04L 63/067G06F 21/44
43
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A method and system for providing a secure network. The system can have a URL programming interface, a server, and a database connected to the server. The server can be configured to receive requests from the URL programming interface. The server can include a file manager, an authentication server, a resource server, and a collaboration server.

Claims

exact text as granted — not AI-modified
1 . A secure network ecosystem, comprising:
 a URL programming interface;   a server configured to receive a request from the URL programming interface, wherein the server includes a file manager, an authentication server, a resource server, and a collaboration server; and   a secure database connected to the server.   
     
     
         2 . The system of  claim 1 , wherein the authentication server ensures that the request is valid. 
     
     
         3 . The system of  claim 1 , further comprising an application program interface configured to authenticate a token generated by the authentication server. 
     
     
         4 . The system of  claim 3 , wherein the request is an HTTP communication. 
     
     
         5 . The system of  claim 3 , wherein the request is an FTP communication. 
     
     
         6 . The system of  claim 1 , further comprising a second secure network ecosystem, wherein the second secure network ecosystem comprises:
 a second URL programming interface;   a second server; and   a second secure database connected to the second server;   wherein the second secure network ecosystem is configured to receive the request and an authentication request from the secure network ecosystem.   
     
     
         7 . The system of  claim 6 , wherein the second server determines whether the request is authorized based on a token generated by the authentication server. 
     
     
         8 . The system of  claim 3 , wherein the token has a lifetime of less than five minutes. 
     
     
         9 . The system of  claim 8 , wherein the token has a lifetime of less than two minutes. 
     
     
         10 . The system of  claim 1 , wherein the resource server includes a central repository of metadata. 
     
     
         11 . The system of  claim 10 , wherein the metadata is publicly available. 
     
     
         12 . The system of  claim 11 , wherein the metadata is associated with content, and wherein the content is not publicly available. 
     
     
         13 . The system of  claim 12 , wherein filenames associated with the content is not publicly visible. 
     
     
         14 . The system of  claim 11 , wherein the metadata is publicly searchable. 
     
     
         15 . The system of  claim 10 , wherein the resource server includes a token validator, a query engine, and a metadata manager. 
     
     
         16 . The system of  claim 1 , wherein data is stored on the secure database in a first normal form (1NF). 
     
     
         17 . The system of  claim 16 , wherein the data violates a third normal form (3NF). 
     
     
         18 . The system of  claim 1 , wherein the secure database is at least partially non-normalized. 
     
     
         19 . The system of  claim 18 , wherein the secure database contains content, and wherein filenames associated with the content are encrypted. 
     
     
         20 . The system of  claim 19 , wherein extensions associated with the content are encrypted. 
     
     
         21 .- 25 . (canceled)

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.