Post #686

210049d3729ee5e226f2fa8c2b27030b5c215588ff447655b2671bdb717671a8
978297ffd59e2c1f59cdff82869176cd8eb3cafe500980d7bd71781920c242ee
Signature not verified

This entry might be using an old signature, or it was signed by a key that does not exist on the server.

{"entry_date":1532465605,"post_data":{"edit_count":0,"last_edit_date":0,"last_edit_user_id":0,"message_sha512":"5468001e8f9fea708d986e0c063770117d5abf1b969ac1472ce541b8249deb8ac63858eab7930d89b51f97488521e45c38077676a115329dc15a9fc0281a9150","node_id":10,"post_date":1524693189,"thread_id":86,"user_id":34},"post_link":"http:\/\/factomize.com\/forums\/index.php?threads\/86#post-686"}
The entry content as it exists in the database. This should be verified against the blockchain entry.
Block Party
[QUOTE="Niels, post: 524, member: 8"][B]NK04)[/B]

Could you name a few hardening actions you will perform on the Node itself?[/QUOTE]

We will strip out all unused daemons and services from our Linux build, lock permissions to Factom data to only the username that runs Factom/Docker, set permissions so that systems administrators only have access to the data they require, ensure each sysadmin has their own user/certificate, set a weekly update schedule for critical system security fixes, and send all system logs to an external logging server to check for abnormal activity.
This is the raw content, without BBCode parsing.
Top