How California Polytechnic State University Centralized IT With AppsAnywhere (special post)

This time I will do something different here.

I don't have 1h to watch this

https://www.youtube.com/watch?v=H_MYZmGT3UY

Do I've took the transcription and I've asked chatgpt some questions

what they did

They centralized campus IT into a service-oriented organization, moved core systems to the cloud, and created a single “software hub” where students, faculty, and staff can access all approved software. They standardized software versions across labs, personal devices, and virtual labs, enabled self-service downloads and remote access, integrated support, knowledge base, and service catalog into one front door, and used data and analytics to manage usage, licensing, support demand, and continuous improvement.

how they did

They did it by first reorganizing IT from siloed technical teams into a plan–build–run, service-focused model, with clear ownership, documentation, and operational gates before services went live. They moved infrastructure to the cloud, adopted a single service management platform as the front door for requests, support, and knowledge, and defined services in customer-focused language. They then packaged and standardized software once and delivered it everywhere through a centralized software hub and virtual labs, integrated identity and access controls, trained support teams, and used usage and support data to continuously adjust staffing, licensing, and processes.

what were the challenges they faced

They faced fragmented and decentralized IT, inconsistent software versions across departments and labs, poor and confusing software distribution, and limited visibility into usage and support demand. Operational teams were overloaded with run work, leaving little capacity to improve services. Cultural and political resistance to centralization, lack of shared data, and dependence on individuals rather than documented processes also slowed progress. The pandemic then created urgency, forcing rapid scaling of remote access, exposing network and equity gaps, and accelerating adoption under tight time constraints.

what was their strategy to overcome these 

Their strategy was to shift focus from technologies and organizational silos to services and users. They secured executive buy-in, used data to make decisions and reduce political friction, and restructured IT into a service-oriented, plan–build–run model. They standardized and documented services before operational handoff, created a single front door for access and support, centralized software packaging and delivery, and leveraged cloud and virtual labs to remove location and device constraints. They also prioritized self-service, measured usage and outcomes continuously, and used the pandemic as an accelerator rather than a workaround.

Comments

Post a Comment

Popular posts from this blog

Prompt Engineering Demands Rigorous Evaluation

In the blog post “Prompt Engineering Requires Evaluation” on the Shostack + Associates website, the author argues that treating prompts for large language models (LLMs) merely as creative artefacts is insufficient. Engineering prompts properly demands structured evaluation frameworks — what the AI community calls “evals” — to test which prompt versions work better, with which models, and under which conditions. The post highlights that simply assuming a prompt is “good enough” creates risks when LLMs are integrated into production systems (e.g., for threat modeling). It advocates for measuring prompt performance, variation effects, and tool-chain dependencies (model, context, ancillary materials).  Ultimately the message is: prompt engineering should borrow disciplined practices from software engineering (versioning, testing, benchmarking) rather than relying on informal experimentation.  https://shostack.org/blog/prompt-enignieering-requires-evaluation/
Read more

Secure Vibe Coding Guide: Best Practices for Writing Secure Code

Ken Huang's "Secure Vibe Coding Guide" emphasizes the importance of integrating security into the software development lifecycle. The guide provides best practices for writing secure code, including input validation, proper authentication mechanisms, and secure data storage techniques. It also highlights the necessity of regular code reviews and staying updated with the latest security vulnerabilities and patches. By following these guidelines, developers can create applications that are resilient against common security threats and contribute to a safer digital environment.  https://kenhuangus.substack.com/p/secure-vibe-coding-guide
Read more

KEVIntel: Real-Time Intelligence on Exploited Vulnerabilities

KEVIntel is a dynamic platform providing up-to-date information on known exploited vulnerabilities (KEVs). It aggregates data from over 50 public sources, including CISA, and enriches each entry with metadata such as EPSS scores, online mentions, scanner inclusion, and exploitation status. The platform aims to serve as an early warning system, offering insights even before official publications. KEVIntel supports various formats like JSON, CSV, and RSS, facilitating integration into security operations. These entries include CVSS scores, exploit status, and links to proof-of-concept code, aiding organizations in prioritizing remediation efforts.   https://kevintel.com/
Read more