# data[].attributes.headline
A clear vision of OIT's next steps should help EIS understand and focus on tech/skills

# data[].attributes.subject
A clear vision of OIT's next steps should help EIS understand and focus on tech/skills

# data[].attributes.headline
Communication is key. High to low, low to high, left to right.  

# data[].attributes.subject
Communication is key. High to low, low to high, left to right.  

# data[].attributes.headline
I feel it's about time to re-align our structure to modern organizations - DC

# data[].attributes.subject
I feel it's about time to re-align our structure to modern organizations - DC

# data[].attributes.headline
We learn new skills to keep us up to date - DC

# data[].attributes.subject
We learn new skills to keep us up to date - DC

# data[].attributes.headline
What is the overall goal for this effort?

# data[].attributes.subject
What is the overall goal for this effort?

# data[].attributes.headline
What are the other EIS teams doing - Martin

# data[].attributes.subject
What are the other EIS teams doing - Martin

# data[].attributes.body
Learning new technologies and increasing our skill sets - jf

# data[].attributes.headline
More of a question. Is anyone not excited or afraid of this change? - DC

# data[].attributes.subject
More of a question. Is anyone not excited or afraid of this change? - DC

# data[].attributes.headline
Are we using outside resources to help reorg - John

# data[].attributes.subject
Are we using outside resources to help reorg - John

# data[].attributes.headline
I feel they need more definition than just "going to the cloud" - DC

# data[].attributes.subject
I feel they need more definition than just "going to the cloud" - DC

# data[].attributes.headline
"Why" cloud first.  Need strategy holistically.

# data[].attributes.subject
"Why" cloud first.  Need strategy holistically.

# data[].attributes.headline
I don't think we should get to hung up on how much it costs to move Peoplesoft to the Cloud.  That is for Jay and the Senior Staff to worry about; I am sure they know it could be more expensive that what we are doing now

# data[].attributes.subject
I don't think we should get to hung up on how much it costs to move Peoplesoft to the Cloud.  That is for Jay and the Senior Staff to worry about; I am sure they know it could be more expensive that what we are doing now

# data[].attributes.headline
Overall design is needed FIRST. When you build a house, you design it before actually starting construction. 

# data[].attributes.subject
Overall design is needed FIRST. When you build a house, you design it before actually starting construction. 

# data[].attributes.headline
If the only reason we are moving to the cloud is to address the needs of DevOps (be it OIT or campus departments), then perhaps we should re-evaluate.  One additional experienced individual added to our team to address cloud infrastructure, programming needs, and DevOps could meet that need. 

# data[].attributes.subject
If the only reason we are moving to the cloud is to address the needs of DevOps (be it OIT or campus departments), then perhaps we should re-evaluate.  One additional experienced individual added to our team to address cloud infrastructure, programming needs, and DevOps could meet that need. 

# data[].attributes.headline
Security needs to be made a priority in the design phase.  There's a quote from CompTIA that basically states it will cost an organization much more to address security after the fact (approx 9 times more), than if it is included in the design.

# data[].attributes.subject
Security needs to be made a priority in the design phase.  There's a quote from CompTIA that basically states it will cost an organization much more to address security after the fact (approx 9 times more), than if it is included in the design.

# data[].attributes.headline
Reducing the amount of frustration involved when trying to work with other departments.

# data[].attributes.subject
Reducing the amount of frustration involved when trying to work with other departments.

# data[].attributes.headline
Use of scale sets could be very useful for such things like class registration, admissions, drop\add, room draw, etc, where based upon a specific threshold, additional VMs can be automatically spun up to support the load.  However, applications must be able to support this.

# data[].attributes.subject
Use of scale sets could be very useful for such things like class registration, admissions, drop\add, room draw, etc, where based upon a specific threshold, additional VMs can be automatically spun up to support the load.  However, applications must be able to support this.

# data[].attributes.headline
Duplication of current services:  Firewall, DDoS Protection, Infrastructure, IAM, Monitoring.  See screenshot for duplication of Security Tools.  In order to create a secure environment in the cloud, we will literally be recreating the same environment we have here, yet we will be expected to continue to run our current infrastructure as well as the new infrastructure. Where are these resources going to come from?

