find ip addresses on switch

No one good way to do this, depends on variables. Some commands may help 

sh ip arp (only works if you have l3 interfaces in each vlan)

sh ip dhcp snooping binding (needs dhcp snooping)

sh ip device tracking interface gigabitEthernet 

Good video explaining HSTS for customers

 https://www.youtube.com/watch?v=Jx5NEOI_TPw&t=9s

Although some of it is specific to the company platform the explanation of the HSTS and why its an issue is good.

HSTS

HTTP Strict transport security

Any site that redirects from HTTP to HTTPS is vulnerable 

Its medium severity usually but low hanging fruit for attackers, if they see the basics are not done they may probe further but if they see HSTS setup they may move on

HSTS is a protocol sets regulations for how user agents (web browsers) should handle their connection for a site running https

Its possible for attackers to downgrade https to http connections and read data 

library kiosk urls

 mysmartadmin.com

subscription.librarystationupdate.com

shared.bibliotheca.services

how to open big log files

 needed to open a 5GB log file

tried a few different options but landed on notepad++ with bigfiles plugin

palo alto user id not working for some user

Check for NTP settings on both firewalls

Saw an issue where the groups were not being downloaded

All config looked good, checked all settings etc

The cmd below was run and it came back

debug user-id reset user-id-manager type user-group

mac address formats

default: 1234.5678.90AB

IEEE 802/IETF: 12-34-56-78-90-AB

Unformatted: 1234567890AB

One byte 12:34:56:78:90:AB

Two byte 1234:5678:90AB

IP addresses were using dots

One byte 12.34.56.78.90.AB

two byte 1234.5678.90AB

Xerox made it and got 00-00-00

Cisco 00-00-0C

Next (later apple) 00-00-0F

Samsung 00-00-F0

MAC addresses are the address at L2

MAC addresses are possible to spoof so MAB sec not great

Some devices can't do MFA or 802.1x so MAC rules will be needed until devices get smarter.

csr attributes that are required or optional

 

CN	Common   Name	This is the fully qualified domain name (FQDN) that specifies the server’s exact location in the Domain Name System (DNS). For example, a component with hostname webBridge1 and parent domain example.com has the fully qualified domain name webBridge1.example.com. The FQDN uniquely distinguishes the component from any other components called webBridge1 in other domains.	Required, see notes below
O	Organization or Business name	Usually the legal incorporated name of a company. It should include any suffixes such as Ltd., Inc., or Corp. Use “” around the attribute if more than one word, e.g. “Example Inc.”	Optional
OU	Organizational unit or Department name	For example, Support, IT, Engineering, Finance. Use “” around the attribute if more than one word, e.g. “Human Resources”	Optional
L	Location	City or town. For example, London, Boston, Milan, Berlin.	Optional
ST	Province, Region, County or State	For example, Buckinghamshire, California. Do not abbreviate. Use “” around the attribute if more than one word, e.g. “New Jersey”	Optional
C	Country	The two-letter ISO code for the country where your organization is located. For example, US, GB, FR.	Optional
An email address		An email address to contact the organization. Usually the email address of the certificate administrator or IT department.	Optional
SAN	Subject Alternative Name	From X509 Version 3 (RFC 2459), SSL certificates are allowed to specify multiple names that the certificate should match. This field enables the generated certificate to cover multiple domains. It can contain IP addresses, domain names, email addresses, regular DNS host names, etc, separated by commas. If you specify this list you must also include the CN in this list. Although this is an optional field, the SAN field must be completed in order for XMPP clients to accept a certificate, otherwise the XMPP clients will display a certificate error.	Required   for XMPP server certificates or if a single certificate is to be used across   multiple components.  See note below. Note: XMPP server is not supported from version 3.0