...
- Hacking into a vendor account
- Possible consequences
- loss or corruption of vendor data
- use of storage for illicit purposes
- interruption of vendor data deliveries
- load on "u2" server (currently wain006)
- Possible mitigations
- configure vsftpd to recognize only certain IP addresses to log in
- vendors must agree with the level of security and the risk
- monitor disk usage with ganglia and look for abnormalities
- configure vsftpd for secure userid/pwd transfer, e.g., tls
- Possible consequences
- Hacking into the vsftp server
- Is this likely?
- Hacking into the lsstlnx VM
- Probably independent Independent of vsftp and, therefore, no different from other VMs at SLAC with externally visible ports
Why Existing FTP Service is Unacceptable
- Non-anonymous (s)FTP requires a SLAC unix account and that has been deemed unacceptable by LSST project team
- Anonymous FTP server suffers from several shortcomings:
- The server software cannot restart an interrupted data transfer
- The AFS-backed store is possibly not scalable to the hundreds of GB needed
- The 3-day dwell period is too risky for the data
- The AFS permissions combined with the 3-day swell do not allow for the type of permissions that would allow for a convincing separation between the two vendor's data
- The dropbox does not allow for vendor management of its data at SLAC
...