Small remark: I observed many issues caused by Nessus scanning.
Usually those issues can be classified as false positives - messages
reporting problems which didn't happen.
However I also noticed complete failure of communication to HSM (High
Security Module), which meant card transaction processing outage. And
this problem was repeatable.
It i worth to understand such scanning is not just an observation,
readonly process. It really affects the scanned systems.
So it is really worth to identify problems caused by scanning and
exclude those "fragile" things from this process.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 06.07.2024 o 18:19, Steve Estle pisze:
Hello All,
Pardon the interrupt on all the religious discussions surrounding Python vs.
Rexx (count me in the camp of a REXX biggot given my years in ZVM and ZOS) I
see Rexx as a swiss army knife for so many tasks in our never ending myriad of
tasks as Sysprogs, etc. - I do though wish Rexx could process SMF records
better though. BTW - I have never have done any OO Rexx tasks so can't comment
on that world but certainly hope to at some point given all the great comments
surrounding it's capabilities.
Now to the real reason for my post:
We run Tectia for ZOS in our environment (SSH.COM). During our attempts to upgrade Tectia for ZOS to 6.7.1 it
became very apparent the base SSHD2 started task would hang under certain conditions on our Sandbox LPAR. After
much further investigation it is clear the trigger to the hang conditions is because of our external Nessus port
scans that run periodically against our mainframe LPAR's. The "hang" condition issue has been reported
to the vendor support team in which their initial response was to halt our scans which won't fly with our
security teams of course. Tectia SSH Dev. team seems stymied on the issue although they are trying to recreate
in lab environment (many debug logs sent to them - they don't appear to like dumps - prefer the debug logs). The
hang strictly presents itself in the SSHD2 operator interface (in other words "F SSHD2, VERSION" &
"P SSHD2" commands are no longer responsive, etc. and the task has to be cancelled to restart started
task).
My key questions are:
1. Anyone else out there that is running this product on ZOS (We are running
ZOS 2.5)?
2. If so, anyone else experienced any similar issues? If so did you figure out
workaround for the issue to avoid the hang conditions caused by the port scans?
If you prefer to talk offline on this please email me.
Thanks,
Steve Estle
[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