# data[].attributes.subject
Duplication of current services:  Firewall, DDoS Protection, Infrastructure, IAM, Monitoring.  See screenshot for duplication of Security Tools.  In order to create a secure environment in the cloud, we will literally be recreating the same environment we have here, yet we will be expected to continue to run our current infrastructure as well as the new infrastructure. Where are these resources going to come from?

# data[].attributes.headline
Fileshares are incredibly easy to create (although could be costly depending on the region\how often they are accessed)

# data[].attributes.subject
Fileshares are incredibly easy to create (although could be costly depending on the region\how often they are accessed)

# data[].attributes.headline
Key Vault may be very useful to DevOps in securely storing passwords applications may need.  Also useful to SOC and CSS in create\control encryption keys, provision, manage, deploy public\private SSL\TLS certificates.  More centrally managed, don't have to manage a separate application to store encryption keys.  Also useful:  self service password reset.

# data[].attributes.subject
Key Vault may be very useful to DevOps in securely storing passwords applications may need.  Also useful to SOC and CSS in create\control encryption keys, provision, manage, deploy public\private SSL\TLS certificates.  More centrally managed, don't have to manage a separate application to store encryption keys.  Also useful:  self service password reset.

# data[].attributes.headline
Policies would allow us to ensure VMs have a departmental tag associated with them.  Much more efficient to receive a real-time error when forgetting something, than to have to go back and fix it later.

# data[].attributes.subject
Policies would allow us to ensure VMs have a departmental tag associated with them.  Much more efficient to receive a real-time error when forgetting something, than to have to go back and fix it later.

# data[].attributes.headline
Azure Locks helpful to guard against human error\accidental deletion of a resource.

# data[].attributes.subject
Azure Locks helpful to guard against human error\accidental deletion of a resource.

# data[].attributes.headline
Azure Monitor would allow us to view metrics\logs\service health\create alerts for resources hosted in Azure.Who will be responsible for creating policies\controlling Network Security Groups to lock this down?  Who will have access\abilitiy to create VMs in Azure that has Princeton data on it?  Who will be responsible for ensuring no restricted data is put on such a machine?  Ex:  Joe Schmo from East Asisan Studies decides he wants a VM in Azure, spins one up with an easily crackable password, public access from the internet via RDP and puts some restricted data on it.  We know Direct RDP access is not permitted currently from OIT (and for good reason).  Who's going to stop this from happening?  Unless hosting Web Apps by using Azure PaaS, this is riddled with Security issues.  Joe Schmo can easily make the argument that since we are now a Wireless shop, he has to leave RDP open to the Internet since his IP may change.

# data[].attributes.subject
Azure Monitor would allow us to view metrics\logs\service health\create alerts for resources hosted in Azure.Who will be responsible for creating policies\controlling Network Security Groups to lock this down?  Who will have access\abilitiy to create VMs in Azure that has Princeton data on it?  Who will be responsible for ensuring no restricted data is put on such a machine?  Ex:  Joe Schmo from East Asisan Studies decides he wants a VM in Azure, spins one up with an easily crackable password, public access from the internet via RDP and puts some restricted data on it.  We know Direct RDP access is not permitted currently from OIT (and for good reason).  Who's going to stop this from happening?  Unless hosting Web Apps by using Azure PaaS, this is riddled with Security issues.  Joe Schmo can easily make the argument that since we are now a Wireless shop, he has to leave RDP open to the Internet since his IP may change.

# data[].attributes.headline
There is a place for DevOps, but it should not lead the way in how an organization is run.  It is very easy to look at Azure as a simple way to spinup VMs.  However, there are numerous security concerns that are not being addressed. Since managers are required to stay out of daily operations, it is easy to forget security\not understand what the day-to-day looks like and more importantly, WHY things are set up the way they are.  How can we ensure GPOs, CrowdStrike, etc will be deployed to all new VMs?  How will patching be enforced?

# data[].attributes.subject
There is a place for DevOps, but it should not lead the way in how an organization is run.  It is very easy to look at Azure as a simple way to spinup VMs.  However, there are numerous security concerns that are not being addressed. Since managers are required to stay out of daily operations, it is easy to forget security\not understand what the day-to-day looks like and more importantly, WHY things are set up the way they are.  How can we ensure GPOs, CrowdStrike, etc will be deployed to all new VMs?  How will patching be enforced?