Tell me about your program. What is it called, what's the age group, and the aim of the program? So our program I guess is Chief White Cap School and we're part of Saskatoon Public School Division in a partnership with White Cap Dakota First Nation. It's a K-8 elementary school in Saskatoon Public Schools. Our aim and our goals I guess is within the provincial curriculum of Saskatchewan Learning to facilitate all elements of that with a particular focus on our phoneme outcomes that are in the curriculum being sort of centered around Dakota language culture. And the work that's gone into that prior is part of the partnership with our school division and White Cap to create this beautiful building, to create these lessons. So we're sort of dedicated to that and our goals around phoneme outcomes with specifics to Dakota language and instruction. I'll take a run at what we're doing here. I guess the holistic view is just the relationship between White Cap, Dakota, and the city of Saskatoon goes back to I believe it's 1882. We'll have to double check that on our website in our history but John Lake and White Cap, John Lake moved here and wanted to start Temperance Colony and he looked and seeked for the local First Nations people and now it's Chief White Cap. These are people settled down south of Saskatchewan River. And they came in met with John Lake and now the city of Saskatoon is born, right? We wanted to make sure that our roots here rooted as Dakota people were also, I guess, emphasized and commemorated in the city of Saskatoon. So we looked to the city of Saskatoon. It's our primary market for education, for economics, for business, for partnerships. So we definitely were 20 minutes south of Saskatoon. So we wanted to make sure that our kids had a fighting chance when it comes to learning their language, learning their cultural identity and who they are as Dakota people. So we worked with the city of Saskatoon, SPSD, that's the public school division in collaboration and we moved something forward. That started in 1992, I believe, between George Rathwell and Darcy Bear, Chief Darcy Bear and Ray Morrison as well. So those three gentlemen met and then they just progressed on. Eventually we came to this agreement and now we're working together on a program to make sure that Dakota curriculum is taught in all these schools and I believe it's taught in other schools as well, right? It could be, Dylan, I'm not 100% sure of that, but it certainly will be moving forward with these resources and the website being what it is right now. It's certainly accessible. So more or less this seems like a pilot project right now, so that's what we're doing. So we're incorporating our Dakota cultural identity or language into the Stonebridge School, the Chief White Cap School. So there's a lot of history here and also it's a lot of first two as well as Chief White Cap Schools. The first chief, I guess the first school in Saskatoon named after a chief. So there's also reconciliation behind this as well. And that's what we talk about between the TRU Truth and Reconciliation calls to action. So we're trying to make sure that we're following that as well and making sure that we're having reconciliation and we're continuing on moving forward together as partners in the city of Saskatoon and with White Cap. And just from my perspective, just to get started, Saskatoon Public Schools is very proud of our relationship with White Cap Dakota First Nation and like Dylan was explaining, it goes back 25 years or so. One of the things that I see as an aim of the program is to take the students that are going to school and grades kindergarten to grade four at Charles Redhawk Elementary School in the First Nation and to successfully transition them here to Chief White Cap School. And then to have those students successfully take their grades five through eight and then transition into high school in a successful way and then move forward from there after grade 12 into whatever they want to do with their lives. And so that's really important to Saskatoon Public Schools. We value our partnership a great deal with White Cap. The Dakota Language and Culture piece of the school is unique to Saskatoon Public. Something again we're very proud of. And we have some support folks here at the school. So we have, in addition to the regular staff, we have Nancy Linklater and Lois Baer who are here that help us with ceremony every morning for the students and families. As well they're in classrooms helping to bring forward the resources, the Dakota resources and teachings. And we have Ian Worm who's a shared partnership person that works with Saskatoon Public and White Cap. He's often at Chief White Cap School here. And he's also in the classroom supporting students, White Cap students and families. So, yeah, it's a great partnership. We're very proud of it. Yeah, that's very cool. What is the program intended to do? What are the learning objectives? So within our Saskatoon Public Schools follow provincial curriculum set forth by the Ministry of Education, whether students in La Ronge or Estevan. So there's learning outcomes within that. There's some overarching principles around First Nations and UNMAT outcomes in schools that in this particular year we focus on reconciliation, we focus on Canada 150. We talk a little bit about recognizing diversity in our city, in our community, in our province. And certainly the cultural pieces and that respect and learning about treaties, the respect and learning about cultures. That's where you'd see lots of tie-ins with this particular resource and the help that we have in our school for achieving that outcome within Dakota. So there may be other schools in our division that would talk about other First Nations, perhaps like Cree or other cultures within the First Nations outcomes that are there. But ours is sort of, I want to say, tailor-made a little bit. Like again, we've got some things at our access right at the school. Two elders, as Dean mentioned, Ian is sort of a transition support worker for our families and for students. And those outcomes can be achieved, I think, through our teaching staff as well, but through the support of the First Nation and those partnerships that are there as well. So the curricular outcomes, though, you could probably refer specifically just to, and we could provide that for you through SAS learning, and just look right at that document as well and you'll see just the listed kind of right there in the overarching piece as well. What was the question? There was, what's the program intended to do? It's intended to learn your culture, your identity, who you are as Dakota people and also your language as well. So that's something we're going to be incorporating. There hasn't been much language on the forefront, but if you walk around the school, it's basically bilingual in Dakota and in English. You see a lot of schools. Sometimes it's French and I thought, I know there's another school in the city, it's Cree as well. So you have a very diversified city right now and then there's a lot of reconciliation going on and working with our Indigenous peoples as we have one of the second highest population, I believe, within the region. So the program is meant for everyone to learn and learn who the first peoples of Canada are, right? So we're trying to educate everybody about who we are and also our own people as well. So we're definitely trying to keep that tradition alive. I think Dallin had a good point. I still remember this from our school opening. It seems like a million years ago, but it was only about five months ago. I think we have about 45 kids from White Cap that come out every day and certainly, I hope this is a welcoming, inviting place and Dean spoke about that transition from schools they were out last year via Charles Raddock or John Lanker, Budivist, I think, for some of our students. And that learning is tailored for those students but also for the wider audience. There's another 560 or so students that need to know the truth about reconciliation, about treaties, about the history of our province and our region, and so that excites me a little bit, I guess, as well, to get the story straight and to make sure that we deliver that through our curriculum and to have those supports again is huge for all 608 students, I think, what we have now. So that's a big important part of it. I think one of the things, again, just a little different angle on things is we want all of our students who attend the school to feel like this is their place and so for the White Cap students, this is a big brand new school and our partners have put money towards this that they added to the amount that we could spend on our school and you can see it reflected in the dirt walls, dirt being D-I-R-T-T, and it explains some of the history of the region as it relates to the Dakota peoples and I think part of the goal here is to make sure that the White Cap students and families that are transitioning here feel at home and feel like this is their school and so I think some of that is reflected in the design of the building. We also have a culture room, which is unique. There's been eight P3 schools or four sets of two, if you will, between the separate system and the public system. This is the only one that has a special feature like a culture room and that's where we have our ceremony each morning to smudge and to start the day in a good way. We also, our elders and our support workers work out of the culture room sometimes and it's a space for families that they can come in and have a spot that they feel like they have some area that's theirs when they come into the school. How do you measure the success of your program? Do you notice a difference or change in participants at the end of the program? Is enrollment high? Is the demand for the program high? That'd be a question for you. Yeah, so we have, I guess, what I would call traditional measures of success in school where students get a report card three times a year. One of the things that we just completed here and haven't got the results synthesized yet or put together is our tell-them-from-me survey and we were able to disaggregate how our students who live out at Waycap are feeling and relationship-wise or what their perceptions are of the school and how they're enjoying it or not enjoying it or what their perceptions are. So we look forward to kind of getting into that a little bit and seeing what we need to know and reflect on that. We, early on in the year, have had lots of open houses for our parents to come in. On February the 15th, I believe, is our next one out at Waycap, just for our community out at Waycap to take our staff out there and have a little meet and greet and get into small table groups and sit down with parents and talk about how things are going. We're kind of halfway through our first year right now. I think January 29th is for the halfway point of school year. As we sort of develop those routines and relationships, one of the things that we really focused on in our school, along with all the curricular outcomes in every subject is, again, this piece around cultural language but also the relationships. In our first year that we've been open, to me, Tim, that's very important that students feel welcome here, that students feel like this is their school. I think Dean alluded to that a little bit before. How do we make every student feel respected and honored and part of our team and sometimes that involves when kids do things that might not be part of what we're about. We have to find a good way to sort of support them and make good decisions but also celebrate when we're doing things right and get kids on board with what we're trying to do here. I think in that respect we're probably like many schools in our division at the start of the year. We've developed procedures and classrooms that are set up for kids. We've just reviewed that. We just spent a full day here on Monday looking at that again to sort of review how are we doing, what else do we need to do to particularly work with students from downford to the diversity. We have about 45 students from White Cap and another 30 or so students from other First Nations who've declared. About 116 students from I want to say 42 or 43 different countries so it's a very diverse population for sure and we spent a fair bit of time on trying to make everybody feel a part of our crew here and to make students feel like that's my school, that's where I belong, that's where I go every day and I'm proud to be here and I'm enjoying my teachers and I feel like I'm learning and those are those things that we try to get to so there's some formal things around academics I guess Tim, and I don't mean to I probably said that with a tone in my voice I don't mean that to sound like that's a bad thing those are really good things but in our first year especially I want to make sure that we're getting the relationship piece right and established students feeling comfortable feeling like this is a good place to be and they can come every day and I think they have an ally or two here at the school on their behalf that is looking out for them and has their best interests is trying real hard to get to all those outcomes to get their education so that they can go on I think just measuring the success is that the measuring success program? I just think just a lot of us our leadership and white cap we get a lot of parents come up to us so they're concerned about something or else they praise the program so we want to hear good things about the system and what the program that we've established in place and the partnership that we have in place because those are things that have been mandated the ideas come from our leaders so we bring them back to our community our community membership and we ask them is this something you want to go forward with and we get to vote and everyone usually for it we explain the benefits and we explain the negatives as well but definitely the benefits away the negatives and once we hear good feedback this is our first year we'll do a survey we'll talk to our people we'll have a community meeting we'll have I guess an outing here maybe a barbecue again in the fall for our students welcome back but it's definitely just getting the feedback from the parents and also the youth as well how you guys feel at the school you guys feel comfortable there and then once we know that they're feeling comfortable then they're in a good environment to start learning they need to be in a good environment when they're learning whether it's their language whether it's different languages French, math, English whatever it is definitely and also making new friends is key as well so we'll be hearing back after the first year but that's how we're going to measure it we're going to have to come back and talk to the parents and talk to our youth as well just a couple things to add I guess we measure success I guess a lot of times by looking at students reaching the curricular outcomes for the particular grade that they're at and so we want that for all of our students that are attending Saskatoon public schools and we want it for all the students that are here attending Chief White Cap School and so we want to celebrate all the things that are going great so for example the school being brand new is in the process of figuring out what their name and logo will be moving forward and while we haven't made a final decision we think we're pretty close and the visual that's come with that is actually the idea came from a whole bunch of different areas but one of the students who's here from White Cap had some leadership in that and so those are things that we want to celebrate the students that sometimes needs extra supports all of the students we want to get that right so that we can keep students at grade getting their curricular outcomes in place and moving successfully through the transition through elementary school we also want like Dallin mentioned this but I just want to reinforce it we need to ask our community how we're doing and so one of the strengths of Harold and his team here is Harold's a great communicator as the principal and he has been out and talked to the community on a number of occasions while we were preparing to open Chief White Cap School and once we're going here with the great things that are happening or some of the concerns that come up we want to keep that line of communication open with the First Nation, with the community and with the students so we'll be asking those questions and we'll find out where we're doing well and the things that we need to improve on are you guys willing to share any supporting documentation about the program with the NCCIE so I'll not quite defer but I do know that with part of the partnership that has to be something agreed upon between both our school division and the First Nation so if you're talking about these specific binders the agreement, things like that like a syllabus or outline I guess the websites, your key probably your key starting point it's public, it's everything, kindergarten, grade one, grade two and that's exactly what these are so you can print them off it's obviously transparent, you can just walk in there and print whatever you want off on there and just a little bit of background like this is our partners from White Cap supporting financially to go through a process to hire two consultants to work with the community, the elders, the parents the students to create the resources and the lesson plans which we have by grade here so we've got a couple examples to grade seven and a grade two binder but there's one for every grade and you know to create the website and all those kind of things so I mean Saskatoon Public Schools benefits from the fact that this is extra work and cost that our partners have put in place so that we can use them to be successful at Chief White Cap School and also spreading out into other schools with Saskatoon Public so just a little bit of background on the website before you get on there and have a look at it the other thing Tim, I guess too is the other piece of documentation in terms of what's taught at the school that's provincially mandated so we can send you the link that is the Ministry of Education so again, whether you go to school and LeRange or Estevant or all parts in between all schools follow the same curriculum and then within each school teachers have a little bit of leeway on how they get to each of those outcomes so the great part that I'll speak for our staff at the start of the school year some are walking in and going do I have to be fluent in Dakota and we've had lots of supports these being part of that the website now being up and running the work that the First Nation has put into getting Kevin Tachin who's a language person from University of Brandon out here worked with our staff once I think there's a conference coming up here that does May end of May, last week of May is a Dakota Language Summit it'll be our first annual so we'll see how that goes so that's an opportunity if we can get two, three staff out there to that to sort of bring back some of that knowledge to our staff pieces that we'll contribute to our specific work around Dakota Language and Culture but in terms of documentation so the website has given you some background there but the the Saskatchewan curriculum is also part of what we all do at our schools across the province I think Tim just one thing to add there's a formal document called the Alliance Agreement it is a legal document that White Cap Dakota First Nation and Saskatoon Public Schools took a couple years to develop you know with lots of good input from the federal government the provincial government was certainly aware of what was happening chief and council of course and Saskatoon Public School our board level and so that agreement is kind of a foundation for our relationship in terms of the education part of doing good things together and it's up for renewal right now we're in the process of looking at the first four years of it because it's going to come due here August 31st 2018 and we're going to look at the great things that have happened as a result of the Alliance Agreement and again we're going to look at the things that we can tweak and do better moving forward and so there's an evaluation happening right now but that's a foundational document to everything that's happening here with our partnership okay so in your opinion what is indigenous education like how would you define the word indigenous is it a term that you would normally use I think indigenous education would be like I said teaching your values your language, your culture and your identity whether you're a Cree or Soto, Ojibwe I think that's just the term you need to be used you're teaching who you are as an indigenous person and then you're incorporating into the schools with Chief White Cap school or any other school in the city of Saskatoon so indigenous education is coming from your roots of who you are as an indigenous person so I see that just keeping an eye on who you are and your identity and learning it and also teaching others about who you are and your history and who you are in this country as well so I think it's important for the kids that don't know the first peoples of this country they hear a lot of the derogatory things I've gotten it growing up all my life so nowadays we're getting away from that we're all working hand in hand now and we're educating each other on who we are and a lot of people are from other countries so we're learning about their countries as well so it's good to see everyone's learning each other's histories and background one thing I did I think bang on the piece that I think about as well is so we got to get the story right and we want to make sure we do justice to the facts and not to oversimplify it but we can learn about an event or something like that but to sort of get inside kids' hearts a little bit too so changing attitudes, changing thinking beliefs a little bit is part of that education as well and there's a big again in the SAS Learning document but it's just good thinking is that critical thinking piece like what do I know and now how do I think about things based on what I've learned what changes do you make how do you think differently what actions do you take that are more respectful to all cultures so what I think of Indigenous education is education downspoken to culture I would put in there and valuing that as well for all kids whether you are Indigenous or not we all belong here and we all have a voice in the seat of the table that's sort of a metaphor I guess but I do think that's part of the piece that's important to me moving forward to bring some value to that as well just real quickly there are two high schools that are involved with the following their voices work where there's a cohort of staff which is growing each year in those two high schools that look at a specific way of engaging our First Nation Métis students in the classroom and I think some of the lessons that I've learned as I've listened to the themes that have come out of that work in those two high schools is number one it's all about that positive relationship and creating that positive relationship I think between not only the teacher and the student but also between students and like Harold said making sure that students see themselves in the school which they're attending and another big part that I've learned through the following their voices work is the ability of using discursive teaching strategies to bring response and voice to the Métis students in the class and I think in a lot of ways it's about sharing that power that the teacher sometimes is seen as that person that has all the power and we're looking to share that power with the students so that they feel like they have ownership and can bring their experiences to bear in the class in a good way so I know those are high school examples but what I think is happening here at Chief White Cap School is there are classrooms at an earlier stage and so these teachers are teaching with those kind of themes and ideas starting before students get to high school and so I see a lot of the following voices work they might not call it that here at Chief White Cap but they're doing it How would you define education? Sorry How would I define education? Over the next 10 years right? No it's still in the Indigenous education in general? How would you define education from an Indigenous perspective? I think Dean's alluded to some of that you know having a voice I'll think back a million years ago and I often we hear this last time well when I was a kid and old guys like me sometimes say to Dean's point teachers stood at the front and the teacher was the purveyor of knowledge I have something I'm going to give it to all you students and I think Dean's alluded to how we not to share that power but learn from each other and there's a million learning opportunities in a school every day and they don't all just come one way from teacher to student or principal to staff there's I guess the spirit of A we want to show up and learn from each other and with that trust relationships have to be in place to make that happen because if I don't feel like I'm part of this place I'm not going to speak up share my story or share who I am so we kind of want to focus on that at first and that's I think that's true of all of our students not just our Indigenous students but in particular our Indigenous students who in the past maybe felt like they haven't had a voice so it's important to get that part part right in there What is your vision for the future of Indigenous education in the community and in Canada? I think we're second precedent here with our partnership with White Cap and SPSD and also one of the things too is the reason why we did this is the reason why we did it is we wanted to incorporate our language into the schools that our kids are involved with but another thing too is the funding that our children received is adequate we're receiving close to 6500 per student and then now I think we're up to 10,000 per student so there's a major gap that we've closed with funding you know there's a lot of kids, there's a lot of dropouts and they don't get the same attention or the same I guess quality of education that other kids do in the province so we wanted to make sure that we diminished that education gap and we did that by signing this agreement with SPSD but in that agreement we wanted to make sure that our Dakota values our language, identity and culture were still upheld at the highest level so we're both honoring that and we're both working together to meet that to meet that so eventually in 10 years we want to be able to see our kids coming out of there speaking their language, speaking their Dakota tongues and passing it on to our next generations because as First Nations people a lot of us are losing our languages I think there's over 300 linguistic languages don't quote me on that but across the country and that's First Nations so we don't want to lose our language so that's why we're trying to make sure that we uphold that within the city of Saskatoon and also White Cap Dakota so that's why we see ourselves taking care of our language and making sure that our values and who ours Dakota people are always remembered and valued and passed on to the next generation like you said, what is education it's passing knowledge on from one to another that knows a little more than the other learning the student always teaches the teacher as well I would think looking forward 10 years specific to this program we would have a Dakota language teacher full time or more than one or maybe two, it depends on how big our school gets to but that would be front and center of specifically a curriculum kind of objective I guess, Tim the part for me that I think about in terms of fast forwarding is and Dean could probably speak to this more at the division 11 around graduation rates so our First Nations students there is a little bit of a gap and Dallas talked about a funding gap is closed, I'd like to see that gap in graduation rates like on time graduation rates close a little bit and I know again high school example but when students are engaged and want to be there that is never a bad thing and we're going to see some bang for our buck there a little bit when kids are here and want to be here and feel good and have that positive relationship trust with their teachers, with their community with their fellow students this is a good place to be like I want to get up and come to school and do everything I can to be there and I think that's on us a little bit to certainly create it here but sustain it over time and grow it I want the story to be for students at white cap 10 years from now that in grade 4 they're excited oh next year I get to come to chief white cap or in grade 3 they're thinking about a couple years down the road or whenever it starts because it is a transition and if we can make that as smooth as possible and as positive as possible for kids and make this a positive place where yes we're having a high standard of learning that's going on but we're going to make sure that everything you can to facilitate that through positive relationships and supports and community and parents and staff working together I think that takes a little bit of time to really solidify and I certainly hopefully over 10 years for sure we can really grow that just a couple things from my perspective I want to start by echoing that Dallin said that I think what we have built here in terms of the partnership and the alliance agreement and chief white cap school and Charles Redhawks school and working together is unique and it's in our context here so I don't think necessarily you can just take what we've done and replicate it somewhere else and say it's somebody else's answer and they could take it and run but we're very proud of what we've built to this point by no means do we feel like we're finished or that we have it all right and I think that's the beauty of any partnership but what I will say is that there's trust in place so that between the two organizations when we need to celebrate many of the good things that are happening we're getting pretty good at that and there are lots of things to celebrate and when we have some bumps along the way we know we can pick up the phone and have good honest conversations so that we can figure out a way to work our way over around or through those barriers that happen for our students and our families so I'd like to start there the other big piece is the truth and reconciliation commission calls to action and I see that on display with what we're trying to accomplish here and so over the next ten years there are many aspects of that document that I think we need to keep an eye on in terms of both these folks have mentioned Indigenous language and culture and so I think we have to start but what are we going to do to grow some of those things over the next ten years so that we can continue to be at the forefront and a leader for our families and students at Chief White Cap but also in a bigger way with Southend Public Schools because we have other Indigenous languages and communities and interests as well so it's all part of it and I guess I just close the little piece by saying the relationship and the reciprocity are two terms which I come back to often in my work because sometimes I get the question from my colleagues in other school divisions about what Chief White Cap First Nation might be gaining on behalf of this alliance agreement and I listen politely and say yeah there are some things that I think we can do to help with the relationship and support students and families however I don't really think they understand what we as a school division gain from White Cap that's a story that often isn't told as much and I'll just give one example we have a learning opportunity out at Charles Redhawk School with a hoop house that's being constructed on land-based education through the lens of growing and so that's a connection that Chief and Council had and they have brought in the hoop house itself and they're going to be teaching their K-4 curriculum according to the province of course but through the lens of this growing through the hoop house and it's tremendously exciting to see the students and the staff and the community involved with the potential of what's going to happen out there and as a school division we're going to learn from that and potentially learn from it replicated in different parts of other schools within our system and that's just one example but there's reciprocity in this partnership we're learning as much as we're giving into the solution here so that's enough for me okay can you think of any types of information that if you had now it would help to achieve your vision any types of information to help achieve our vision for like 10 years from now you mean? like what information would we need to get there? this question does not have to be asked during the recorded part what information materials resources do you need to achieve that vision like aside from the programs in which you are personally involved what information do you have on other Indigenous education programs in Canada? I just think we have the resources we have the people in place we have the partnership it's a productive positive progressive partnership I think we have what we need more or less it's just it'd be nice to have more of our elders be involved and to continue to give their guidance and their leadership and their history on our past as Dakota people and I think the continuance of SPSD's executive and their staff to make sure that this partnership continues to survive and strive so I think the resources is just basically everybody continues to be a part of the game and be a part of the team and we feel very positive that that relationship will continue that's what I see Harold touched on this but I think I'll just throw it out there to find that Dakota language leader somebody who's going to come in and help guide and work with Chief and Council and the community out at White Cow is going to be a critical position and so there's a process in place where we're going to be as a partnership looking for that individual but I'm just saying that I think it's going to be really important for our progress forward with the language I think I would echo sort of what Dean said in terms of a resource or something moving forward that would be certainly a key asset as we move forward to advance that work you know I think I'll steal some of the downsides there's lots of good things in place already and I guess I just for me sustaining that positive relationship where when we're doing things right we can celebrate it when we get it wrong or we need to tweak something that we can go pick up the phone and say what do we need to know and for me over the next year or the rest of this year we're moving forward however many years I'm here I just want to make sure we keep dipping our toe in the water for our community to say what's going well what do we need to do get some ideas and some feedback and we have a mandate of a Saskatchewan curriculum but within that lots of flexibility in every school and how teachers and how schools achieve that and development how something works out there so can it work here what things are unique out here and we learn that as we go and we talk to our partners we listen to our elders we combine that with our people from our side I guess from Saskatoon Public and keep that sort of synergy going where you can come together often and stay on the same page throughout that extended period as long as we're here we're going to try and do that in a good way Anything else you guys like to add? It's good for us to sit together and to have this conversation I think every time that we chat about things related to the partnership or what's best for our students I learn something and so today's no different so I thank you for bringing us together


