Difference between revisions of "SUNScholar/Internet Security"
Jump to navigation
Jump to search
*** Originally the internet was not designed to be secure ***
m |
m (→References) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
</center> | </center> | ||
| − | <center><font color="red"><big><tt>'''Originally the internet was not designed to be secure | + | <center><font color="red"><big><tt>'''*** Originally the internet was not designed to be secure ***'''</tt></big></font></center> |
==Introduction== | ==Introduction== | ||
| − | + | The internet was principally designed to be robust (no single point of failure) and be able to reliably transport data between disparate local networks. | |
Securing the internet is done on an individual basis, therefore it is the companies/institutions responsibility to secure internet communications. | Securing the internet is done on an individual basis, therefore it is the companies/institutions responsibility to secure internet communications. | ||
| Line 17: | Line 17: | ||
===[[SUNScholar/Firewall|'''STEP 1. SERVER FIREWALL''']]=== | ===[[SUNScholar/Firewall|'''STEP 1. SERVER FIREWALL''']]=== | ||
===[[SUNScholar/Secure_Internet_Connections|'''STEP 2. SECURE CONNECTIONS''']]=== | ===[[SUNScholar/Secure_Internet_Connections|'''STEP 2. SECURE CONNECTIONS''']]=== | ||
| − | ===[ | + | ===[[Media:Linux-security.pdf|'''FURTHER LINUX SERVER SECURITY (55MB Download)''']]=== |
==Client Security== | ==Client Security== | ||
| Line 26: | Line 26: | ||
==References== | ==References== | ||
*https://wiki.duraspace.org/display/DSPACE/SecuringDSpace | *https://wiki.duraspace.org/display/DSPACE/SecuringDSpace | ||
| + | [[Category:System Administration]] | ||
| + | [[Category:Installation]] | ||
| + | __NOTOC__ | ||
Latest revision as of 00:01, 10 June 2016
Back to After Installation Tasks
Introduction
The internet was principally designed to be robust (no single point of failure) and be able to reliably transport data between disparate local networks.
Securing the internet is done on an individual basis, therefore it is the companies/institutions responsibility to secure internet communications.
Open unsecured communications creates the potential for intrusion therefore it is recommended that ALL internet traffic to your repository be firewalled and encrypted.
See below for more details.
Server Security
STEP 1. SERVER FIREWALL
STEP 2. SECURE CONNECTIONS
FURTHER LINUX SERVER SECURITY (55MB Download)
Client Security
Please encourage your managers, submitters, reviewers, collection managers and metadata editors to use safe up to date browsers such as one of the following:
