[cisco-voip] Your Associated Webex Sites

[Matthew Loraditch]

The only list I can think of is behind the sign in screen for webex admin and it only lists the accounts you have been given access to so I’m not sure how or why this would ever be a problem? It’s no different than looking at my deal list in CCW or say your accounting departments list of accounts? Unless I’m missing what you are thinking about?


Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: MLoraditch at heliontechnologies.com
From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Anthony Holloway
Sent: Monday, September 9, 2019 8:11 AM
To: Charles Goldsmith <w at woka.us>
Cc: Cisco VoIP Group <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Your Associated Webex Sites

Correct, mostly for Partners, since:

A) We have a higher quantity than end customers
B) The list of sites acts like a list of customers we do business with (past, current and future)
C) Lists off all end customer sites too (which, depending on how the site names are being used, could give insight into the business; E.g., divisions, project names, future name changes indicating: splits, mergers, re-branding, etc.

However, I would think it would apply to end customers themselves too.  Not only for option C above, but I can also see a situation where if two customer names were put side-by-side on the same list, that could cause an issue.

On Mon, Sep 9, 2019 at 1:04 AM Charles Goldsmith <w at woka.us<mailto:w at woka.us>> wrote:
Lelio, I think this mainly applies to partners, since we can see our customer sites.

Anthony, I don't think there is a public listing of your sites, not that I've seen anyway.

On Mon, Sep 9, 2019 at 12:07 AM Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

I’m not quite sure I understand the question.

Are you asking about a public index of sites?

I know that configuration-wise, you can choose to list meetings on a site. We’ve chosen to not do that. So the worst that can happen is some gets to our WebEx landing page.

I’m not sure what hiding a site helps with. Or helps deter.

I mean, I’ve got our site listed on our service pages. They’re not restricted, so anyone can find it.

Logins are protected by SSO, so we’ve got that going too. Protection-wise, I mean.

Is there something I’m missing?

Are you gonna make me loose sleep now!??? :)

-sent from mobile device-

Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354<tel:519-824-4120;56354> | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook


On Sep 8, 2019, at 2:45 PM, Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>> wrote:
All,

I want to take the pulse on a topic here, relating to your list of associated Webex sites, and whether or not they are private to you, or if they should be public information.

I was talking with a colleague about this ever growing list of customers we work with being cataloged by Webex in the fact that we keep getting associated to more and more customers, and what potential issue this may cause if the site list were to be viewed by just anyone on the internet.

Would you want your site list (whether end customer or partner admin) protected from view of others, or is it not that big of a deal?

And I guess as a follow up, is this list protected today, or is there a means by which my list can be exposed to the public relatively easily?
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190909/f70b30d6/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image335972.png
Type: image/png
Size: 9409 bytes
Desc: image335972.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190909/f70b30d6/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image176415.png
Type: image/png
Size: 431 bytes
Desc: image176415.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190909/f70b30d6/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image764365.png
Type: image/png
Size: 561 bytes
Desc: image764365.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190909/f70b30d6/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image038122.png
Type: image/png
Size: 444 bytes
Desc: image038122.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190909/f70b30d6/attachment-0003.png>