Not input per se, but they can see what sites you visit and apps installed. Getting every keypress is a bit harder to my knowledge. Depending on mobile device management (MDM) software used, they can have granular access to running and installed apps, web traffic logs, and access to memory in an aim to control corporate data. Also, most MDMs running on non-corporate (BYOD) devices run corporate data in a sandbox that is managed by the MDM separately. If you have a corporate phone, than this is usually not true and the MDM can see much more data.
Now, the question of will anyone look at what you wrote is a bit harder to answer and it depends on the size of your organization. My firm will not really look unless there is a HR or legal request or you pop up in some reporting of malicious site visits.
It isn't though. This merely changes the display of the cursor. Go to windowed mode (not fullscreen) and pull the cursor down into the address bar and tabs area to see that this does not prevent access to the address bar. It only changes how you perceive the position of the cursor.
This is such a terrible idea I cannot wrap my head around why any one thinks pasting a password is a vulnerability. If someone is on the system and can see the clip board, you are screwed regardless.
The issue is not with problems, but with the arbitrary nature of this as a learning tool. Getting a page to fix an issue that you forsaw and prevented is dumb. Teach them to make resilient systems rather than get out of bed.
I have never gotten up at 3am to fix an outage because outages do not impact systems that widely. If it is a network problem, let the network team do their job. All of your other problems are solved with multiple HA/ load balanced servers, monitoring, and proper testing.
So the students engineered themselves to fail or the instructors gave them a terrible system that is bound to fail? Shit going sideways is a fact of life, but you can at least let people have the chance to prevent the problems before they exist.
While there is always someone else's mess you have to support, that does not seem like a great teaching moment to me.
Wait, this seems to ignore the fact that with good change controls and sound code, products do not just fail at 3am. If they call everyone at 3am without a failure the student could have prevented, that does not teach anything other than how to answer a phone. Instead, teach them to properly engineer and document their solution such that they aren't called at 3am.
This seems like a waste of a good night's sleep to me.
Could not agree more. We have done this with my last project and it was immensely helpful. As our team switched from one version of Angular to another, our tests were consistent and able to catch a flaw on the main landing page that had been completed months before. By having tests separate and having a person(s) responsible for testing, it allows developers more time to fix problems.
In addition, we used our tests for many of the same things the author recommended such as running a thousand instances concurrently to load test and using parameterized inputs to test the database indirectly. It lends some incredible abilities to verify over and over the application works.
(I used Selenium and a number of add ons to do this on our web application)
The article does mention the split between the FBI's public nature of investigations (they have to prosecute) while the NSA does not really care about methods, so long as it returns results.
The interesting part is that the NSA is compelled at all to help. Why would they? Give up their toys and secrets to help another agency go after someone who is already dead seems to put them in peril for little/ no gain. Unless you believe the "dormant cyber pathogen"[1] line holds any water (which it does not).
Absolutely not, we have the benefit of multiple people and a budget of more than 6 tokens. We prioritize, but they are more focused around planning, not these faux surprises.
In addition, there is no way this person would interact with the dev team, PR, journalists, and data teams themselves. There are too many people giving input for a business of more than 10 people to go this sideways.
Repping Raleigh here. There is a decent startup scene and housing is very reasonable. $1200 for a 2 bed/ 2 bath apartment with garage that is about 10 minutes from my office and less than 20 minutes to downtown.
Weather is nice and there are plenty of firms moving to the area. The only downside is that traffic is increasing, but there is enough sprawl it is not a huge issue. Startups are coming out of major universities and office space and co-work spaces abound. Aside from the hot months and increasing traffic, it is pretty great so far.
That is not how car production works. Paint is literally the second thing that occurs after a chassis and body panels are applied. But otherwise, the working time on a car from start to finish, including paint, is somewhere in the 10-20 hour range. Theoretically, your timeline could work but paint takes time to cure, then needs polish and interior features take a while, although CAN-BUS has certainly made the electronics easier.