DX NetOps

 View Only

  • 1.  Logs access user's in DX NetOps Spectrum

    Posted Apr 09, 2026 12:14 PM

    In DX NetOps Spectrum, is there any log or mechanism available to track historical user password changes?

    Additionally, is there any visibility or logging for password policy configurations and related events such as complexity, expiration, password history, failed login attempts, account lockout, and inactivity timeouts?



    -------------------------------------------


  • 2.  RE: Logs access user's in DX NetOps Spectrum

    Broadcom Employee
    Posted Apr 13, 2026 12:12 AM

    Hi Jose,

    Spectrum does not natively support the tracking, enforcement, or logging of advanced password policies for its local user database. There is no mechanism, log file, or database table within DX NetOps Spectrum that tracks the history of user password changes. 

    To achieve this,  we would
    recommend using  Single Sign-On (SAML 2.0) or LDAP.



    ------------------------------
    [JobTitle]
    [CompanyName]
    [State]
    ------------------------------



  • 3.  RE: Logs access user's in DX NetOps Spectrum

    Posted Apr 13, 2026 11:05 AM

    Thanks for the reply! Best regards!

    -------------------------------------------



  • 4.  RE: Logs access user's in DX NetOps Spectrum

    Posted 26 days ago

    It should also be added that the reason why LDAP and SAML integration exists in Spectrum (and have done so for a very long time - and the same goes for the Portal as well) is to answer all of these questions that you have proposed - in particular to move the responsibility of the questions back to the team in the organisation that performs these activities - as in the Identity/Access team. Therefore, since they have access/control over these sorts of issues then it is their responsibility to maintain them and NOT the network observability's team to do their jobs for them. 😉

    Sure, this sort of thing can be bypassed with using local user accounts in NetOps (and NetOps itself does have extensive security setups - see Techdocs for the details) BUT that is not what should be setup in Prod in and organisation...

    -------------------------------------------