Innodata Server Hardening Document: Difference between revisions
No edit summary |
Flag as outdated (client review pass) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Outdated|reason=Old Technology and Customer But Relevant for Understanding|date=2026-07}} | |||
[[category:INNODATA]] | [[category:INNODATA]] | ||
='''Innodata Server Hardening''' | ='''Innodata Server Hardening'''= | ||
Latest revision as of 15:59, 25 July 2026
This is an Old / Outdated Article, Please use this only as technical Reference
Reason: Old Technology and Customer But Relevant for Understanding
Flagged: 2026-07
Innodata Server Hardening[edit]
Block root access:[edit]
Root user should not be allowed to access shell,steps to do it below
Apply ssh Banner[edit]
Include company propriety Banner in ssh config file
Banner will be displayed in blow fashion:
ssh channel encryption[edit]
Ssh ciphers should only entertain the request if ciphers are minimum aes256 bit.
Account lockout policy[edit]
