Repository navigation
Security
themarioga edited this page Nov 8, 2026
·
1 revision
| Concern | What TIE does |
|---|---|
| SFTP server identity | Always verified with known_hosts or a SHA256 fingerprint. Accepting any key requires insecureAcceptAnyHostKey(true) and logs a WARN on every connection |
| Credentials | Literal or ${secret:name} resolved by your SecretProvider only to connect; the returned char[] is cleared. SftpChannel.toString() hides them |
| Credentials in messages | Never in logs, exceptions or results. A failing SecretProvider gives a fixed message, since its own could contain a secret |
| Record values in logs | Never logged above DEBUG; TIE logs file names and statuses at INFO |
| Personal data | Travels only in results, listener calls and reports, which you control |
| Path traversal | Listed names with /, \ or .. are ignored; deliverFile rejects such names; nothing is written outside the working directory and the configured destinations |
| XML | DTDs and external entities are disabled; a DOCTYPE fails the file (UNSAFE_CONTENT) |
| XLSX | POI's zip-bomb limits apply (UNSAFE_CONTENT) |
| Spreadsheet formula injection | Neutralized in CSV/XLSX result reports (=, +, -, @, tab, carriage return) |
| Parse errors of definitions | Line and column only, never an excerpt of the document |
| Partial files | Deliveries go through .<name>.part and a final rename |
TIE is MIT-licensed · tie · tie-core · tie-spring-boot-starter · Changelog
Using TIE
How it works
Reference
Contributing