|
|
Level
5
How automated file exchange can be integrated into this architecture
without introducing a flaw into the current security
The security risk is in the capacities of
the applications to do such or such thing. Thus a communication
software such as TBT/400 is useful to give an important help into
the control of these security risks by:
- Whatever the protocol used, TBT/400
will never expose the files directory tree of the
machine (no visibility), either in outgoing or incoming
- in incoming (from outside to TBT/400):
as TBT/400 creates dynamically single file, it forbid to crush
any file according to the own nomenclature of the local exploitation,
- in outgoing (from TBT/400 to the
outside): transmissions are destructive. A file will never be
transferred twice to the outside world (expected if the local
exploiter ask for that)
- Access control to the applications of flow
process, control of the authorized correspondents (thus identifies)
- Call access control,
- Centralization of all network addresses
and of the used transmission profiles (directories administration)
- Analytic reports with alerts sending
- and this without any front-end computer
dedicated (in case of a front-end dedicated, a double security
will have to be generated)
TBT/400 is not only a software of automated
file transfers, but it can be naturally integrated into a secured
local area network (LAN) without changing it or requiring a large
impact analysis).
With the TBT/400 communication software, everything
is fordidden except the authorized things. It
is at the opposite of some file sharing logic where everything is
authorized except the forbidden things.


|