Well, hello everybody and welcome again to another OpenShift Commons briefing. I have my good friend, Nox, from Cystic who is going to give us a briefing on security and forums, express practices on OpenShift and tell us all kinds of WTF things. I'm loving that you use that in the title because I think it's the first time anyone's ever used that. So that's great. And I'm going to let Nox introduce himself. He'll do a good job of it. He's promised a pretty lively demo. If you want to ask questions, ask them in the chat. We'll make him pause and take a breath and he can answer questions. But otherwise we'll have a live Q&A at the end where anything that doesn't get answered in the chat will reiterate them and we are recording this session. So Nox, take it away. Awesome. Thanks Diane. So, hey everyone. I'm Nox from Cystic. I work on the product marketing side for Cystic Secure and we've actually got some awesome content for you today. We're going to be covering mainly a live demo. I'm going to go in, cause some vulnerabilities to happen and then look at a live OpenShift environment, how you can do forensics in there and do a bunch of other stuff. So I'm going to try to get through these slides as quickly as possible and then get down and dirty in the command line and show you everything else that's going on there. So what's on tap for today? We're going to talk a little bit about security with containers at a high level. How it's changing, how you architect your applications, what you need to kind of build out your systems and how you can actually enable better security through OpenShift and containers. Then we're going to move on to kind of the architecture that you want to collect data from your systems, look a little bit more about the Cystic Secure capabilities, how we can help you deliver secure services through OpenShift and then go into the live demo and instrumentation from there. High level on Cystic, we're the container intelligence company and we're going to provide a unified security monitoring and troubleshooting from a single instrumentation point. And a background on us, our founder was the co-creator of a popular network packet analyzer that many of you guys have probably used called Wireshark. From there he went and launched Cystic, our open source project, which is kind of like if you took TCP dump, LS off, S Trace, H Top and just smashed them into one and then layered on some container goodness, that's our open source tool. That launched in 2013, a million plus downloads and hundreds of thousands of users there. And then from there we've launched our container intelligence platform which is made up of Cystic Monitor, Cystic Secure, and we have 300 plus enterprise customers using that to kind of safely and securely deploy containers into production. And we have really deep integrations with OpenShift and use of major enterprises. So we take all that OpenShift metadata to heart and allow you to really layer that on for service performance monitoring, service oriented security, all those kind of things. So what we're going to really talk about today is the convergence of two challenges. First the one of kind of operating containers in production, what that means, how it looks for different groups, and then go from there and look at how you can enable effective scalable security of these diverse past workloads that you're running on OpenShift. All right, so containers are everyone refers to them as black boxes and they're great for development and great for operations, but what does that mean for your like your knock or your sock teams that are really there to focus on how do I get visibility into those systems? So on the development side containers are awesome, they're black boxes, you can put your code in them, you can execute that, they're repeatable. And then on the operation side, you can move these around really easily. Now my database doesn't have to be on one node, it can be on multiple nodes, it can be scattered out through OpenShift, and there's all these layers of orchestration that are making it really easy to deploy applications in multiple locations. But how do you keep track of all those containers as they're moving and they're scaling without going and putting in a sidecar container or something like that? And then how do you also make sense of these services that are now scattered across multiple nodes and make sense of them as that single logical service or that OpenShift deployment and the pods that roll up into them? So this is kind of some of the challenges that you'll face, but with challenges always come opportunities. And we really think that containers offer an opportunity for you to have better security. So there's controllable attack services. It's a single isolated container, that black box that we looked at before, should really only have one process running inside of it. So it makes it a whole lot easier to kind of lock that down, get that isolation through your different C groups and namespaces as well for that controllable attack surface. You also have much easier time doing robust configuration and change management. So it's really easy to roll back to a certain image or make a change to an image and push that out across your whole infrastructure really quickly, then kind of going in what we're seeing in your typical VM mode right now, where people are going out and having to patch different servers, patch different services. With containers, you can just cube CTL or deploy a new OpenShift service. And then from there, you've deployed a new version out to your entire infrastructure. That same process isolation also makes it really easy for you to do anomaly detection. So if you've got an InginX container and it's communicating through non-standard ports, or if there's some other process besides InginX running inside that container, it's a whole lot easier to go and spot, okay, something's going wrong inside this container rather than this VM where you'd have tens or hundreds of processes running on top of it. And then it also really lends an opportunity with containers and OpenShift to do more of that zero-day threat protection and behavioral monitoring. So looking at the activities that are coming from those containers and running those through a pipeline so that those easily baselineable activities, you can then spot anomalies against and really look for fundamentally malicious behavior that's happening on those systems. So how can you really deliver that security to your environment? And you can really do that if your security stack is architected for containers. So what do I mean by that? You need to have full visibility into every single container that's running across your infrastructure, down to the process level of what's running inside the system calls, without you having to do any of that per container instrumentation. Next, you need to have kind of automated adaptive security policies. The policies that you can scope to a certain OpenShift deployment or even the individual pods that roll up into a deployment and have those policies that are going to scale as new services come out and really rely on the metadata and the different things that your orchestrator like OpenShift is providing. The thing that I think is probably the most important is this non-disruptive unified instrumentation. So if you're deploying 10s to 20s of containers per host and we're really seeing the density kind of grow up as more and more companies are moving to use containers in production, you really don't want to have a sidecar container or go and inject some process inside each one of your containers. So you kind of need a single unified instrumentation that isn't going to go and mess with the Docker daemon or be going and sitting as a sidecar to each container. You need to keep that instrumentation kind of lightweight from a single point on that host without having to go and think about those containers as each individual point where you want to instrument. And then last being service and orchestrator aware. So understanding exactly how OpenShift is deploying your containers across your infrastructure and then having specific policies and actions that are tuned against that. And then also giving you the ability to use that metadata to then go and track down all the commands that were executed across a specific OpenShift service or the pods within that. All right, so now that we've kind of gone to, okay, what do we need to think about with OpenShift and the containers that are running there and how am I going to deploy and operationalize security? Let's go and look at our architecture and how kind of we've addressed some of these problems. So before we get into that, I'm going to just talk a little bit about where Cystic secure fits in your security stack. So we're really focused on two main aspects here, runtime security and forensic security. So runtime security doing your intrusion detection, lateral movement, data exfiltration. So seeing if your database has spawned an unexpected outbound connection, if sensitive data was read from that, and really looking for kind of fundamentally malicious behavior happening on your host. And that can be through system calls, processes, ports, pretty much everything that makes a system call will be able to pick up and then layer on this runtime security. And then the other side with containers is forensics. And a lot of times when a container gets killed, you're basically screwed. You've lost all your data. Someone starts a shell inside that container. You can't really see what's going on. They've killed the container. It's all gone. We've really built a unique way to get a buffering capture of all the system activity, pre and post any security violation. So you have the full breadcomb trail of every single thing that's been happening in your environment. And this is something I'll go in much deeper to kind of in the demo. On top of that, we're going to integrate with your existing platform security and IT security. So we'll integrate with platforms, be able to pull in events from there. If you have vulnerabilities that are discovered, our back, things like that, we integrate with those setup user credentials, can ingest events from those into kind of our events API, and allow you to have a really tight integration with us and OpenShift there. And then for your existing IT security, our product is entirely API driven. So sending out every single executed command from that OpenShift environment to your existing SEM or logging tool, or just doing and all your user tracking to your governance committees and things like that. All the data that we collect can be fully exported out to any other system. All right. So now I'm going to get into the architecture. The, our container intelligence platform is really built up of two main components that I'm going to be getting into further. The first is container vision. And this is our ability to see all app activity, network activity, host activity without going and instrumenting any of your containers. From here, we'll also will automatically discover any application metrics, system metrics, all that kind of stuff on the monitoring side from that individual container that's running on the host. And then the second is service vision, where we're going to go and enrich every single piece of data that we collect and send through our data pipeline with all the metadata that OpenShift is exposing. And all of that can be sent to our backend, which you can use as a SaaS service or deploy it on premise on your own infrastructure. And that backend is something that can be fully managed by OpenShift or Kubernetes as well. Okay. So from there, that single instrumentation and that single backend, we actually layer on three different products. So you can use SysTig secure, SysTig monitor or SysTig inspect. And there's no performance impact of using any of those on top of each other. So you're just are really going to have that single container per host that's going to give you full visibility into everything that's running. All right. So I've talked a lot about how we use this data, the data that you want to collect from containers, but how do you actually go about doing it? So what we're looking at now is a simple host. I've got a host OS running here. I've got a custom container. I've got an open source app. So something like nginx running here. And what we do is deploy our agent as a container or a process running on that host, our containers Red Hat and OpenShift certified. And from there, that container is going to load a unique kernel of instrumentation that we have. This instrumentation is part of our open source tool. It's part of our open source security tool, SysTig Falco, and is using kind of millions of machines, government agencies, all that kind of stuff. And that kernel instrumentation is going to see every single system call happening from every single container through non-blocking read and then put that into a ring buffer where our agent can go and process that at user space to see all commands, events, take it performance metrics, basically anything that's happening on that host, we can see and detect, protect and troubleshoot from that single instrumentation point. On top of that, we've layered on a rules engine. So rules for kind of any, any file access, court scanning, any connection or executed program that's running on that host or within that container. We'll detect at the agent level and then allow you to do policy enforcement. So killing a container, pausing a container, committing a container to then quarantine it, run it through workloads later, all from that, from that agent that's running on the host. And then the last component of the, of our architecture service vision.  And if you're looking at an open shift infrastructure, it's going to look a lot like this. So you've got multiple different VMs. There's a bunch of different scattered containers running across them. But how do you make sense of that as logical services? And that's where we're going to integrate with open shift directly and allow you to think of a logical service based on any piece of that open, open, the open shift metadata. So you can enforce and explore policies based on any piece of this metadata. And this is something that we've done for kind of hundreds of different companies with open shift on premise, using SAS, really whatever you want. That's something that we're here to support you with your open shift journey. And now time, the thing that everyone's been waiting for, let's get to the demo. So before I get to the demo, this is a time where I usually like to pause and see if there's any questions about our instrumentation, how we collect data and things like that. I don't see anything popping into the chat yet. So I wanted you to do the demo and I'm sure that's going to give us some questions. Okay, cool. All right. So what I'm going to do now is something that you'll definitely never see from any other security or monitoring vendor live on a demo. And I'm actually going to do an instrumentation of our container intelligence platform, running on a containerized host. So as you can see now, we've got kind of no, no data coming in. I've got system monitor running here. I've got system secure running. Really, nothing's going on in these environments. So now I can pull up my instance, run a quick Docker PS. You can see I've got a simple WordPress application running here. So I've got a load balancer database, some WordPress services here. And now let's go and get that command to run our agent. So I can copy it right here. And let's switch over an assistive monitor so we can kind of see the real time data stream in. And I'm actually going to just going to remove the dash D. So then we can see the output here. All right. So what this is doing is it's loading our kernel module via DKMS. So we're going to look at the existing version of your kernel, build the module on top of that. So it's not going to require a kernel restart or anything like that. And then if we scroll up within here, you can see we're doing a bunch of different checks for if Kubernetes is running stats, the metrics, if they're in the environment, JMX sampling, all of that all automatically. Pulling any certificates, searching out for any AWS metadata, mesos metadata, and then pulling all of that automatically. And so now if we look kind of over into SysTik monitor, you can see all the different containers that were running have pulled up. We can drill that into something like this WordPress container, see the performance of those. But let's actually go and kind of look at it from a topology perspective. This is one of the things that kind of anyone in the PCI compliance space will see. You need to see every single network connection that's going on in your environment. So if I go over to hosting containers here really quickly, click back on entire infrastructure, I can see every single connection that's coming into this host, then drill down, see all the containers that are running there. I can even actually see the SSH process that's running on this host from the ISP provider that we have in our office. And then I can actually go down all the way into all these containers and see the individual process that's running inside and the network impact and all the network connection. So this is something we installed our agent on the host. It automatically discovered all this, had this pre-built mapping. And then you can actually go down a step further. And let me switch this to container name really quickly. Go over to something like MySQL. And we're going to automatically detect that MySQL is running. Start pulling things like number of requests, number of errors, top queries, slowest queries, slowest tables, all automatically without you needing to do any other additional instrumentation. So here we're actually decrypting that TCP connection and then reading the file descriptor. So you just install the agent and all this is discovered out of the box. So we've seen some of the visibility that gives you automatically. Now let's go in and do some stuff that you wouldn't expect or want to happen in your environment. So I'm going to go back over here. Now you can see that we've got the sysic agent running. And let's go in and exact to one of my WordPress containers. All right. So now that I've kind of shelled into that container, let's start doing some stuff that really should never happen in your environment. So I'm going to go in and change and replace it, copy it over to switch it over to LS. So basically now what I've done is kind of hit in the curl command as something that can be kind of executed by kind of one of your standard system binaries. So then from here I can go and go LS openshift.com and I've essentially gone in and replaced kind of LS with curl and I've kind of masqueraded that as a different process. So let's go over and look at this into secure and see kind of what we've detected. So first off, no one should ever be able to shell in a container from what we've just seen because basically now I can hide everything inside that container, execute stuff across my entire system once I got access inside. So let's look at what actually we discovered in sysic secure. First off, there's a whole lot more red than before and I can actually open up that host and click on that WordPress one container and then switch over to this list for you and we can see, all right, first there's this terminal shell that was running in a container. We had that right below a binary directory and then there were system processes that had unexpected network activity. So I can click on any one of these, get full details about kind of the scope where it happened, the individual container, the host and then actually the full output here with user commands and everything else that was running. I can also hop over to the command history, click on the host, see every single command that was executed with full scoping of where it happened in my environment as well. So I always like to do the install to show kind of how easy it is to get up and running and out of the box of visibility you're going to get from both a performance monitoring perspective as well as a security perspective. All right, so now I'm going to hop over to kind of a more robust OpenShift environment that we've got running and look at some of the different things that are going on there. So first off, I'm going to start with our policies and right now we're looking at them by severity. So we can see kind of some of the high severity policies that are running in my environment, different file policies, network policies, things like that. But since you're using OpenShift or any and deploying services and managing services and exposing those to developer groups, you really want to think of those as your logical entities that you're trying to protect. So now I can go and look at my entire environment based on scope and see the policies that are running across my entire infrastructure, protecting the hosts and containers, but then actually drill down into kind of specific deployments. So I can go in where we're using the deployment name equals Redis and trying to detect if there's some unexpected outbound connection for Redis. So your database, you don't want it hanging out to the outside world and kind of tuning these policies on a deployment by deployment basis. I can also go in and add other data services to this if I wanted. So we can look at it from that kind of that logical perspective again at something like mySQL and drill down from there. From any policy, you can take actions so you can go stop the container, pause the container, or create the assisted capture. And the really unique thing here is you can tune this for different policies to see how much system data you want to capture pre and post any policy violation. And since we're going to be writing kind of every single system call to that to that SCAP file, for anyone in the audience use to use something like a wire shark or TCP dump, this is kind of like a TCP dump of your kernel where you're going to see every single system call pre and post that security violation and then can troubleshoot that later. And we'll go through some of those examples. And then from here, you can send it out to kind of page-to-duty Slack, Victrops, Opsgene, send it to CloudForms via webhook kind of all automatically there. All right, so now that we've seen how policies are created, let's go in and kind of look at some of the events that have happened in this OpenShift environment. So if you're looking at your infrastructure from a typical perspective, you'll see something like this. So you've got a bunch of different hosts. There's containers running on them. You can see which containers have had events and things like that. But like we've talked about before with OpenShift, you really want that service oriented security. And we can switch over to this deployment's view here and then drill into something like this Java namespace. And one of the easier ways to actually look at this is to go back to that topology map and go in and explore where violations have happened kind of based on that logical infrastructure. So here we've drilled down into a specific namespace. We can see all the deployments that are running in them, drill into a specific deployment, and then actually see where the event happened at a pod or container level and all the different network connections and the dependencies that have happened there. So let's drill into kind of this policy violation that happened with Redis. And we can see, okay, there's an unexpected outbound connection and then a sensitive file was read. The really cool thing here is I have the full scoping of where this happened from a logical perspective as well as that host and container. So if I need to go and quarantine that host, I can do that. But then I also have full knowledge of where this actually went and affected my open shift deployments, pods, or any services that's rolling up into. We can drill down further and look at the output here. So we can see, all right, there's an unexpected outbound connection from this F test command. And then after that, a sensitive file was open for reading by that same F test command. And they're actually going and reading from Etsy shadow. So they've immediately come in, got access to my hash passwords, and are going and reading from it. So this is kind of one of your classic data exfiltration examples that could be happening in your environment. And from here, you can kind of tune this. So, okay, if I ever see something like this happen again, I can kill the container or customize any of the out of the box policies that we have in our environment. And kind of all of these policies have been pulled in from they are rule engine integrates with our open source tool cystic Falco. So we have tons of policies that have come in from the open source community, things that cloud.gov or Yahu is using to protect their infrastructure. And then since we've been monitoring millions of containers with years for years with cystic monitor, there's a lot of policies that we've auto generated based on classic workloads or baselines that we've really seen from your containerized infrastructure. Let me ask one of the questions that just popped up. I think that is there an ability to stop an entire pod altogether if a security violation is detected. So we can stop, we can do kind of container level stopping of those containers. One of the things that you can also do is webhook out to the cube API to go and stop a pod from there. But the enforcement is done kind of at the container level right now. Okay. There was one other quick question Doug was asking, what is the persistence store technology for all the events and logging for the cystic agent? Yeah, great question. So our back end architecture is really made up of two main technologies. The first would be Cassandra. So all of our time series metrics and things like that are all sent to our Cassandra database. And then all the commands history events. On the monitoring side, we also pull in any Docker event or Kubernetes event. So if you've got a crash loop back or something like that, all of that data is sent to Elasticsearch. And those are the two main components. Both of those have REST APIs. So if you want to export any of the data that we're collecting, you can send it out. So we have a lot of customers that are kind of taking commands history data or event generation data and sending that out to things like Splunk. Cool. All right. Carry on. Thanks. Cool. Awesome. That was a good break before we get into some forensics. So thanks for sending those in. All right. So now I can go into this WordPress environment, this namespace here, and drill down into this specific WordPress deployment that's running there. So we can see this policy violation that happened where there's a shell in a container, kind of the same thing that I showed before. I can click on it, see kind of that same logical information that we saw earlier. But here with this policy, we actually recorded a capture, and then there's commands that are associated with it as well. So I can go click on view commands, and this is going to drop me back in time to that point in time when the event happened and give me all the commands that were executed around that specific security violation. So from here, I can see, all right, the user spawned a shell. They curled down a URL and then untart it. So from here, I can actually click on any row and get really deep information about that specific command. So we can see from the full command line here, they actually curled down a root kit. So this looks sketchy. I'm definitely going to want to do further forensic analysis here. We can see the working directory, the PID, user ID, shell distance, all that kind of stuff automatically. And then that user untart that command, and so they've done some pretty malicious stuff here. I can click over onto captures now and do further analysis of that capture at that point in time when the event happened. So if I click on this button here, we're going to open up Cystic Inspect. And Cystic Inspect is kind of our forensics tool to do a full analysis of kind of every single thing that's been happening in your environment. So you can see kind of all file access patterns, network activity, network apps, app log messages, your full HTTP requests and payloads. All of this data is going to be captured here in a really easy to filter way. So let's set this stage first with looking at when did that notification happen? And then I can isolate a specific time around that notification. So we can actually look at kind of sub-second granularity in here if you wanted to. And then start overlaying things like kind of file access patterns, network bytes in, and then those executed commands that we saw earlier in the command history. So this is right here when that user spawned the shell.  So any one of these tiles you can drill that into and get really rich information kind of about that tile and use that as a jumping off point. So right now we can see those same executed commands. So I can see the users started a shell, curled down that root kit, and then untart it. And then from here I can actually drill down in and do further analysis of what actually happened when that tar process was executed. So if I double click on that tar process, and then switch over to this files view, now I can see every single file that was written at that point in time when that tar process was executed. So we can see basically that root kit was unzipped. It wrote a read me and install script, all that kind of stuff. And then from here we can actually go in another step further and use our IO streams functionality to actually look at the individual contents that were written to that file. So just taking a step back here, we detected a user spawned a shell in a container, kicked off a capture, and then can go and drill down all the way from what individual root kit they installed from there, how it was unzipped, every single file that was written, and then the actual individual contents that were written to that file. Any questions right now about kind of the forensic side, cystic inspect, how that works, and things like that? There's one question here, can network payloads be inspected and viewed? Yeah, so let's go into kind of this HTTP request. From here we can see basically all the different contents, the headers, things like that. So right now we're pulling in seeing the individual kind of full payload of these requests. I think that answers his question. Awesome. And then you can get your fork counts, fork trees, all that kind of stuff all within here. If you want to see all the different processes that were running, drill down into kind of the individual system calls from a process, all the way down into really every single thing that made a system call during that point in time, you've got this full visibility. And the really nice thing is it's buffered. So you can see what led up to that security event, how they might have gotten access, and then how it was affecting all the systems and everything else that ran afterwards. That's about it that I had planned on the demo side today. Right now I'd really love to kind of open it up to questions and hear everything else that kind of you guys have to say, or if there's anything else that you really want me to show. Well, what I would like you to show while we're waiting for people to ask questions is perhaps your final slide on how to get a hold of you. So while we're asking questions and anyone who's watching the video can see where the resources are to contact you afterwards. Here we go. So actually don't have one of those slides repaired right now. The easiest way to always contact us is on our website. So within here you can actually start a free trial of SysTig monitor or SysTig secure, request a further demo, do all that kind of stuff. So if you go to SysTig.com you'll have full access. And then if you want to follow up with me directly, my email is really easy. It's just knocksknox at SysTig.com. So you mentioned Falco. Where is that hiding in the internet and on GitHub? And maybe a little bit about how you differentiate the open source stuff and the commercial stuff. Yeah, so Falco, it's got its own GitHub page. So Falco is really the rules engine. So it doesn't allow you to take actions, pull in any of that OpenShift metadata or things like that. But it's our open source security rule engine that's kind of similar to if you had combined like some things from SE Linux, some things from OSAC, some stuff from S Trace, kind of and built it for containers. That's kind of where SysTig Falco sits. And it's really that behavioral activity monitor. So it'll just send alerts to standard out and things like that. SysTig secure is really built for securing and monitoring that entire platform where Falco is more of a single host behavioral activity monitor. Perfect. All right. Well, I am not seeing any questions and your demo was awesome and it didn't crash in any way shape or form. So I'm pretty impressed with that since you said this was the first time you were doing this variation on it. So kudos to you for pulling it off. Again, give people a couple more minutes, couple seconds here. If there's any questions, there's a bunch of people on there, but they've asked most of their questions during your presentation. So I'd just say thank you very much for your presentation. I know the folks from SysTig will be in London with us at the upcoming OpenShift Commons gathering that we're hosting again on January 31st in London. If you're looking for information about that, you can just go to commons.openshift.org and there's information there. There's one person asking a question now talking about how sort of product differentiation between some of the other security apps or applications like Twistlock or Aqua Security. Do you feel confident about that or would you like to hold that? We could maybe have a panel on that sometime soon. That's a great panel question. Just doing the highest level and then we can follow up directly a little bit more about individual features and functions. We're a container intelligence platform, so you're really going to have this single agent that's running on your host that's going to be able to give you that full monitoring visibility, full troubleshooting visibility, and security visibility from that single instrumentation point. So it's really one way to get full insight into every single thing in your system than having separate monitoring agents and things like that that are adding more attack services or more of a performance hit. So that's the high level of how we would compare against those and then I can follow up directly with more information about individual features and how they'd be comparing. I think that's a good one for a panel and an upcoming gathering or event. It would be interesting to hear that but I do appreciate you taking the time today and everybody who's joined us we will put the slides up on blog.openshift.com shortly along with the video and it will be up on our YouTube channel as soon as it's processed and ready, so probably by the day. So thank you again Knox for joining us. Awesome, thank you for having me Diane and thanks everyone for all the questions that you sent in today.


But now listen, you can have a little bit of a third of a breath. So challenge me please, okay? I'm going to show you guys some legs. I'm going to show you those legs. Those legs that I heard was from Coach John Smith. Now I'll show you guys some legs. But John Smith, Coach John Smith, I am. So now I'll show you another second leg. So this is what we're going to do. I'm just going to teach you kind of the ideas that you guys have to see. I feel situation, okay? So this is what we're going to do. If I'm going to right leg lead, if I'm going to right leg, if I'm going to left leg lead, I'm going to focus on your knee. If I'm going to left leg lead, knee to left. And I can still show you those legs to that side. So just so that you can see the right situation or the right position on this. And you're going to see your knee are getting disabled. It's like that, okay? So I'm going to let you know that knee is right. It's not locked, right here, okay? You need to be at least arm's length apart from here. I can't be here. Shoot a little straight knee out to there. Make sense? I'm not going to have that. Alright? I need to be here. I need to be here, okay? I need to be low and in here. Okay? I need to do this if I want to. I'm going to drop down. I'm going to drop down to here. Drop. Okay? Drop down and touch the mat. From here, my temple's going to be inside of me. Temple's the inside of me. Boom. Once I'm here, drop out of here. It's like my hand. It's a company ankle. My forearm's over the top of the laces. Okay? I'm here. Okay? My temple's on the inside of me. I need to post it. When you're out of penetration, it's a snatch. I'm going to shoot the low-singulate up here. I just want you to imagine this situation right now. And then we'll go from there. Got it? One, two, three.


A magistrate court sitting in Lagos State has denied embattled Nigerian actor James Omi Inka, popularly known as Babajesha Bell, and an ongoing trial over a alleged sexual assault. During the trial on Wednesday, Coyote, a labirant, his counsel prayed the court to release his client, citing his deteriorating health. He said the controversial nature of the case has made it difficult to secure his release, despite his bill as intended shorties were scared of the likely consequences. But in his ruling, the judge, P.E. Omi Inka, held that the court cannot grant actor bill because the matter is beyond its jurisdiction. The judge also explained that the case has already been filed before the High Court. The actor was arrested and detained by the Lagos State Police after he was alleged to have sexually molested a minor at age 7 and 14. The notification button so you get notified about fresh news updates.